Track your TE campaigns

Give each source a label

Use a different campaign label for each exchange and page version. If your analytics supports UTM parameters, an example is ?utm_source=exchange-name&utm_medium=traffic_exchange&utm_campaign=welcome_v1. Replace the example names and confirm your destination still works with the parameters.

Do not put passwords, account tokens or visitors’ personal details in a tracking URL.

Record the same fields each time

• Exchange and campaign name.
• Date range and page version.
• Credits used and visits reported by the exchange.
• Visits recorded on the destination.
• Completed actions, such as confirmed signups.
• Time spent and any campaign cost.

Calculate one useful rate

Divide completed actions by the visits used for that calculation, then multiply by 100. Label the denominator clearly: exchange-reported visits and analytics sessions are not interchangeable. Keep the calculation consistent when comparing page versions.

Investigate differences

Timers, blocked analytics, consent settings, repeat visits and loading failures can all affect counters. Treat a discrepancy as something to investigate. It is not enough on its own to establish a cause.

Keep rewards in a separate column

TE credits, Colossari damage and funded-event awards represent different things. Record them separately so a game reward does not conceal an advertising campaign that missed its goal. Colossari’s Hunt and Prizes pages show game activity; your destination analytics shows what visitors did on your page.