WebmasterID logoWebmasterID
UTM tracking

Partner / co-marketing UTM tracking

Co-marketing only measures cleanly when both partners tag links the same way. This page shows how to agree a shared utm_source naming and campaign convention up front, so a joint campaign aggregates instead of fragmenting across two different schemes.

Verified against primary sources

Agree the convention first

Before any link goes out, write down the exact strings both sides will use. The most common failure is each organisation choosing its own casing or name for the same partner. Lock it in a shared doc:

Why a shared convention matters

If your side tags utm_source=acme and the partner tags utm_source=Acme-Corp, your two analytics views will never reconcile and the joint campaign looks smaller in both. A single agreed allow-list of strings means the same campaign aggregates cleanly no matter who built the link.

Keep the list short and documented, and treat any new value as a change both sides sign off on rather than an ad-hoc decision.

How it appears in analytics and logs

A visit with utm_source set to the partner's agreed name confirms the co-marketing channel. If each side invents its own labels, the same campaign splits across mismatched rows.

Diagnostic use case

Agree one shared UTM convention with a co-marketing partner so both organisations attribute the joint campaign consistently.

What WebmasterID can help detect

WebmasterID reads the agreed utm_source and utm_campaign at ingest and attributes the joint traffic consistently, so both partners can reconcile a shared campaign against the same labels.

Common mistakes

Privacy and accuracy notes

Use the partner's brand name as a stable label, not any individual's contact details. UTM values are public; keep personal data and internal identifiers out.

Related pages

Sources and verification notes

Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.