Skip to content
Menu

Offline conversion tracking with Amperity

Send eligible purchases and customer events from Amperity to supported advertising platforms through their configured event connectors, combining transaction details with available customer identifiers to support matching and conversion measurement in each destination.

Get a demoMeta events docs

Conversion events • Customer matching • Platform-specific delivery

Bring purchases beyond the website into advertising measurement

Include eligible store purchases in Meta conversion reporting.

Send offline conversion signals to a Google Ads conversion action.

Connect recent store transactions to TikTok campaign measurement.

Deliver offline checkout events for Pinterest reporting.

Give Snapchat campaigns eligible offline purchase signals.

Provide supported transaction data for The Trade Desk or Criteo measurement.

How offline conversion data reaches each advertising platform

  1. Select eligible events. Query available customer and transaction data, applying consent criteria and the destination’s supported event-age window.

  2. Map the receiving platform’s fields. Include its required identifiers, timestamp, event type, and purchase fields; configure the exact event connector.

  3. Validate delivery and results. Run a sample, inspect errors and destination reporting, then schedule the validated workflow.

Each connector applies its own mapping and delivery rules. Audience membership and conversion-event delivery are separate workflows.

The delivery branch depends on the configured connector. File workflows can include a separate upload step.

Give each platform the identifiers it can use

Event matching depends on the customer identifiers available in your data and accepted by the destination. Select relevant fields and follow that connector’s normalization and hashing rules. A hashed identifier still requires appropriate consent and permission to share; hashing alone does not establish eligibility.

What offline conversion delivery supports

Capability

Supported behavior

Direction

Amperity sends selected events to configured advertising destinations.

Payload

Customer identifiers plus event timestamps and destination-specific purchase or event fields.

Matching

Destination-specific identity rules; no universal identifier or match-rate guarantee.

Delivery

API event connectors or file workflows, depending on the chosen destination and path.

Refresh

Query orchestrations on a validated schedule; receiving-platform processing is separate.

Results

Delivery status and platform reporting must both be checked; acceptance does not prove attribution.

Choose the correct event route

Platform

Documented path and qualification

Meta

Conversions API for events. Use a consolidated dataset and follow the documented event-age rules for the selected event source.

Google Ads

Google Enhanced Conversions (GDM) uses the Google Data Manager API. Each send submits conversions to a configured conversion action.

TikTok

TikTok Events API supports offline and web events. Offline events require email or phone and a timestamp.

Pinterest

Conversions API sends offline checkout events from the previous seven days.

Snapchat

Snapchat Offline Events uses the Conversions API. Amperity hashes supported identifiers; mobile advertising IDs remain unhashed. The manual CSV route requires a different query.

Criteo

Commerce Growth transaction files use SFTP. The separate Criteo Offline Sales connector is in beta and accepts recent retail-media transaction line items.

The Trade Desk

Offline-event delivery uses a separate connector. Confirm eligibility and setup requirements with your Amperity representative.

Use transaction signals to improve the next measurement decision

Include store purchases in platform reporting

A retailer can select recent store purchases, associate them with available customer identifiers, and send the eligible events to Meta or Pinterest. This gives the receiving platform transaction signals beyond website activity. The team can check which conversions were matched and credited within its configured attribution window, using that reporting alongside other evidence when evaluating campaigns and planning its next media investment.

Give Google Ads conversions without a click ID

An eligible team can use the configured Google Enhanced Conversions (GDM) connector for in-store purchases or phone bookings where no ad-click identifier exists. Amperity hashes the supported email and phone values and submits the conversions to the configured action. Review results in Google Ads after matching completes, then decide how that conversion action should inform the account’s measurement and bidding settings.

Keep retail-media event delivery within its window

For the beta Criteo Offline Sales path, plan the transaction feed around its two-day acceptance window. Align product IDs with the catalog and check arrival with your Criteo Account Strategist after the first send. This helps the team identify late data, missing products, or account-configuration problems before relying on retail-media reporting.

The Commerce Growth SFTP workflow remains a distinct option with its own requirements.

Set up and verify the event connection

Ask your Datagrid Operator or Amperity representative to configure the exact destination, credentials, receiving account, and required dataset or conversion action. Agree on the event definition, consent filters, recent-event query, and deduplication fields before scheduling delivery.

Send a sample and verify it in the destination. Check purchase values, timestamps, identifiers, and duplicates as well as Amperity’s delivery result; processing and attribution can continue after a send completes. Follow the platform-specific guides below.

Offline conversion tracking FAQs

Bring more purchase signals into your advertising decisions

Explore which event connections fit your customer data and measurement goals.

Get a demo