A campaign can have a polished subject line, a valid send, and a working-looking button while still producing unusable traffic data. One link may point to an old page, a redirect may drop campaign parameters, or the landing page may fail only on mobile. By the time the problem appears in a report, the email has already gone out.
Email campaign QA should treat every call to action as a small data workflow: a subscriber clicks, the link resolves, campaign parameters survive, the destination loads, and the intended action can be completed. That workflow is testable before a send.
Start with a link inventory, not a visual skim
Export or list every meaningful URL in the message, including logo links, navigation links, buttons, plain-text fallbacks, unsubscribe and preference links, and any personalized destinations. A visual review often catches a button that looks misaligned, but it will not reliably catch two buttons pointing to different versions of the same page.
For each link, record the intended destination, the visible call to action, the link in the rendered message, and the expected campaign values. This creates a compact test sheet that another person can review without opening the email code.
| Check | Question |
|---|---|
| Destination | Does the URL point to the current page, form, product, or resource? |
| Redirect | Does the final URL stay on the intended host and preserve required parameters? |
| Tracking | Are source, medium, campaign, and creative values present and consistent? |
| Experience | Can a subscriber understand and complete the next action on a phone and desktop? |
Test the final URL, not just the link in the template
Email platforms frequently wrap links for click tracking. A link can therefore look correct in the template while the final request follows a chain of redirects, passes through a tracking domain, or lands on a page that has changed since the email was written.
Test links from a rendered test message in the actual email clients your audience uses. Confirm the HTTP response, the redirect chain, the final hostname, and the visible page. A successful response is only one part of the check. The page should also be the correct page, load without an authentication prompt, and expose the expected form or purchase path.
Pay special attention to links that pass through shorteners, campaign redirects, login gates, or regional routing. Each extra hop is another place for a parameter to be removed or a destination to change. If a redirect is required, document why it exists and test its final behavior rather than assuming it is harmless.
Make UTM values predictable enough to report
UTM parameters are labels attached to a destination URL so analytics can identify where a visit came from. Google recommends using relevant campaign parameters such as utm_source, utm_medium, and utm_campaign; additional fields such as utm_content can distinguish links or creative variants. Values are case-sensitive, so newsletter and Newsletter can split reporting into different values.
For email, define a naming rule before building the message. A simple example might be:
utm_source=member_newsletter
utm_medium=email
utm_campaign=2026_fall_registration
utm_content=hero_buttonThe exact names matter less than consistent ownership and reuse. Decide whether the source identifies the sending program, the audience, or the vendor. Decide how campaign names map to the planning calendar. Decide whether each call to action gets a distinct content value. Write those decisions into the campaign brief so the person building the email does not have to invent them at send time.
Before approval, compare the actual rendered URLs against the brief. Look for missing parameters, accidental spaces, inconsistent capitalization, duplicate question marks, encoded characters, and parameters attached to one link but not its companion link. Also check whether a redirect or landing-page system strips the query string.
Check the landing page as part of the email
The email and landing page are one subscriber journey. A campaign QA pass should confirm that the destination repeats the promise made in the message, displays the intended offer or form, works without unexpected consent or login friction, and records the expected conversion.
Use test cases that reflect the campaign, not just a generic page load:
- Open the link in a private browser window and confirm the page is publicly reachable if it should be.
- Test a phone-sized viewport, including keyboard focus and the submit or purchase action.
- Confirm hidden fields, source values, or referral data are populated as designed.
- Submit a controlled test and verify the expected email, CRM record, analytics event, or confirmation page.
- Check that the test record is clearly marked and excluded from production reporting.
If the email uses a personalized link, verify both the happy path and the missing-identifier path. A malformed or expired identifier should produce a useful fallback, not expose another person’s record or silently create an unmatched submission.
Compare clients after the functional checks
Rendering problems still matter, but they should be checked alongside function. Test the message in representative desktop and mobile clients, inspect the preheader, confirm that buttons have a usable tap area, and make sure images have meaningful alternative text or are correctly decorative.
Do not treat a screenshot as proof that the link works. Use the screenshot to review layout, then use the rendered message and a controlled browser session to validate destination behavior. Store both results with the campaign approval record.
Keep evidence that can be reviewed later
A practical QA record should include the message version, send audience or test segment, date tested, tester, URLs checked, final destinations, UTM values, landing-page results, and any exceptions accepted by the owner. Keep screenshots only where they help explain a visual issue. For links and tracking, structured results are easier to search and compare.
When a campaign is repeated, reuse the checklist but refresh the destinations and campaign values. A copied email is not a validated email. Pages change, redirects are retired, forms are replaced, and analytics conventions evolve.
Make the pre-send decision explicit
End the review with a clear status: approved, approved with documented exceptions, or blocked. A blocked campaign should name the failing link, destination, parameter, or landing-page action. That makes the next step concrete and prevents a vague “looks good” from becoming the record of approval.
DigitalWerks helps organizations connect email templates, websites, forms, analytics, CRM systems, and reporting workflows so campaign QA covers the complete path. Ask DigitalWerks to review an email campaign workflow when a send depends on more than the message itself.
Sources and further reading
For the current Google Analytics guidance on campaign parameters and naming consistency, see Google Analytics: Collect campaign data with custom URLs.