Customer-Permissioned Retail Connector

Evidence-aware by design.

The product makes it clear what is connected, what is imported, what is eligible, and what remains a directional observation.

Trust & Methodology

Make the mechanism clear before the claim.

Permission

Explicit and revocable

Customers can see connection scope and disconnect.

Method

Source-aware and directional

A stronger causal claim needs a defined lift or attribution method.

Governance

Brand-isolated and configured

Destinations, exports, and delivery happen only with appropriate consent 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.

Trust FAQ

Plain answers about permission and evidence.

Is this scraping?

It is not unrestricted scraping. The program uses customer-authorized retrieval through specific supported methods. The shopper is shown the value exchange, scope, and disconnect path before a connection.

Does the platform collect retailer passwords?

The brand does not receive retailer passwords. Supported authentication occurs through the retailer or a supported isolated method, and raw credentials are not delivered as brand data.

What does a brand receive?

Only the program-approved, source-classified evidence and configured delivery actions needed for the stated use case. Source, period, freshness, and eligibility stay visible.

What is excluded?

A retailer sell-through import is not shopper-level confirmed purchase evidence. A supported connection is not a claim to a complete retail account history, universal retailer coverage, or unrestricted data access.

Can a shopper disconnect?

Yes. Connection scope and a revocation or disconnect path are part of the participation experience.