Amperity and Meta: Meta Conversions API and audiences

Q: Does Amperity support both Meta Custom Audiences and the Conversions API?

Yes. The audience path uses the Facebook Marketing API to manage Custom Audiences. The separate event path sends eligible transactions through the Conversions API. Configure and validate each workflow for its own identifiers, permissions, and required fields.

Q: Does an audience update append customers or replace membership?

The documented audience destination uses Meta’s Replace Users endpoint. It replaces prior membership with the current customer list, so review the complete intended audience before sending. This behavior does not describe the event-delivery connector.

Q: Which customer identifiers can I use?

The audience connector supports documented email, phone, name, location, birthdate, gender, external-ID and mobile-advertising fields. Configure only the required and permitted attributes for your workflow. Event queries follow the event connector’s separate field requirements.

Q: How long do Meta audience updates take?

Allow up to 24 hours after Amperity finishes sending an audience update for it to be available in Meta Ads Manager. Your Amperity schedule and Meta processing are separate parts of the total refresh time.

Q: Can I send historical offline purchases?

Normal event updates cover the previous seven days. The Meta event guide documents a first-send exception for physical_store events. Confirm the applicable setup before attempting a backfill rather than treating that exception as an ongoing historical-data window.

Send customer audiences to Meta Ads Manager through the Facebook Marketing API and eligible purchase events through the Meta Conversions API, using customer identifiers from Amperity to support audience matching and offline conversion measurement.

Get a demo See the Meta docs

Custom Audiences • Conversions API • Separate delivery paths

Put your customer selection to work in Meta

Reach repeat-purchase audiences defined by available purchase history.

Exclude recent buyers from eligible acquisition campaigns.

Build retention audiences around loyalty and engagement criteria.

Keep Custom Audiences aligned with refreshed segment membership.

Supply eligible offline purchases for Meta conversion reporting.

Give your media team a consistent customer definition for audience selection.

How Amperity connects to Meta

Define the audience or event set. Use an Amperity segment for audience membership or a query for eligible transaction events.
Configure the correct path. Use the audience destination for Custom Audiences and a separately configured event destination for purchase signals.
Validate and refresh. Check a sample in Meta, then schedule the workflow and review destination processing.

Audience activation and offline-event delivery use separate configurations.

Align identity with the Meta workflow

Select the supported identity fields your customers have provided and apply consent criteria before sending. Audience matching and event matching use different schemas. Amperity hashes the audience connector’s specified identity fields automatically; follow the event guide for event payload requirements.

What the Meta connection supports

Capability	Supported behavior
Audience delivery	Facebook Marketing API, Replace Users endpoint; current membership replaces the prior audience.
Audience identity	Supported contact, location and mobile advertising fields; configured external ID required by the campaign setup.
Event delivery	Conversions API for events; consolidated Meta dataset required.
Event window	Normal updates use the previous seven days; initial physical_store delivery has a documented exception.
Refresh	Scheduled Amperity workflows; allow up to 24 hours after sending for audience updates.
Authentication	Meta OAuth, account ID and accepted Custom Audience terms; event dataset configured separately.

Use customer context for the next media decision

Suppress recent buyers from acquisition

Define a recent-buyer segment from the purchase data available in Amperity, then deliver it as a Meta Custom Audience for exclusion where the campaign supports it. Your media team chooses the exclusion settings in Meta Ads Manager. Refreshing membership helps keep the exclusion aligned with the segment definition as customers buy, rather than relying on a static uploaded customer list.

Reconnect with customers due for a follow-up

Build an audience using purchase recency, relevant product history, or loyalty criteria available in your customer data. Send the eligible matching fields to Meta and use the Custom Audience in a retention campaign. The team still chooses creative, placements, budget, and timing in Meta; Amperity supplies the audience definition and delivery workflow that keep the customer selection grounded in your data.

Include store purchases in conversion reporting

Select eligible store transactions and associate them with available customer identifiers for the separately configured event destination. Include the required purchase fields and apply the supported event-age window before delivery. Check the received events and reporting in Meta after processing. These signals can support platform measurement, but a delivered event alone does not establish that advertising caused the purchase.

Set up and validate the connection

Ask your Datagrid Operator or Amperity representative to configure the audience destination, Meta account and OAuth access. Accept Meta’s Custom Audience terms and verify the configured external identifier and supported matching fields before your first audience send.

For conversions, configure the event destination and a consolidated dataset. Validate timestamps, purchase values and identifiers with a sample; normal updates maintain the seven-day event window. Keep event delivery separate from audience replacement and inspect results in Meta.

Audience setup docs Event setup docs

Meta integration FAQs

Does Amperity support both Meta Custom Audiences and the Conversions API?

Does an audience update append customers or replace membership?

Which customer identifiers can I use?

How long do Meta audience updates take?

Can I send historical offline purchases?

Keep Meta audiences and purchase signals aligned with your customers

Explore a connection that fits your audience strategy and conversion-measurement needs.

Get a demo