Documentation

Google Tag Manager Integration

How to accurately track influencer conversions using the official Influise GTM Templates.

1

Prerequisites

Influise uses server-side click ID tracking. Influencers generate traffic via a redirect link {brandSlug}.influise.com/c/{slug}. This drops a persistent click ID (clid) into the destination URL.

  • Ensure you have configured a Workspace URL under your Influise Settings (e.g. mybrand).
  • Find your API Key inside your Influise Settings. You will need this for the conversion tag.
  • Download the official GTM Templates (.tpl files) from our Integrations hub to import into your workspace.
2

Tag 1: Store Click ID (Initialization)

When a visitor lands on your site via an influencer tracking link, they will have a ?clid= parameter in their URL. This tag extracts it and stores it securely in a 1-year first-party cookie based on last-click attribution.

Tag Configuration

  • Tag Type: Custom HTML (or import the Influise Click Cookie template)
  • Code: Paste the JS block from the Integrations page (if using Custom HTML)
  • Trigger: All Page Views
3

Tag 2: Send Conversion Event

When a customer purchases or registers, this tag fires. It reads the cookie stored by Tag 1 and transmits the clickId back to Influise via a secured API payload. If no cookie is found (e.g. returning customer on different device), it can gracefully fall back to matching the customerId from the first conversion.

Tag Configuration

  • Tag Type: Influise Conversion (Import via GTM → Templates → New → Import)
  • Send Mode: Select Pixel
  • API Key: Paste your API key from the Influise Dashboard
  • Trigger: Custom Event (Fire on your Purchase/Sign-up event)

Data Variables (Optional but Recommended)

  • Customer ID: Map to your GTM Variable `{{Customer ID}}` (used for recurring billing / cross-device matching)
  • Order / Payment ID: Map to `{{Order ID}}` (used to prevent duplicate webhook counting)
  • Conversion Value: Map to `{{Order Value}}` (overrides the Influencer's default CPA threshold)

Note: The conversion tag exits silently if neither a valid click cookie nor a Customer ID is available.

4

Going Ad-blocker Proof (sGTM)

For absolute 100% data fidelity, we highly recommend shifting Tag 2 (Conversion Event) into a Server-Side GTM (sGTM) container.

Change the Send Mode on Tag 2 to Server Container. This pushes an influencer_conversion event to the dataLayer. Then, create a GA4 Event Tag triggered by influencer_conversion that forwards the variables to your sGTM Container URL. Inside the sGTM server, a single HTTP Request tag ferries the payload to Influise. This completely shields your API Key from the browser and prevents ad-blockers from terminating the payload network request.