Ads Conversions icon

Ads Conversions

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

Actions5

Facebook Conversions → Send Complete Registration Event

AI-generated

Summary

Send a CompleteRegistration conversion event to Facebook's Pixel via the Facebook Conversions API, including optionally hashed customer data and custom event details.

Inputs

  • Pixel ID (required) — The Facebook Pixel ID to send events to
  • Action Source (required) — Where the conversion took place; e.g., website, app, email, etc.
  • Event Time (required) — The time when the event occurred; accepts date/time string and converts to Unix timestamp
  • Event ID — Unique identifier for deduplicating events between Pixel and server
  • Event Source URL — The browser URL where the event happened; required if Action Source is website
  • Test Event Code — Code from Facebook Events Manager to mark the event as test, excluding it from ads data
  • Opt-Out of Ads Delivery Optimization — Flag to use this event only for attribution purposes, not ad delivery optimization
  • Data Processing Options Country — Country code for data processing options (1 = US, 0 = geolocate)
  • Data Processing Options State — State code for data processing options (1000 = California, 0 = geolocate)
  • User Data — Collection of customer PII fields (email, phone, name, location, etc.) automatically normalized and SHA256-hashed before sending
  • Custom Data — Additional event-related data such as value, currency, content name/category, and registration status

Output shape

a JSON object representing Facebook's API response, augmented with details of the sent payload and optional warnings

Events include hashed user data for matching. If action source is website and event source URL is missing, a warning is added. At least one user data field is recommended for effective matching.

Links

Discussion