Affiliate Networks

usertrax can fire the Awin and Adcell conversion pixels itself — instead of you hand-coding them into your site. You maintain merchant and publisher IDs in the dashboard, and which event triggers which commission is defined on the conversion definition.

1. Enable affiliate tracking in the script

   Add affiliate: true to window.usertraxConfig, alongside your other flags:

   window.usertraxConfig = {
     affiliate: true,
     // …other options, e.g. ga4, tagManager, facebook
   };

   Without this flag, usertrax fires no affiliate pixels, even if IDs are already configured in the dashboard.

2. Set the merchant and publisher ID in the dashboard

   Under Domains → Settings enter:

   • Awin Merchant ID
   • Adcell Publisher ID (pid)

   These IDs apply per domain and identify you to each network.

3. Set the network mapping per event

   Under Conversion Definitions, define for each event which commission it triggers on which network:

   • Awin commission group, e.g. LEAD
   • Awin fixed amount (optional) — overrides the actual conversion value
   • Adcell Event ID, e.g. 17870

   Only events with at least one of these mappings can trigger a pixel at all.

Fire the event as usual, but with your own id:

usertrax.track("lead", { id: "anfrage-8123", total: 50 });

Without your own id, no affiliate pixel fires — this is the single most important thing on this page. usertrax.track("lead") alone fires nothing, even if the merchant ID, publisher ID, and commission group are all correctly configured. The id is the key Awin uses to merge duplicate reports (ref), and Adcell requires the same value as its reference (referenz). usertrax does not invent this id itself — it has to come from you, because it must match the id your own systems use for the same event.

Awin can run client-side (this pixel) and via the server-side conversion reporting at the same time. As long as both use the same id, Awin deduplicates them via ref — no double commission results. This also lets you move from a hand-coded pixel to the server API without being double-counted in between.

Awin’s test mode (testmode) is set automatically by usertrax based on the environment — active on staging, off in production. You don’t need to configure it.

For Awin, usertrax loads no external script (no dwin1.com master tag) — the Awin conversion pixel is embedded as a plain image (<img>). Adcell offers no pixel-only variant; for Adcell, usertrax embeds the script tag Adcell provides.

Unlike Awin, Adcell has no testmode setting. If you enter a real Adcell publisher ID on a staging or development domain, usertrax will report real conversions to Adcell there — there is no way to intercept this in software. Configure the Adcell publisher ID on your production domain only.