CampaignLint workflow guide

Check client newsletter links against the intended domain and campaign

Before asking a client to approve a newsletter, check the destination list against the client host and the specific campaign you meant to send. A link can contain complete, lowercase UTM tags and still belong to another client or last month’s campaign.

A practical check

1. Copy the actual destination URLs into a list, one per line. Set the exact allowed host or hosts from the client’s approved destinations.
2. Set the expected utm_campaign value. Run the free CampaignLint check and investigate every unexpected host, campaign value, duplicate or missing required field.
3. Correct the source links and run the check again. If you need a handover artifact, Pro exports HTML findings and JSON containing the selected rules and results. Keep those results with the final source list.

Example

Allowed host: shop.example.com
Expected campaign: spring
shop.example.com + spring → matches selected text rules
other-client.example.com + spring → unexpected host
shop.example.com + winter → unexpected campaign value

Know the scope

All three example links can have valid UTM syntax. The host and campaign policy supplies the context that syntax alone cannot provide. CampaignLint checks up to 500 pasted URLs and does not follow tracking redirects, fetch page status or prove analytics attribution. Test wrapped links and actual attribution separately. Basic UTM hygiene can also be checked with free tools; CampaignLint Pro is for retaining findings and the rules used for your client check, with one reusable local rule set. Free previews need no account; purchasing Pro uses ChatGPT sign-in and provides a license code. Monthly and annual subscriptions are available.

All guides