Affiliate

“Affiliate” lives in two worlds at once. In GA4 ecommerce it is a structured field on the purchase event — the affiliation parameter — used to tag the marketplace, store, or sales partner attached to a transaction. In marketing, “affiliate” is a partner who promotes your offer for a commission. This guide covers both meanings, shows how to wire the GA4 parameter through the dataLayer, and explains how affiliate traffic differs from a generic referral.

What Is “Affiliate” in GA4?

In Google Analytics 4, affiliate is shorthand for the affiliation parameter — a string field on the purchase ecommerce event that identifies where a transaction happened or who drove it. It is one of the official ecommerce parameters documented by Google. Setting affiliation lets you split revenue by store (“Main Site” vs “Amazon Marketplace”), by partner (“Affiliate Network A” vs “Direct”), or by physical location in omnichannel setups.

It is optional. GA4 will accept a purchase event without it. But if you run more than one storefront, sell through marketplaces, or want a clean breakdown of partner-attributed revenue inside GA4 reports, the affiliation field is the cleanest place to put that label.

The affiliation Parameter in GA4 Ecommerce Events

The parameter sits inside the ecommerce object of the purchase event. It is a string with a 100-character limit. You can also set affiliation on individual items in the items array — useful when one order contains products from multiple stores or marketplaces.

If both are set, the item-level value takes precedence for that product line in GA4 reports. The event-level value still appears as a transaction attribute under Reports → Monetisation → Ecommerce purchases → Item affiliation.

How to Pass Affiliation Data via dataLayer

The clean implementation is a dataLayer push fired from the order confirmation page after a successful payment. Below is the canonical structure with affiliation highlighted in context:

dataLayer.push({
  event: 'purchase',
  ecommerce: {
    transaction_id: 'T12345',
    value: 99.99,
    currency: 'USD',
    affiliation: 'Amazon Marketplace',
    coupon: 'PARTNER10',
    items: [{
      item_id: 'SKU123',
      item_name: 'Wireless Headphones',
      affiliation: 'Amazon Marketplace',
      price: 99.99,
      quantity: 1
    }]
  }
});

In Google Tag Manager, map a dataLayer variable to ecommerce.affiliation and pass it as an event parameter on your GA4 Event tag. The parameter name in GA4 will be affiliation — case-sensitive — and shows up automatically in the standard ecommerce reports. No custom dimension is needed for the built-in slice.

Multi-Store / Marketplace Tracking with Affiliate

The affiliation field shines when one GA4 property serves multiple revenue surfaces. Common patterns:

• Main site + marketplace mirror. Sell on your own domain and on Amazon. Tag the website orders 'Main Site' and the Amazon API-imported orders 'Amazon Marketplace'.
• Multi-brand house. One company, three storefronts. Tag each transaction with the brand name to compare revenue per brand without splitting the GA4 property.
• Online + offline. Pipe in-store POS transactions via the Measurement Protocol and tag them 'Retail — Store 14'.
• White-label resellers. Each reseller gets a unique affiliation string so you can audit revenue per partner without setting up dozens of properties.

Heads-up: the affiliation parameter is not the same as source/medium. It describes where the sale happened, not where the click came from. Use UTM parameters for click attribution and affiliation for transaction tagging.

Affiliate Marketing — Definition and Models (CPA, RevShare, Hybrid)

Outside GA4, “affiliate” means a partner — a publisher, influencer, comparison site, or coupon platform — who sends you traffic in exchange for a commission. The commission structure is one of three models, sometimes combined:

1. CPA (Cost Per Action). A fixed payout for each conversion — a signup, qualified lead, or sale. Predictable for affiliate budgeting; favoured by lead-gen and one-off-sale products.
2. RevShare (Revenue Share). A percentage of revenue, often recurring. Common in SaaS, subscription, and long-LTV verticals where the partner shares in the customer’s lifetime value.
3. Hybrid. A smaller fixed CPA plus a smaller revenue share. Reduces upfront partner risk on hard-to-acquire users while keeping recurring upside.

Tracking Affiliate Conversions in GA4 (UTM + affiliation parameter)

Affiliate conversion tracking needs two pieces working together: click attribution on the way in, and transaction tagging on the way out. UTMs and the affiliation parameter solve different halves of the problem.

A practical pattern: tag every partner link with utm_source=<partner-slug>&utm_medium=affiliate&utm_campaign=<program>, set medium=affiliate as a custom channel group, and pass the partner slug into affiliation on the resulting purchase event. The two views — acquisition by partner and revenue by partner — then reconcile cleanly. For revenue-tying details see tying revenue to traffic.

Common Affiliate Networks and How to Tag Their Traffic

Each major network exposes click parameters you can rewrite into clean UTMs at the landing page or via a tag. A quick reference for the largest networks:

Standardise utm_medium=affiliate across every program. That single rule lets you build one channel group, one report, and one revenue-by-partner pivot — instead of chasing dozens of bespoke source values.

Affiliate vs Partner vs Referral — Distinctions

The three terms overlap in casual use but mean different things in analytics. Mapping them to GA4 correctly avoids double-counting and keeps the channel report honest.

The cleanest rule: always tag affiliates with UTMs so they never fall back into the generic referral traffic bucket. An untagged affiliate looks identical to an organic blog mention, and you lose the ability to credit (or audit) the partner.

Frequently Asked Questions

Related Terms

• CPA — fixed payout per conversion, the most common affiliate model
• Conversion — the action that triggers the affiliate payout
• Purchase event — where the affiliation parameter lives
• UTM — parameters for click attribution on partner links
• Source — where the click originated
• Medium — channel category, set affiliate for partner traffic
• Referral traffic — generic inbound, what untagged affiliates fall into
• Attribution model — how GA4 splits credit across touchpoints
• Cookie — how partner clicks persist to the conversion