A Facebook lead generation account sends one standard event per form, and for most lead forms that event is Lead. CompleteRegistration fits webinar and account sign-ups, Schedule fits a booking made inside the form flow, SubmitApplication fits applications, Contact fits call or chat clicks. Send the same event name from the Meta Pixel and the Conversions API, so one submission is counted once.
Pick the event by the offer, not by the form field
Meta defines 17 standard events, and the Pixel adds PageView on its own. Six of the 17 describe something a lead generation business does, and each one names a different moment.
| What the visitor is offered | Event | How Meta describes it |
|---|---|---|
| A quote, a callback, a consultation, a contact form | Lead | a submission of information with the understanding that the person may be contacted later by your business |
| A webinar place, an event, an account created | CompleteRegistration | a completed registration form |
| A booking made inside the form flow | Schedule | a person books an appointment to visit one of your locations |
| An application for a course, a job or a credit product | SubmitApplication | a person applies for a product, service or program you offer |
| A call or a chat, when contact itself is the conversion | Contact | a person starts contact with your business by telephone, SMS, email or chat |
| A free trial of a product | StartTrial | a person starts a free trial of a product or service |
The choice follows what the reader did, not what the form looks like. A form with three fields that ends in “send me my quote” is a Lead. The same three fields behind “book your slot” are a Schedule. Spelling matters as much as the choice: write the name exactly as Meta writes it, in the browser and on the server, because a near match is a different event.
Why Lead covers most lead generation accounts
The other eleven standard events name commerce and site actions: AddToCart, AddPaymentInfo, AddToWishlist, CustomizeProduct, Donate, FindLocation, InitiateCheckout, Purchase, Search, Subscribe and ViewContent. None of them describes a person who asked to be contacted. ViewContent is the one agencies reach for when nothing else fits, and it records a visit to a URL you care about without saying what the visitor did there. It is fine for building audiences and useless as a lead.
Lead also has a structural advantage. It is an event Meta expects from the Leads objective, and that objective is the only place where Maximize number of leads and Maximize number of qualified leads appear as performance goals. The Facebook ads objectives guide sets out how the objective decides which conversion locations and events your ad set can optimize for.
There is one number to respect. Meta’s best practices ask for an optimization event that happens about 50 times a week at a minimum, because the ad set needs that many events to learn. An account that receives 12 leads a week is asking the delivery system to optimize on very little, whatever the event is called.
One event per form, and one firing point per submission
A landing page that fires Lead, CompleteRegistration and Contact for the same form gives Meta three conversions to learn from and gives you three numbers to reconcile. Meta’s own setup checklist points the same way: typically one conversion event, with extra events only when a different user action triggers them.
The firing point is the second half of the rule. The common shortcut is to attach the event to the submit button, and on a lead form a click is not a lead:
- it fires when validation fails, for example on a phone number in the wrong format;
- a double tap on a slow connection fires it twice;
- your server can still reject the submission as spam or time out.
Fire the event after the server has accepted and saved the lead, in the success callback of the submit request or on a confirmation screen that only a successful submission can reach. That single choice is the difference between an event count and a lead count.
The same event name in the browser and on the server
Two copies of one submission are normal once the Pixel and the Conversions API both send the event. Meta pairs them only when the names and the IDs agree, and the pairing happens inside 48 hours on the same Pixel.
| Pixel copy | Server copy | What Meta sees |
|---|---|---|
| Lead, eventID lead_8c1f | Lead, event_id lead_8c1f | one Lead |
| Lead | CompleteRegistration | two events for one submission, and an ad set optimized for Lead sees only the browser copy |
| trackCustom with QuoteRequest | quote_request | two custom events that never pair |
| Lead, no event ID | Lead, with an event ID | nothing to pair on, and the fallback identifiers work only if the browser event lands first |
Three habits keep the names straight. Define the event name in one place and have the landing page and the server read it from there. Prefer a standard event to a custom one, since a custom event needs a custom conversion and a standard event category before it can be a goal. And after any change, compare the Lead count in Events Manager with the submissions your forms recorded.
A setup order that keeps the counts straight
- List the forms you run and write one event name next to each, using Meta’s spelling.
- Create the event on the server, in the success path of the submission, with an ID derived from the lead itself.
- Fire the browser copy with the same name and the same ID. The Meta Pixel setup guide covers the base code, the
<head>placement and advanced matching. - Send the click identifier and the browser identifier with the server event, so the submission can be matched to the ad click that produced it.
- Submit the form once with Test Events open in Events Manager, and confirm the name, the parameters and the event ID.
- After a week, compare the event count with your own submissions. A small gap comes from consent banners, blockers and duplicate clicks, and the gap is worth knowing before anyone reads a cost per lead.
When a custom event or a custom conversion is worth adding
A custom event names a step of your own, such as a form started or a calendar opened, and it is a reasonable second event when you want to see where visitors stop. It cannot be an optimization goal on its own: it first needs a custom conversion built on it with a standard event category.
Custom conversions filter events Meta already received, by URL or by parameter, and they are the right tool for a subset of leads. A business with one dataset and two offers can build “Lead where the service is a boiler” and report on it, while the ad set keeps optimizing for Lead. Treat that as reporting first. Moving an ad set onto the subset changes its optimization event, which restarts the learning phase, and a subset below roughly 50 events a week leaves too little to learn from. The differences are set out in custom conversions vs standard events.
Then the arithmetic that decides whether the account can see any of this: per ad, per creative and per landing page, on leads you actually received.
DropCPL sends the standard Lead event to Meta through the Conversions API with a shared event ID, and counts every lead on the landing page that received it, so the cost per lead you read is built from submissions rather than from a modelled count. The rest of the tracking questions, from deduplication to attribution windows, are collected in Meta Pixel, Conversions API and attribution.