01
Shopper permission
A clear value exchange, connection scope, and revocation path come before data access.
Customer-Permissioned Retail Connector
A shopper chooses a retailer connection, sees the scope, and can disconnect. Brands receive only the evidence and delivery actions their program permits.
Customer-Permissioned Connector
01
A clear value exchange, connection scope, and revocation path come before data access.
02
Availability and connection health are shown per retailer. Examples do not imply universal support.
03
Evidence is classified, dated, and handled separately from imported sell-through.
04
Use eligible activity for directional measurement, a supported loyalty pilot, or configured impact participation.
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.
What customer permission looks like
The browser extension is one currently available participation surface. It can pair retailer choice with a clear program benefit, while other methods remain a supported-pilot decision.
Retailer availability, connected state, and program value are shown only where a supported experience is configured.
A managed pilot first
Start with a single answerable question and the participation surface that fits the approved program.
Invite shoppers through an approved campaign or program link.
Available nowPlace the participation step in an approved brand web experience.
Supported pilotUse a hosted flow when it best fits the pilot scope.
Supported pilotReview source-aware results, then choose the next test.
Configured destination