Create a Meta custom conversion and attach it to a pixel event via the Marketing API

domain: developers.facebook.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Create a custom conversion via POST /{ad_account_id}/customconversions with a name, pixel_id, and rule; the rule is a JSON filter object that matches pixel events by event name and optional URL or parameter conditions.
  2. Set the custom_event_type to one of Meta's standard categories (e.g., PURCHASE, LEAD, ADD_TO_CART) to enable reporting in standard conversion columns; use OTHER if the event does not map to a standard type.
  3. Optionally set a value_type to CONSTANT (and supply a custom_event_values array) or USE_VALUE if your pixel fires a currency value; this controls how conversion value is attributed.
  4. Reference the custom conversion ID in the ad set's promoted_object.custom_conversion_id to optimize campaigns toward it; ensure the ad set's optimization_goal is OFFSITE_CONVERSIONS.
  5. Verify the custom conversion is receiving data by checking its status via GET /{custom_conversion_id}; the last_fired_time field shows the most recent pixel event that matched the rule.
  6. Test the rule logic using the Meta Pixel Helper browser extension before going live; incorrect URL match conditions are a common cause of zero-firing custom conversions.

Known gotchas

Related routes

Send server-side conversion events to Meta's Conversions API with Pixel deduplication
advertising · 6 steps · unrated
Send server-side events via Meta Conversions API
developers.facebook.com/docs/marketing-api/conversions-api · 6 steps · unrated
Send server-side conversion events to Meta Conversions API (CAPI)
developers.facebook.com/docs/marketing-api · 6 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans