Media inputs
Configured platform and file imports
Use platform delivery or imports according to the account access and mapping available.
Customer-Permissioned Retail Connector
Use each source for what it can support.
A useful retail view starts with clear connection boundaries and continues with visible mapping, freshness, and evidence status.
Data Connections
Make the mechanism clear before the claim.
Retail inputs
Imports and permissioned connections
Imported sell-through and shopper-permissioned evidence remain separately labeled.
Destinations
Consent-approved delivery only
CRM, webhook, audience, and loyalty destinations remain conditional on consent and configuration.
Illustrative exampleMedia import + retailer sales import + consented connector evidenceExample reporting period: April–JuneFreshness: shown as reported by each configured source
Media and sales comparisons are directional unless a defined lift or attribution method supports a stronger conclusion.
A real participation surface
Make the connection method visible.
The existing Oui Impact browser experience can make retailer choices and participation value visible. Other connection methods remain program-specific and clearly labeled.
01Offer a clear program benefit.
02Show supported retailer options and scope.
03Classify eligible evidence before any configured action.
Retailer availability, connected state, and program value are shown only where a supported experience is configured.
Supported methods
Know how the evidence entered the program.
Methods differ by retailer, program, consent, account access, and approved pilot scope. This is a support matrix, not a universal connector claim.
Extension signals
Available now- What the shopper does
- A shopper chooses the browser extension and follows the supported experience.
- Evidence it can provide
- Connection state and scoped supported activity, where available.
- Campaign context
- Only when supported mapping is present.
- Exclusions and availability
- No universal retailer coverage or complete shopping history.
Direct retailer connections
Supported pilot- What the shopper does
- A shopper reviews the retailer option, scope, and disconnect path before choosing to connect.
- Evidence it can provide
- Classified retailer activity when a supported connection is available.
- Campaign context
- Shown only when campaign mapping is available.
- Exclusions and availability
- Availability, fields, and freshness vary by retailer and pilot.
Reviewed email receipts
Supported pilot- What the shopper does
- A shopper submits or authorizes a receipt for review under the program rules.
- Evidence it can provide
- Reviewed receipt evidence at the supported detail.
- Campaign context
- Not assumed; depends on approved receipt and campaign mapping.
- Exclusions and availability
- Not a universal inbox connection or a complete purchase record.
User-authenticated browser sessions
Planned expansion- What the shopper does
- A shopper authenticates in their own supported browser session and sees the experience scope.
- Evidence it can provide
- Scoped activity available through the supported session method.
- Campaign context
- Only when the supported method preserves it.
- Exclusions and availability
- No password collection by this site, and no broad account access claim.