Customer-Permissioned Retail Connector

A connection is not a blank check.

Trust is designed into the experience: explicit permission, scoped evidence, visible freshness, revocation, and brand isolation.

Data connections & trust

Make the mechanism clear before the claim.

Connection scope

The shopper stays in control

Connection state, retailer scope, errors, and disconnect options are communicated in the experience.

Evidence

Classify before you compare

Observed, imported, and eligible confirmed activity are not presented as the same thing.

Destinations

Configuration before delivery

Webhook, loyalty, CRM, and audience destinations depend on consent, permissions, and setup.

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.