Customer-Permissioned Retail Connector

The customer-permissioned connector, explained.

The connection starts with a shopper decision. It can then create scoped, classified evidence for measurement, supported loyalty pilots, or configured impact participation.

See a sample report Design a supported pilot

Connector Guide

Make the mechanism clear before the claim.

Permission

What the shopper agrees to

The experience names the program, scope, and disconnect path before connection.

Evidence

What the brand can read

The program distinguishes imported reporting from eligible confirmed connector activity.

Outcome

What may happen next

Any loyalty, CRM, webhook, audience, or impact action must be permitted and configured.

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.

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.

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.

A managed pilot first

Launch through what you already use.

Start with a single answerable question and the participation surface that fits the approved program.

Configured link

Invite shoppers through an approved campaign or program link.

Available now

Approved embed

Place the participation step in an approved brand web experience.

Supported pilot

Hosted experience

Use a hosted flow when it best fits the pilot scope.

Supported pilot

Configured reporting

Review source-aware results, then choose the next test.

Configured destination