CampaignLint workflow guide

Validate a campaign destination against the intended domain

A campaign can have correct UTM fields and still point to the wrong website. A staging domain, a misspelled host or an unexpected subdomain can survive a quick visual review. Checking the parsed hostname gives you a precise rule to apply to every link.

A practical check

1. List the exact allowed hosts, such as shop.example.com and www.example.com. Do not include a protocol or path.
2. Require HTTPS if the campaign policy calls for it. Include each permitted subdomain explicitly.
3. Paste the destination batch and investigate every unexpected host.

Example

Allowed host: shop.example.com
shop.example.com → matches
shop.example.org → unexpected host
shop.example.com.attacker.example → unexpected host

Know the scope

CampaignLint compares exact hostnames. An allowed host does not automatically authorize its subdomains, and a host that merely contains the allowed text does not match. This is a text validation step, not a malicious-site detection service. It does not prove ownership, certificate validity, page availability or the result of a redirect.

All guides