Campaign QA guide

How to check UTM links in a CSV before launch

A campaign file can look tidy while its links still contain inconsistent tags. Review the whole file against one set of client rules.

This walkthrough uses a small, made-up campaign for example.com. Keep a copy of your original CSV before changing real campaign links.

Start with five sample links.

Download both files, then open the campaign audit in UTM Builder. Free users enter the sample rules manually in the Client profile form. Pro users may import the saved JSON; saved-profile import is a Pro feature.

Get the five-link CSVGet the matching rules

Review each row for a different reason

  1. Mixed capitalization and spaces. The first row uses Google, CPC and Spring Sale. Review the normalized tags and required campaign prefix. Keep its other query parameter and fragment.
  2. A clean control. The newsletter row already follows the example rules. A useful audit should leave a valid link alone.
  3. An unapproved source. unapproved_network is not in this profile. Either choose the correct approved source or deliberately update the client's rules. Do not guess which network was intended.
  4. A duplicate tag. One URL includes utm_source twice with different values. Confirm the intended source before exporting a corrected link.
  5. A missing campaign. The last row has source and medium but no campaign name. Supply the real campaign identifier rather than accepting an invented value.

Review suggestions before using the export

Compare each original URL with its proposed result. Check that destinations, non-UTM parameters and fragments are preserved. After export, open a few representative links and confirm that the intended page loads. A tag audit does not prove that a destination is online or that analytics is installed correctly.

In Google Analytics, campaign-tag values are case sensitive. Google describes how they appear in traffic acquisition reports in its official URL builder guide. Use that guidance alongside your client's own naming rules.

Make this a small pre-launch check

Our suggested workflow is: save the original file, enter the client's rules in the free profile form or import a saved profile in Pro, audit, resolve each warning, export a reviewed copy, and test representative destinations. Reuse the same rules for the next campaign and revisit them when the client's channels change.

The extension processes the campaign audit locally. Free preview shows the first five rows. Saved-profile import and full audit CSV export are Pro controls. It does not replace destination testing or a full analytics implementation review. Read the naming template and check the current extension release status.