Skip to content
Menu

Amperity and Criteo: Criteo audiences from customer data

Amperity sends first-party audiences to Criteo Commerce Growth and Criteo Retail Media through separate destinations. Build segments from customer history, choose the appropriate account and identifier configuration, and validate audience availability before activating campaigns.

Get a demoSee the Criteo docs

Criteo logo

What teams can do with Amperity and Criteo

Build Criteo audiences using online and in-store purchase history.

Distinguish recent buyers from customers ready for a new offer.

Activate segments in the appropriate Commerce Growth account.

Support onsite and offsite Retail Media audience strategies.

Refresh membership with the behavior specific to each destination.

Evaluate offline sales through a separately configured events path.

How Amperity and Criteo connect

1. Select a customer segment

Use purchase, engagement, or lifecycle attributes in Amperity and apply your activation exclusions.

2. Choose the Criteo destination

Use Commerce Growth for its audience workflow or configure Criteo Retail Media for the required onsite or offsite use case.

3. Validate membership and availability

Check the audience in the chosen Criteo account before applying it to a campaign; the two audience destinations use different update behavior.

Identity and matching for Criteo audiences

Amperity's unified customer context supports audience selection; Criteo determines downstream matching. Commerce Growth uses email lists, while Retail Media identifier requirements depend on onsite or offsite configuration. Audience membership, matched customers, and eligible ad delivery are separate results; no fixed match-rate improvement is promised.

What the Criteo connection supports

Capability

Supported behavior

Commerce Growth method

Amperity → Criteo API; audience lists use email. Invalid email rows are filtered and counted in workflow logs.

Commerce Growth refresh

Full replacement: the existing audience is cleared before the current membership is added.

Retail Media method

Separate Commerce Yield destination; onsite and offsite audiences require independent configurations.

Retail Media refresh and limits

Incremental additions and removals; up to 24 hours for availability. A minimum 0.1% match rate is documented.

Retail Media identifiers

Onsite: CustomerId. Offsite: use the identifier required by the destination and campaign configuration.

Offline sales options

Legacy CSV/TSV through SFTP; separate Criteo Offline Sales beta for retail media with a two-day transaction window.

What teams do with Amperity and Criteo

Retarget customers with a relevant next offer

Identify customers who bought a product or category and have not made a relevant follow-up purchase. Send that segment to the appropriate Commerce Growth audience, then pair it with an offer selected by the media team. Keep recent purchases and exclusions in the source criteria so subsequent sends reflect the current customer relationship. Validate membership after each important change because this destination replaces the previous audience with the new list.

Make retail audiences useful across placements

Create customer segments that reflect a specific retail objective, such as repeat purchasing or interest in a category. Work with the retail media owner to choose onsite or offsite activation and the identifier that configuration requires. Send each audience through its own configured Retail Media destination and check availability before launch. This gives the media team a shared customer definition while keeping placement choices and campaign execution within Criteo.

Connect store transactions to retail media evaluation

For an approved Criteo Offline Sales beta implementation, select recent transaction line items and align product identifiers with the catalog feed used by Criteo. Validate the destination with the Criteo Account Strategist before scheduling sends. Review data arrival timing because the connector skips transactions outside its two-day window. Keep this workflow distinct from the established SFTP file route, whose setup and attribution requirements must be evaluated separately.

Setting up the Criteo connection

Choose the audience connector before authorizing access: Commerce Growth uses its advertiser configuration, while Retail Media requires its own OAuth, account, retailer, and campaign-specific identifier settings. Validate a sample in the correct Criteo account before sending the production audience.

For the beta Offline Sales path, each line item needs transaction and product details plus a shopper identifier. Amperity hashes email automatically; catalog matching and attribution need validation in Criteo. An accepted request does not confirm the configured account received or attributed the sale; verify with your Criteo Account Strategist.

See the Criteo docs

Criteo integration FAQs

Put customer context to work in Criteo

Explore how Amperity can connect your customer data to the audience workflow your team needs.

Get a demo