CampaignLint workflow guide

Compare an approved offer with every final email variant

Duplicating a promotional email is useful until one country or client variant keeps the old discount, coupon or button destination. Valid UTM parameters cannot establish which offer the client approved. Use the approved campaign sheet as the comparison source.

A practical check

1. Start with the signed-off copy, not the draft you are checking. For one email, enter the exact offer phrase, optional literal coupon, text button label and HTTPS destination in the free quick check. Add last campaign’s offer as forbidden text when useful.
2. For recurring variants, use the CSV template: variant, file, required_text, coupon, cta_text, cta_url, forbidden_text. Use unique filenames and variant names. Separate required phrases, such as the offer and expiry wording, with |. Export the final email HTML for each row.
3. Compare one actual variant free. Inspect the approved value next to the observed value. Pro compares up to 20 variants together, including explicit incomplete entries for missing files, and exports a single review report. Correct the source HTML and run a fresh check before sending.

Example

Approved UK: Save 20% · SAVE20 · /uk/spring
Final UK: Save 10% · SAVE10 · /uk/winter
Findings: required offer absent, literal coupon absent, stale offer present, wrong CTA destination
A French variant with its own approved text is checked against its own row.

Know the scope

This is a deterministic comparison of explicit phrases and text CTA destinations, not a judgement about the writing. Case and words matter; ordinary spacing is normalized. The six standard lowercase UTM fields are ignored only for destination comparison; other query values and URL fragments remain relevant. Image-only offers/buttons, subject lines, expiry arithmetic, CSS rendering, recipient selection, coupon redemption and redirects need separate QA. Missing files and template or conditional markup do not become clean passes. A hash identifies the compared snapshot; it does not prove client approval. For one-off emails, a manual checklist or configurable free QA tool may be sufficient. Batch checks and reusable named sheets are the specific paid convenience.

All guides