Set opt-in for a receipt challenge
How opt-in scope applies to receipt challenges and where to configure it.
A receipt challenge often collects personal data, purchase evidence, or both. That means opt-in matters just as much here as it does for a game or a booking flow.
In OmniLab, opt-in is usually managed at campaign level. When the campaign uses touchpoint-level scope instead, the receipt challenge can have its own dedicated opt-in configuration.
Opt-in usually lives outside the receipt-game tabs
You do not normally configure consent text from the receipt-game Appearance or Configuration tabs. Instead, continue in the Platform opt-in guides below.
When to keep campaign-level scope
Keep opt-in at campaign level when the same consent wording should cover every touchpoint in the campaign, including the receipt challenge.
A typical example is a summer promotion where one landing page, one wheel game, and one receipt challenge all feed the same CRM purpose.
When to switch to touchpoint-level scope
Use touchpoint-level opt-in when the receipt challenge collects something materially different from the other campaign touchpoints, such as proof of purchase, extra retailer data, or a dedicated post-purchase marketing permission.
Next steps
About opt-in in OmniLab
Understand the opt-in model before you configure the receipt challenge.
Enable opt-in and choose scope
Turn opt-in on and choose Campaign Level or Touchpoint Level.
Configure opt-in at campaign level
Use one shared consent setup across the full campaign.
Configure opt-in at touchpoint level
Give this receipt challenge its own consent configuration when needed.