SubIDs Email Affiliate Tracking: UTM Hybrid & Click Zones
Operators who trust UTMs alone to tell them which email send, placement, or CTA earned a commission end up with beautiful dashboards and zero payout proof.
UTMs are an analytics story. SubIDs pay the commission. And email is where the gap between those two stories gets widest, fastest, because your email service provider wraps every link inside its own click tracker, often stripping or reordering the parameters you so carefully built.
If you can’t answer “which send and which click zone earned this locked commission – and will the network still see that SubID after the ESP wraps the link?” you’re managing a newsletter, not an attribution system. This piece assumes you already know what SubIDs are (the full taxonomy lives in the SubID tracking guide). Here, I’m zeroing in on the email ops layer: zone naming, the UTM hybrid that doesn’t turn into spaghetti, and the verify-click habit that keeps your payout data alive through ESP redirects.
The failed “UTMs are enough” assumption
UTMs do one thing: they hand your analytics tool a story about the session. utm_source=newsletter, utm_medium=email, utm_campaign=spring_sale tell Google Analytics “this visitor came from the spring sale email.” That’s useful. It is not, however, a receipt the affiliate network uses to decide who gets paid.
The network’s attribution logic runs server-side, on its own click ID, cookie, and postback. It doesn’t read utm_source and credit you. It reads its own subId1, SID, afftrack, or whatever SubID slot you were supposed to populate. If that slot is blank, you get a commission without any trace of which email sent it, which link inside the email got the click, or which list segment it came from.
Even worse: if you send an email with clean affiliate URLs – no SubIDs, just the bare network link – and add UTMs only for your analytics, the network sees the conversion, you see the network report, and you feel fine. But you just dropped the entire send story. You cannot prove that the hero CTA worked while the footer link was dead weight.
You cannot negotiate with an advertiser using placement-level data. You cannot detect a list segment that converts way above average and deserves more sends. Add in the fact that untagged email clicks often land as Direct / None in Google Analytics, and you lose even the session-level story. So if your entire reconciliation habit is “I’ll download GA’s campaign report and match it to the network’s commissions,” you’re matching apples to absence.
Publishers who try to align ESP “influenced” revenue with network locked commissions in a spreadsheet rarely close the gap – the missing piece is almost always the SubID.
So, no: UTMs are not enough. They’re necessary for the analytics layer. But if you want payout truth, you need a SubID on every email link that matters.
Split the jobs: analytics story vs commission story
Here’s the clean split I recommend keeping on a sticky note:
- UTMs (source/medium/campaign) = which send, which channel, which campaign – the analytics story.
- SubIDs (network parameter) = which placement, which creative, which list segment – the payout story.
You tag your email links with both, but you never confuse their roles. A well-built UTM hybrid is exactly that: a URL carrying UTMs for GA, and network SubID slots for the affiliate program, riding together through the click. But when you reconcile money, you open the affiliate network report – not GA, not your ESP dashboard – and you look for the SubID column. That column is your evidence.
There’s a quiet lie hiding inside most ESP analytics: the “influenced” revenue metric. That number is the ESP’s last-touch attribution guess, often inflated by view-through windows and internal weighting. It over-claims compared to the locked, final commissions the network actually paid. Treat the ESP dashboard as triage – a quick sanity check for total clicks – but never as cash. Cash lives in the network.
If your SubIDs show up empty in the network report despite being appended correctly, you need the full diagnostic sequence. I wrote that separately as a step-by-step diagnosis – SubID tracking not showing up? How to diagnose it – because the causes (wrong parameter name, network refuses hand-typed SubIDs, postback not returning the value) are multiple and none of them are “just wait longer.” Before you treat that blank column as a mystery, rule out the obvious.
A quick fallback: coupon/vanity codes. When everything else fails – the ESP strips the parameter, the redirect drops the query string, the network simply won’t accept a SubID – a unique code per send/zone can serve as a rough attribution key. But it’s a fallback, not a substitute. It doesn’t tie back to the exact click the way a SubID does, and it’s useless for multi-zone tests inside the same email. Keep it in your back pocket for worst-case scenarios, not for your primary CTAs.
Click-zone naming (treat the email like a page)
An email isn’t a page, but for tracking purposes, pretend it is. It has a header, a hero section, a body, a footer, maybe a P.S. or a secondary offer. Each clickable zone that leads toward a commission needs its own stable identifier, passed through the SubID slot.
Why? Because if every CTA in the blast shares one SubID (say 2026-08-nl42), you can’t tell whether the footer won or the hero did. You can’t A/B test CTA copy with SubID granularity. You can’t prove that moving the primary link higher in the layout lifted commissions, because the data collapsed into a single bucket.
So, before you paste the first link into your ESP, map the zones. At minimum: header logo (if it links to a merchant), hero CTA, mid-body link, footer CTA, and PS/secondary offer. Give each zone a short, lowercase, consistent name: hero, midbody, footer, ps. No fb vs facebook splits, no top-cta one week and hero_cta the next.
Store these mappings in a single naming sheet – a shared spreadsheet or a Notion page. That sheet lists every zone label, the SubID encoding grammar you’ll use, and examples with a campaign date or code. Like this: 2026-08-nl42-hero, 2026-08-nl42-footer. The send date/code is deliberate – not random – so you can later find every commission from that send and that zone.
Now, a separate layer: utm_content. Google’s UTM parameter definitions describe utm_content as a parameter “used to differentiate ads or links that point to the same URL.” That’s exactly what you want for CTA copy tests – e.g., utm_content=button-vs-text. Use utm_content for the analytics A/B signal. Keep the SubID as the payout slot. That way you can cross-check: the network says the footer zone earned the commission, and GA confirms that the text-link variant drove the click.
One hard rule: never put UTMs on internal post-click navigation links. If your email lands on a bridge page that then links to the merchant, only the merchant-bound link carries the SubID + UTMs. Internal nav links get nothing, or at most a clean ?ref=internal. Otherwise, you’ll overwrite the original campaign attribution inside GA and lose the thread.
Building the hybrid URL without spaghetti
The practical pattern is simple: the affiliate destination carries the network’s SubID slots for zone and list; UTMs ride along for GA when the hop allows query strings. You don’t need a tracker to do this – just discipline.
A typical hybrid link (example only, affiliate IDs and URLs are illustrative) might look like:
https://track.impact.com/click?affid=12345&subId1=2026-08-nl42-hero&url=https%3A%2F%2Fmerchant.com%2Fproduct%3Futm_source=newsletter%26utm_medium%3Demail%26utm_campaign%3Dspring_sale%26utm_content%3Dhero_button
Notice the SubID carries the zone identifier. The UTMs sit on the destination URL, after encoding.
Slot names and character limits vary by network – verify the current network docs. When you have only one SubID slot, encode zone and send into one disciplined string: 2026-08-nl42-hero. Document that grammar on your naming sheet so everyone on the team knows that the first segment is the date, the second is the newsletter code, the third is the zone. No guessing.
When you need the full matrix of network parameter names – Impact uses subId1, CJ uses SID, Awin uses clickref, etc. – the complete SubID tracking guide has the table. I’m not rebuilding it here. What matters for your email link: check that network’s parameter name, encode your zone, and test it.
One more note: if your ESP auto-appends its own UTM tags (like Kit’s global advanced tracking does with utm_source=kit&utm_medium=email), that’s fine for the analytics layer. But it doesn’t touch the SubID. You still need to hand-code that SubID parameter into the affiliate link. The ESP won’t do it for you.
ESP wrapping, redirects, and the verify-click habit
Every major ESP – Mailchimp, Kit, Klaviyo – wraps your links through its own click-tracking server. Mailchimp, for example, replaces your original URL with a tracking link that includes mc_cid and mc_eid parameters, and the utm_ parameters might stay in the final redirect URL – or they might not (Mailchimp’s click-tracking documentation). Some ESPs allow per-link custom parameters, but many “simplify” the URL and strip unrecognized query strings in the process.
The result: your carefully built ?subId1=2026-08-nl42-hero can survive the ESP wrapper on hop one, only to vanish when the ESP’s redirect chain passes it to the network. In multi-hop setups, the SubID can exist in the original email HTML and still be gone by the time the click arrives at the network’s tracking endpoint. The network sees a clean click with no segmentation tags, pays the commission, and you get no attribution.
Do not outsource payout truth to the ESP. Its job is to count clicks within the email environment, not to guarantee that your network parameter survives every hop onwards. When the ESP says “links are click-tracked and parameters are preserved,” test that statement yourself.
Here’s the verify-click habit I drill: before you send the blast, pull a test email into your inbox (in a private/incognito window – no logged-in sessions that could change cookie behavior). Open the raw email HTML if you can, or inspect the link’s href. Click each zone link from that private window. Watch the address bar.
Does the first redirect show your SubID? After any pretty-link or bridge page? If the SubID disappears before the merchant’s checkout page, you have a strip. Dig into the redirect chain, not the ESP’s analytics chart. For multi-hop leakage where the issue is deeper than the ESP (e.g., a bridge page stripping parameters before passing to the network), start with diagnosing redirect chain commission leakage. Then cross-reference the diagnosis of silent attribution breaks for the broader picture. And for the newsletter context – why you’re doing all this email SubID work in the first place – the survival argument for affiliate publishers under AI search covers why the inbox matters beyond the search volatility. But this article is about tracking ops, not list growth.
One-sitting email SubID checklist
Do this once, sitting at your desk, before you log out. The whole thing should take under an hour the first time, minutes after you’ve done it once.
- Define a zone map for your email template: header logo, hero CTA, mid-body link, footer CTA, PS/secondary offer.
- Fill out the naming sheet with consistent lowercase labels and a documented grammar for combining send date/code and zone into the SubID string.
- Build hybrid URLs: affiliate destination carries the SubID parameter(s) for zone and list; UTMs ride on the destination URL for GA (using
utm_contentfor CTA variant). - In a private/incognito window, open the test email and click every zone link. Confirm the SubID appears in the URL after the first owned hop and survives any bridge page.
- Log into your affiliate network and verify that each click registered with the correct SubID value in the click log or conversion report – not blank, not “unknown.”
- Reconcile ESP vs network: compare the ESP’s click report to the network’s click report, but never treat the ESP’s “influenced revenue” as your paid commission total. The network report is cash.
- Do not mass-reuse a single SubID across all zones in the same send. One SubID per zone per send.
- If the SubID column is empty after a tested click, escalate to the SubID diagnosis guide.
- For advanced slot limits, network-specific parameter names, and multi-zone strategies, bookmark the complete SubID tracking guide.
- Keep a send log: date, campaign code, list segment, and the exact SubID strings used, linked back to the naming sheet. That log is your audit trail.
UTMs explain the session; SubIDs pay the commission. When your email SubIDs survive the ESP wrapper and land cleanly in the network report, you stop guessing which newsletter actually earns its keep. You know – by zone, by send, by list. That’s the payout truth.
