An iGaming influencer campaign report should contain campaign identity, contracted delivery, audience and traffic, validated acquisition outcomes, complete cost, attribution rules, reconciliation exceptions and a decision. Every number needs a definition, source owner, reporting window and status.
The template below is operational. It does not prescribe ROI definitions or tracking architecture; use the linked specialist guides for those choices, then document the choices here.
Download the campaign report template with a synthetic sample (CSV).
The seven-part report
- Identity: campaign ID, operator, product, creators, markets, currencies, timezone and reporting window.
- Scope: contracted deliverables, publication timestamps, make-goods, rights and evidence links.
- Delivery: platform-defined views, watch time or engagement with the export date and source.
- Traffic: clicks and sessions by approved campaign ID, link and code.
- Acquisition: validated registrations, first-time depositors and later outcomes from the operator backend.
- Economics: creator, rights, production, operations, compliance and measurement cost.
- Quality and decision: duplicates, unmatched records, incomplete windows, lessons and the next action.
A small metric dictionary prevents large arguments
| Metric | Definition to record | Primary source |
|---|---|---|
| Published deliverable | An approved contracted asset that went live and met acceptance rules | Contract and publication evidence |
| View | The platform's definition for that format; do not merge incompatible platforms without labels | Platform export |
| Tracked session | A session carrying the agreed campaign dimensions | Web analytics |
| Registration | A new accepted account after test, duplicate and invalid-account exclusions | Operator backend |
| FTD | A validated first-time depositor under the operator's written rule | Operator backend |
| Total campaign cost | All creator, rights, production, operations, compliance and measurement cost | Finance ledger |
| Cost per FTD | Total campaign cost divided by validated FTDs | Calculated from reconciled fields |
Google Analytics distinguishes user-, session- and event-scoped traffic dimensions. Its scope documentation explains why “first user source,” “session source” and event attribution answer different questions. Name the scope in the report rather than writing only “conversions from influencer.”
Synthetic worked example
The downloadable file includes this invented dataset for demonstration only: eight of eight deliverables, 120,000 qualified views, 4,200 tracked sessions, 310 validated registrations, 74 validated FTDs and $24,000 total cost. On those synthetic inputs, cost per FTD is $24,000 ÷ 74 = $324.32.
That arithmetic is not an Octo result, client result, benchmark or forecast. A real report must replace every sample value and must not calculate ROI until revenue or contribution inputs use the agreed definitions and complete observation window.
Run these checks before circulation
- Match campaign IDs across brief, links, analytics export, backend and finance ledger.
- Remove test, duplicate, rejected and ineligible-market accounts under written rules.
- List code uses that cannot be matched to accepted accounts; do not silently force a match.
- Separate clicks from sessions and registrations from validated accounts.
- Confirm currency conversion source and date where costs or revenue use multiple currencies.
- State the latest complete backend date and mark immature cohorts.
- Reconcile deliverable counts to publication evidence and explain make-goods or removals.
- Lock a corrected version and preserve the original export trail.
Manual UTMs populate campaign dimensions, but redirects, missing tags and blockers can create unattributed traffic. Google documents campaign collection and processing in its campaigns and traffic sources guide. Referral codes can recover some journeys, but code sharing can also over-credit a creator.
End with a decision, not a data dump
State what happened, how confident the team is, which limitations could change the conclusion, and what action follows. Useful actions include stop, repeat unchanged, revise the creator mix, adjust the brief, extend the observation window or run an incrementality test.
Use the ROI guide for financial definitions and the conversion-tracking guide for implementation. For a report design tied to your operator data, share the source systems and decision deadline.