LINKRULES / CAMPAIGN NAMING
Many links.
One shared language.
A calmer way to keep campaign reports in step.
01 / SET THE STANDARD
Naming rules
A few clear choices. Consistent across every row.
Values always use Unicode NFC and trim outer whitespace. Accents are preserved, not transliterated.
Managed keys: source, medium, campaign, term, content. Overwrite removes their duplicate and case variants, including optional values left blank in CSV. Other query keys and fragments are preserved.
02 / BRING YOUR BATCH
Campaign links
Paste a CSV or choose a file. The sample is invented.
Required: url, source, medium, campaign. Optional: term, content. One URL per row. 1,000 rows / 2 MiB maximum. Values are plain text, not pre-encoded.
03 / REVIEW THE DIFFERENCE
Before. After. Clear.
Original and transformed URLs stay side by side. Results are text, never clickable links.
| Row / status | Original URL | Transformed URL | Review notes |
|---|
A shared standard starts here.
Apply the rules to see every change before you export.
Keep the good work.
Save the original CSV and rules in an editable JSON backup.
What is preserved, and what should I check?
Only HTTP(S) URLs are accepted. Credentials, backslashes, malformed escapes, controls and bidirectional/invisible formatting characters are rejected. URLs are parsed with the browser URL API: host casing, international domains, dot segments, spaces and default ports can normalize. Unrelated query tokens keep their ordering, duplicates and encoding; the fragment is retained in the URL API’s serialized form.
Retain keeps existing managed values exactly, including duplicate/case variants. Those values do not receive naming rules, and nonstandard key casing may not be recognized by analytics tools. Required existing values cannot be blank. Overwrite removes all five managed keys before adding nonblank CSV values. Custom utm_* keys are preserved. Imported projects/rules reset the choice to Review: overwrite permission is never saved.
UTM source, medium and campaign are required in every CSV row, even when retaining existing values. Reserved characters are encoded once from plain text. A literal %20 input becomes %2520, not a space. The original URL column supports reversal; spreadsheet-safe CSV prefixes formula-like cells with an apostrophe. Use project JSON for exact raw input preservation.
Audit exports include all rows with statuses and errors; ready-link exports include only successful rows. Filters and pagination do not limit either export. No shorteners, redirect hosting, click analytics, campaign launching, destination verification or automatic persistence. JSON and CSV are not encrypted. Opening or reloading the app loses unsaved work.
Free beta, privacy and limits
No account. No charge. This beta has no login or billing. Up to 1,000 data rows and 2 MiB CSV; original URLs 8,192 UTF-16 units; tags 256; rule-set names 80. Project JSON: 5 MiB; rules JSON: 16 KiB. These are local processing bounds, not paid quotas. URL validity is not destination safety or reachability verification.
Your inputs are processed locally, not uploaded by this app. When hosted, the hosting provider receives normal access logs for page and asset requests, such as your IP address, request time and browser information. No app analytics or tracking scripts are included. Choosing the ModuCove home link leaves this app and makes a request to that website.
Work stays in browser memory; there is no automatic saving. Projects include original CSV and naming rules; audit exports include original and transformed URLs. Downloads are unencrypted; keep them private. Closing or reloading loses unsaved work. Resetting the workspace does not delete downloaded files. This app never visits or checks the URLs you enter.
Browser rendering, native downloads, keyboard and screen-reader behavior still require real-browser checks. Review outputs before relying on or sharing them.