Meta Pixel, Conversions API and attribution

Which parameters does each Facebook standard event take?

Meta lists the optional properties for each of its 17 standard events: Lead takes currency and value, Purchase requires both, and six events take none.

Published

Every Facebook standard event takes an event name plus an optional object of properties, and Meta’s reference lists which properties each event accepts. Lead and CompleteRegistration take currency and value, Purchase requires both, the commerce events take content identifiers and item counts, and six events take no properties of their own. The name and the object are the same in the browser and on the server.

One event name, one property object

The Meta Pixel sends a standard event with fbq('track', 'Lead', {properties}) and a custom event with fbq('trackCustom', ...). The object in the middle carries the details that later appear in reporting, in audience rules and in custom conversion filters. Meta marks that object optional for every standard event except Purchase, where currency and value are required.

Three habits keep the object honest:

A second set of values sits outside the property object: the identifiers for advanced matching, passed in fbq('init', 'PIXEL_ID', {em: 'hashed email', ph: 'hashed phone'}). Meta’s documentation says to place them in the base code, or they are not treated as manual advanced matching values. On a lead form the base code runs before the visitor types, so automatic advanced matching in Events Manager is the practical route, with the server event carrying the details from the form (Event Match Quality).

The properties Meta lists for each standard event

This is Meta’s list, with the commerce and site events at the bottom:

Standard eventObject properties
Leadcurrency, value
CompleteRegistrationcurrency, value
StartTrialcurrency, predicted_ltv, value
Subscribecurrency, predicted_ltv, value
Purchasecontent_ids, content_type, contents, currency, num_items, value; currency and value are required
AddToCartcontent_ids, content_type, contents, currency, value; contents required for Advantage+ catalog ads
AddPaymentInfocontent_ids, contents, currency, value
AddToWishlistcontent_ids, contents, currency, value
InitiateCheckoutcontent_ids, contents, currency, num_items, value
ViewContentcontent_ids, content_type, contents, currency, value
Searchcontent_ids, content_type, contents, currency, search_string, value
Contactnone listed
Schedulenone listed
SubmitApplicationnone listed
CustomizeProductnone listed
Donatenone listed
FindLocationnone listed

Every row but Purchase is marked optional. An event that arrives without properties is still a valid event, it just tells Meta less, and a custom conversion rule cannot filter on a value that never arrived.

The reference also maps each event to a custom_event_type for the promoted object, which is what the Marketing API expects: LEAD, COMPLETE_REGISTRATION, SCHEDULE, SUBMIT_APPLICATION, CONTACT and START_TRIAL among them. If you build campaigns with scripts, those six strings are how an ad set is pointed at the event you chose.

The six events a lead generation account sends

EventProperties to sendWhat goes in them
Leadcurrency, valueleave both empty unless the submission itself has a price
CompleteRegistrationcurrency, valuesame rule, for a sign-up or a webinar place
Schedulenonethe moment is the booking, and Meta asks for no property
SubmitApplicationnonean application, with nothing to price yet
Contactnonea call or a chat click, when contact is the conversion
StartTrialcurrency, value, predicted_ltvthe forecast value of the person, if you have one

A quote form has no price at submission, so value stays empty. A placeholder such as 1 or 0 does not make reports richer, it makes them wrong: whatever you send follows the event into every view that uses it. StartTrial is the one case where a forecast belongs to the moment, and predicted_ltv is where Meta expects it.

The same parameters on the server

A Conversions API event carries the properties inside custom_data, next to fields the browser event does not need:

Server fieldRequiredWhat it holds
event_nameyesthe standard event name, spelled as in the reference
event_timeyeswhen the event happened, in Unix seconds, GMT, up to 7 days before sending
user_datayesthe hashed customer information used for matching
action_sourceyeswhere the event happened, for example website, phone_call or chat
event_source_urlfor website eventsthe URL where the event happened, on the verified domain
event_idnothe shared ID that pairs this copy with the browser copy
custom_datanothe object properties, such as currency and value
event_name: Lead
event_id: lead_8c1f
custom_data: currency, and value only if the form takes a payment

The pairing works only inside 48 hours and only when the names match, so a Lead sent as CompleteRegistration from the server is a second event rather than a duplicate. Deduplication by event_id is covered in the deduplication guide linked above; the customer information that goes in user_data is the subject of Meta Pixel, Conversions API and attribution.

A parameter setup for one lead form, step by step

  1. Pick the event from what the visitor is offered, not from the fields. A quote or a callback is Lead, a webinar place is CompleteRegistration.
  2. Decide whether the submission has a value today. For a quote form the answer is no, so currency and value stay out of the code.
  3. Fire the event after your server has accepted the form, so a failed validation or a double tap cannot produce a conversion.
  4. Generate one ID per lead, send it to the server with the form data, and pass it as eventID in the browser and event_id on the server.
  5. Add the click and browser identifiers to the server event, so the submission can be matched to the ad click behind it.
  6. Submit the form once with Test Events open in Events Manager, and read the payload it received. If a property is missing there, it is missing everywhere.

Where these properties show up later

Custom conversion rules are built on an event and then filtered, by URL or by the properties the event carries. A business that runs boiler work and bathroom work on one dataset can report “Lead where the service is boiler” without a second event, as long as the property or the URL it filters on is actually present. Meta’s advice for the missing case is to update the Pixel or the Conversions API setup so the event carries it, and custom conversions vs standard events sets out the limits of that route, including the 100 per ad account cap.

The same properties decide what audiences you can build and how much detail sits in a report. A Lead counts the same with or without value, but a report that splits leads by service needs the split to arrive with the event. Where the base code goes and when the event should fire is covered in the Pixel setup guide.

DropCPL sends the Lead event through the Conversions API with a shared event ID, then counts the leads your landing pages received, so the cost per lead it reports comes from those leads.

Questions on this topic

All questions on this topic →

FAQ

Does the Lead event need a value?+

No. Meta lists `currency` and `value` as optional properties of Lead, and only Purchase requires them. If your form does not take a payment, leave both out instead of typing a placeholder number, because whatever you send follows the event into reporting.

Can I send my own parameter with a standard event?+

Meta defines the properties for each standard event, so a name of your own is not part of that event. If you need a custom detail for a custom conversion rule, build it on the Lead event and filter by a URL or by a property Meta already documents.

Are the parameters the same in the pixel and in the Conversions API?+

The properties travel inside `custom_data` on the server, so `currency` and `value` keep their names. The server event also needs fields the browser event does not, such as `event_time`, `action_source` and the customer information in `user_data`.

What happens if a standard event arrives with no properties?+

Meta still records the event and counts it as a conversion. It reports less detail, and a custom conversion rule cannot filter on a property the event does not carry.

Ready to find out what
converts, for real?

Free to start.

Start free →