What is a Cachebuster?
A cachebuster is a dynamic value used to ensure that each IMG tag request is unique. This prevents browsers, CDNs, or proxy servers from caching the request and ensures that all conversion events are tracked correctly.
Why is it required?
IMG tags are executed as simple GET requests. Without a cachebuster, the same request may only be fired once, causing conversion events to be missed. A cachebuster guarantees that every event is logged.
How to Use the Cachebuster
In the IMG tag template, the parameter ord=[CACHEBUSTER] must be replaced with a dynamic value that changes on every page load or event trigger.
Recommended Values
Preferred:
- Timestamp / Unix timestamp (e.g. Date.now(), {{Timestamp}}).
Alternative:
- Random number (e.g. Math.random())
Conditionally allowed:
- Order ID or Event ID (only if guaranteed unique per event).
Examples
Google Tag Manager:
ord={{Timestamp}}
JavaScript:
ord=Date.now()
ord=Math.floor(Math.random()*10000000000)
Important Notes
- Do not use static values.
- Do not reuse the same cachebuster value across multiple events.
- Static or reused values may result in missing conversions and incorrect optimization.
Summary
The cachebuster is mandatory for IMG-based tracking. Always use a dynamic, unique value per event to ensure accurate and reliable tracking.
M2O IMG Tag Parameters – Event-Specific Instructions
Each IMG tag corresponds to a specific event type.
Depending on the event, different parameters must be populated dynamically.
Below are the exact implementation requirements per event.
1. Signup Event
Purpose
Tracks a successful user registration.
Required Parameters
order
Description:
A unique identifier for the signup event.What to use:
User ID
Signup ID
Registration ID
Any internal identifier created at signup
Requirements:
Must be unique per signup
Must not be reused across users or events
Example
order={ORDER_ID}
Notes
No revenue value is required for Signup
Do not populate currency or value parameters for this event
2. FTD Event (First Time Deposit)
Purpose
Tracks the first successful deposit made by a user.
Required Parameters
order
Description:
A unique identifier for the FTD transaction.What to use:
Transaction ID
Deposit ID
Payment reference
Requirements:
Must be unique per transaction
Must never be reused
value
Description:
The deposited amount, including currency.Required format:
{CURRENCY_CODE:ORDER_VALUE}
Examples:
EUR:100
USD:50.00
GBP:25
Requirements:
Currency must follow ISO-4217 (EUR, USD, GBP, etc.)
Value must be numeric
No spaces allowed
Example
value={CURRENCY_CODE:ORDER_VALUE}
order={ORDER_ID}
3. Deposit Event
Purpose
Tracks all subsequent deposits after the FTD.
Required Parameters
The same parameters and rules apply as for the FTD event.
order
Unique transaction or deposit ID
Must be unique per deposit
value
Deposit amount, including currency
Format:
{CURRENCY_CODE:ORDER_VALUE}
Example
value={CURRENCY_CODE:ORDER_VALUE}
order={ORDER_ID}
Important Implementation Rules
Do not use static values
Do not reuse order IDs across multiple events
Do not send empty or zero values unless explicitly intended
Incorrect implementation may result in:
Missing conversions
Incorrect revenue reporting
Suboptimal campaign optimization