UTM Link Builder & Auditor (Bulk) · SiteVerdict
Pricing
Pay per event
UTM Link Builder & Auditor (Bulk) · SiteVerdict
Build clean UTM links in bulk, or audit the links on your site or in an email: finds broken and inconsistent UTMs, typos, PII, Unassigned GA4 channels and redirects that drop tracking. Naming-convention rules, CSV export, optional AI taxonomy.
Pricing
Pay per event
Rating
0.0
(0)
Developer
Aman Thakran
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
2 days ago
Last modified
Categories
Features
Share
SiteVerdict — UTM Link Builder & Auditor
Stop losing campaign data to messy UTMs. Build clean tracking links in bulk, or audit every link on your site or in your newsletter, before GA4 files your traffic under "Unassigned".
Small UTM mistakes split and hide your reporting:
- "Facebook" in one link and "facebook" in another show up as two sources.
- A typo like
utm_campaingmeans the campaign is never recorded. - A link shortener that drops your parameters loses the attribution.
- An email address in
utm_contentbreaches Google Analytics' terms.
This Actor finds all of these and tells you how to fix each one.
Who it is for
- Performance marketers and agencies. Generate hundreds of consistent links for a campaign and QA them before launch.
- Email and CRM teams. Paste a newsletter's HTML and check every link before sending.
- Analytics leads. Audit the site and the links in circulation, enforce one naming convention, and fix "Unassigned" traffic.
Two modes
Audit: links from web pages (optionally crawling the same site), pasted email HTML or a pasted list.
| Check | Example |
|---|---|
| Required params missing | no utm_medium |
| Typos / unknown params | utm_campaing → utm_campaign |
| Case & spaces | Facebook Ads → facebook-ads |
| Duplicates, empty values, unfilled merge tags | utm_content={{name}} |
UTMs after # | ignored by analytics |
| Personal data | emails or phone numbers in UTMs |
| Hard-coded click IDs | gclid/fbclid copied into links |
| Internal links with UTMs | they overwrite the visitor's real source |
| Swapped source/medium | utm_source=social&utm_medium=facebook |
| GA4 channel prediction | flags combos that land in Unassigned |
| Your convention | allowed sources/mediums, separator, regex per parameter, max length |
| Consistency across all links | groups variants like Facebook / facebook / face-book |
| Destination (optional) | broken links, redirect chains, UTMs dropped by redirects/shorteners, https→http downgrades |
Build: rows of base URL + source/medium/campaign/term/content/id (JSON or CSV). Values are normalised to your convention (lowercase, separator, no spaces). Existing UTMs are replaced, other query parameters and #fragments are kept. Every link is validated, and the destination can optionally be checked too.
Output
- Dataset: one row per link, then a summary row. Views: Links, Issues and fixes, Destinations and redirects. The summary has issue counts, the predicted channel mix, inconsistent value groups and redirect losses.
- LINKS_CSV: spreadsheet-ready export (cells are protected against formula injection).
- SUMMARY: compact JSON for agents and integrations.
Example issue row:
{ "url": "https://go.example.com/bf?utm_source=newsletter&utm_medium=email&utm_campaign=bf-2026","status": "error", "channel": "Email","issues": [{ "code": "utm-lost-in-redirect", "severity": "error","message": "UTM parameters are dropped by a redirect (utm_source, utm_medium, utm_campaign); the visit will not be attributed to this campaign.","fix": "Link straight to the final URL, or configure the redirect/shortener to pass query strings through." }],"redirect": { "finalUrl": "https://shop.example.com/bf", "hops": 1, "utmPreserved": false } }
Run with Run type = Sample to audit a demo newsletter full of mistakes for free.
Optional: AI naming convention (your own key)
When inconsistent values are found, your Anthropic or OpenAI key proposes:
- one clean convention;
- an old → new mapping for every value found;
- a list of GA4-friendly mediums.
It runs once per run and only uses the values in your links. The key is stored encrypted and never logged.
Pricing
| Event | Price |
|---|---|
| Link validated or built | $0.0005 |
| Destination / redirect check | $0.002 |
| Web page scanned | $0.003 |
| AI convention | $0.03 per run |
Example costs:
- Auditing one 40-link newsletter with destination checks costs about $0.10.
- Building 1,000 links without destination checks costs $0.50.
FAQ
Does it change my links? No. Audit mode only reads them. Build mode returns new tagged URLs for you to use.
How accurate is the GA4 channel prediction? It follows Google's published Default Channel Group rules with a representative list of social, search, video and shopping sources. Google's full source lists are longer, so treat it as a strong hint rather than a guarantee.
Does following links count as a visit in my analytics? It may appear in server logs, but the requests are made without running JavaScript, so GA4 tags do not fire. The User-Agent identifies us honestly.
Limits
- Up to 20,000 links, 200 crawled pages and 2,000 destination checks per run.
- Links behind logins or bot protection cannot be followed.
- robots.txt is respected for every page and destination. Links we may not follow are marked "not verified".
- JavaScript-generated links (e.g. single-page apps) are not seen, because pages are not rendered in a browser.
Sources and compliance
- Data: the pages, email HTML and links you provide. Destination checks request each link once and do not run JavaScript.
- Rules:
- GA4 Default Channel Group (checked 2026-10-11).
- GA4 UTM parameters (checked 2026-10-11).
- Google Analytics policy against PII (checked 2026-10-11).
- Polite fetching: honest User-Agent
SiteVerdict/utm-link-auditor (+aman.thakran@bharatfare.com). robots.txt is respected on every hop. Requests to one host are sequential, at most one per second, with no bot-protection bypass. - Security: SSRF guard on every request and every redirect. Size caps and timeouts on all requests.
- UK GDPR / PECR: personal data is never extracted. If a link contains an email address or phone number, only the issue is reported. Delete the run's storage if your links contain personal data.