How to Track Influencer Sales with Promo Codes and UTM Links in GA4

UTM parameters are five query-string fields that Google Analytics reads from any URL a visitor arrives on. UTM stands for Urchin Tracking Module, named after Urchin, the analytics product Google acquired in 2005. Add the parameters to a link and every session that starts from it carries the values you set.

GA4 exposes these as session-scoped dimensions such as "Session manual source" and "Session manual ad content". For creator and partner marketing, utm_content is usually where the individual creator or placement lives. Source, medium, and campaign are usually shared across a wider initiative. Ideally, try to be as detailed as possible with these fields because in the long term you'll end up with richer data for analysis.

Build each link with Google's Campaign URL Builder or by appending the parameters yourself. A tagged link for a creator's Instagram bio looks like this:

The values are case-sensitive and free-form, so it's best to agree on a convention up front. Instagram, instagram, and IG become three separate rows in every report, and sticking to a convention will help avoid having to manually reconcile these in a report.

• Lowercase everything and separate words with hyphens: maya-rivers, not Maya Rivers.
• One utm_content value per creator or placement, reused across all of their links.
• Keep utm_campaign consistent for everything inside the same initiative so you can roll results up.
• Shorten tagged links with a redirect you control (a /go/maya path on your own domain, or a shortener that preserves query strings). Some shorteners and in-app browsers strip parameters, so click every link once and confirm the UTMs survive to the destination.
• Never put UTM parameters on internal links between pages of your own site. They restart the session with a new source and corrupt your data.

The same convention applies more broadly than just creator marketing. A QR code on packaging or a billboard encodes a tagged URL with utm_medium=qr. An event booth gets its own utm_content. Anywhere you can hand out a distinct URL, you can measure the traffic that came from it.

GA4 has a dedicated coupon dimension called "Order coupon" (orderCoupon in the API), and this sometimes trips people up because it stays empty by default. It only populates when your purchase event includes the coupon parameter. If your reports show "(not set)" for every order, check if the coupon parameter is missing from the event.

A purchase event that feeds the coupon dimension looks like this:

Where that parameter comes from depends on your tech stack. Most plugins, like Shopify's plugin for Google and Youtube, and Woocommerce's GA4 plugin, send the redeemed discount code automatically. If you have a custom checkout, you'll need a developer to add coupon to the purchase event. Whichever applies to you, verify it the same way by placing a test order with a code applied, opening GA4's DebugView, selecting the purchase event, and confirming the coupon parameter carries the code.

The next step is to make the discount codes themselves attributable. SAVE20 handed to eight creators tells you nothing about any of them. One code per creator, ideally their name or handle (MAYA20), gives the creator something natural to share with their audience and gives you a clean per-partner row in the data. Keep those codes out of your email blasts and paid ads, because the moment a code finds its way onto a coupon aggregator site, its redemptions become less inaccurate for attribution.

Tagged link sessions appear under Reports → Acquisition → Traffic acquisition. The default view groups sessions by channel, so switch the primary dimension to "Session source / medium" and add "Session manual ad content" as a secondary dimension to see individual utm_content values. Redeemed codes appear under Reports → Monetization → Ecommerce purchases with "Order coupon" as the dimension.

Two things to know when reading these reports. GA4 has cardinality limits, so once a report exceeds them, low-volume rows collapse into "(other)", which hits long-tail utm_content values first. And standard reports can lag by 24 to 48 hours, so DebugView and Realtime are the places to verify a fresh setup.

The bigger limitation is that GA4 attribution stops at the discount code or tracking link itself. It can show you that MAYA20 was redeemed 16 times and maya-rivers drove 422 sessions, but it doesn't know those two rows belong to the same person, what her posts cost, which campaign she was part of, or what else was live that week. Answering "was this partnership worth it?" means putting the data somewhere that holds the rest of your marketing picture.

This is the part Brandwave handles. Connect your GA4 property in Reporting, and the performance page gains a "Promo codes and tagged links" panel listing every coupon code and tagged link GA4 recorded, with sessions, users, and your chosen outcome events beside each one.

From there you map each signal to the creator, campaign, or activity that produced it. MAYA20 and maya-rivers both link to Maya's profile, so her code redemptions, link sessions, content performance, and costs sit in one place instead of three exports. Signals from a podcast sponsorship or a print run map to those activities the same way.

Mapped signals become one layer of evidence among several that help you to triangulate what is really happening in your marketing programme. Brandwave shows them next to self-reported attribution and your GA4 success metrics, such as sign ups and purchases. So when a creator's discount code redemptions spike, you see a lift in "heard about you from a creator" survey answers, and get a lift in sign-ups, all over the same period of time, you can observe that pattern in one view and draw inferences and conclusions from a clearer picture. The influencer marketing measurement framework covers how this evidence layer fits with creators, activities, and costs, and your AI assistant can query all of it through the MCP server or the API.

• Coupon shows "(not set)": the purchase event is missing the coupon parameter. Fix the event; check a test order in DebugView.
• Duplicate coupon rows like MAYA20 and maya20: GA4 stores codes as sent. Standardize casing at the checkout level, or group the variants when you map them in Brandwave.
• Tagged link traffic shows as direct: a redirect or shortener is stripping the query string. Click the link and check the final URL still carries the UTMs.
• UTM values landing under "(other)": you hit GA4's cardinality limits. Trim unused parameter variants and lean on fewer, more consistent values.
• A creator's link works but the code doesn't (or vice versa): each signal travels a different path (links through sessions, codes through purchase events). Verify them independently.
• Signals missing in Brandwave: confirm the connected GA4 property is the one receiving the traffic, then allow for GA4's reporting delay of up to 48 hours.

If you get stuck wiring any of this up, email hello (at) gobrandwave.com and one of the team will help you get the data flowing.