Ads Conversions icon

Ads Conversions

Send conversion events to Facebook (Meta) Conversions API and Google Ads. Auto-hashes PII fields.

Actions5

Facebook Conversions → Send Purchase Event

AI-generated

Summary

Send a purchase conversion event to a specified Facebook Pixel using the Meta Conversions API by providing purchase details and customer user data.

Inputs

  • Pixel ID (required) — The Facebook Pixel ID to send events to.
  • Action Source (required) — The origin where the conversion occurred (e.g., website, email, app).
  • Event Time (required) — Timestamp of when the purchase event happened (automatically converted to Unix timestamp).
  • Event ID — Unique ID to help deduplicate events between Pixel and server.
  • Event Source URL — URL of the webpage where the event took place (required if Action Source is 'website').
  • Test Event Code — A Facebook Events Manager code to mark the event as a test (excluded from ads reporting).
  • Opt-Out of Ads Delivery Optimization — If set, event will be used only for attribution, not for ad delivery optimization.
  • Data Processing Options Country — Country code for data processing options (1 for US, 0 for auto-geolocation).
  • Data Processing Options State — State code for data processing options (1000 for California, 0 for auto-geolocation).
  • User Data — Customer identifying information including email, phone, name, location, and browser details; personally identifiable information is normalized and SHA256-hashed before sending.
  • Purchase Data — Details about the purchase including monetary value, currency, product info, number of items, and order ID.

Output shape

a single JSON object

Returns the Facebook API response with the sent event payload details and warnings if required fields like event_source_url for website action source or user data are missing or empty.

Examples

Example 1: Sending a purchase event to Facebook Pixel with customer and purchase details

Provide Pixel ID, specify 'website' as Action Source, set Event Time, optionally include Event ID and Event Source URL, provide user data like email and phone, fill purchase data with value, currency, content IDs, number of items, and order ID, and optionally include Test Event Code or data processing options to comply with privacy laws.

Links

Discussion