What Is a Repeat Conversion?
A repeat conversion occurs when the same user (pub_member_id) completes the same event more than once.
Allowing Repeat Conversions enables publishers to track, reward and report on events that can occur multiple times per user, such as purchases or repeatable in-app actions.
Use Case & Example
This feature is designed for events that occur multiple times for a single user, such as in-app purchases or app opens.
For example, if an advertiser sends a postback every time a specific eventID is triggered, the offer will track each subsequent action as a repeatable event.
How it Works
If Allow Repeat Conversions is Disabled:
Only the first conversion is recorded.
Any additional purchases will still appear in the history log, but with a warning that the user has already completed the event.
A callback is still sent for each repeat instance, but the conversion is not treated as a new event.
If Allow Repeat Conversions is Enabled:
Each purchase will generate a new conversion ID
A callback is sent for each repeat instance to your server with a unique identifier in the
conversionIdfield.
Allowing Repeat Conversions
Allow Repeat Conversions Toggle
Default state:
OFF.OFF: Only the first conversion is recorded; additional attempts are logged with a warning in history logs.ON: Each repeat conversion is recorded
Conversion Management Table
Displays the number of completions per event when repeat conversions are enabled.
Conversion Status
Repeat conversions inherit the status of the initial conversion.
Statuses for repeat conversions are not yet configurable individually.