Which Meta Events to Send for Lead Gen: Contact, Lead, SubmitApplication, Purchase
Which Meta standard events should a lead generation business send from its CRM? What Contact, Lead, SubmitApplication and Purchase mean in Meta's own definitions, how to map them to sales stages, and when Schedule or a custom event fits better.
Written by Qualimize Team
Founder, Qualimize
- Published
- Last updated
- Reading time
- 10 min read
Table of contents
- 01 The short answer
- 02 What Meta says each event means
- 03 Mapping the events to a sales pipeline
- 04 Industry examples
- 05 Which event should your campaigns optimise for?
- 06 When to use a custom event instead
- 07 Common mistakes when choosing events
- 08 Reading the events once they arrive
Full article
The short answer
For a lead generation business, send four Meta standard events from your CRM: Contact when a lead is reached, Lead when they show real interest, SubmitApplication when they are ready to buy, and Purchase when they pay. Together they give Meta a ladder of signals from a reachable lead to a paying customer. Only Purchase needs a value and currency.
That mapping is a convention, not a Meta rule, and it works because each event's name stays close to Meta's own definition. This guide goes through what each event officially means, how it fits a lead business, and the cases where a different event is the better choice.
What Meta says each event means
Meta publishes a definition for every standard event in its Pixel reference, and the same names are used by the Conversions API. Using the definitions as written keeps your data readable to anyone who opens Events Manager later, including an agency or a new marketer.
Contact is defined as when a person initiates contact with your business via telephone, SMS, email, chat and so on. Lead is defined as when a sign-up is completed. SubmitApplication is when a person applies for a product, service or program you offer. Purchase is when a purchase is made or checkout flow is completed, and it is the only one of the four with required parameters: value and currency.
Two more are worth knowing. Schedule is when a person books an appointment to visit one of your locations, which suits clinics, showrooms and property site visits. CompleteRegistration is when a registration form is completed, which suits webinar or event sign-ups more than sales stages.
Notice that none of these definitions mention a CRM. Meta wrote them for websites and apps, where a person clicks a button. When a CRM sends them, the event describes something a sales rep observed rather than something the person clicked. That is fine, and it is how Meta's own CRM guides expect the Conversions API to be used, but it means the rep's judgement is now part of your ad data. The clearer your stage rules, the more meaningful each event becomes.
Mapping the events to a sales pipeline
A lead business rarely has a checkout, so the events have to stand in for sales stages. The cleanest approach is one event per meaningful step, in order of increasing intent.
Contact marks the first real conversation. It tells Meta the lead was a real, reachable person, which already separates good leads from fake numbers and accidental form fills. Lead marks genuine interest, the point where a rep would say this person is worth a follow-up. SubmitApplication marks the lead being ready to buy: a site visit booked or done, a counselling session completed, a quotation accepted. Purchase marks money received.
One subtlety: when someone submits an Instant Form, Meta already records that form submission on its side. Sending a CRM Lead event later is not a duplicate of the form; it is a separate, later signal that your team judged the lead genuinely interested. That is why some CRMs, Qualimize included, attach Lead to a Pre-Qualified status rather than to the moment the form arrives.
- Contact: lead reached on the phone or WhatsApp
- Lead: lead confirmed interest, budget or requirement
- SubmitApplication: lead ready to buy (visit done, quote accepted)
- Purchase: lead paid, with the amount in INR
Industry examples
The same four events fit very different businesses. The examples below are illustrations of reasonable mappings, not rules.
Example: a Pune real estate broker sends Contact when the lead answers the first call, Lead when they confirm budget and preferred area, SubmitApplication after a completed site visit, and Purchase when the booking amount is paid. A Jaipur coaching centre sends Contact after the first call, Lead after a counselling session, SubmitApplication when the student attends a demo class, and Purchase on fee payment. A visa consultancy sends Contact after the first call, Lead after the eligibility check, SubmitApplication when documents are submitted, and Purchase when the service fee is paid.
If your business is built around appointments, such as a dental clinic, Schedule can replace SubmitApplication for the booked-appointment step, because Meta's definition of Schedule matches that action exactly.
What these examples share is that each event sits one clear step further from the form than the one before. A useful test for your own mapping: could a manager look at any single lead and say, without asking the rep, which of the four events it should have triggered? If the answer is often no, tighten the definitions before you send anything. A mapping that two people would apply differently will produce events that rise and fall with who is on shift, not with who your ads are reaching.
Which event should your campaigns optimise for?
Sending an event and optimising a campaign for it are separate decisions. You can send all four events and still optimise campaigns for Instant Form leads while Meta builds up history on the deeper stages.
The trade-off is volume against meaning. Contact happens often, so Meta gets plenty of signal, but it only tells Meta the lead was real. Purchase means the most, but a small business may only record a handful a week, which is thin data for any learning system. SubmitApplication is often the useful middle: frequent enough to learn from, and close enough to a sale that leads who reach it are worth paying for.
Meta does not publish one threshold that applies to every lead business here, so the practical test is your own numbers. If a stage is reached by only a tiny fraction of leads, keep sending it, but do not expect Meta to optimise well towards it yet.
When to use a custom event instead
Custom events let you send any name you like, such as SiteVisitDone. They are useful when no standard event describes the step and you only need it for reporting or custom conversions.
For lead businesses, standard events are usually the better default. They are recognised everywhere in Meta's tools without extra setup, and the four above cover the steps most Indian lead businesses track. Use a custom event only when a stage genuinely does not fit any standard definition, and keep the names short and consistent.
The exception is Meta's Conversion Leads performance goal. Its payload specification treats event_name as a free-form field for your CRM's own stage names, with extra required fields. If you are setting that up, follow that specification rather than the standard event mapping.
Common mistakes when choosing events
The most frequent mistake is sending Purchase for something that is not a payment, such as a booked appointment, with a placeholder value. That inflates conversion value in Ads Manager and makes return on ad spend meaningless.
The second is sending the same event for two different stages, for example Lead for both Interested and Qualified. Meta then cannot tell the two apart, and you lose the ladder that made the events useful. The third is renaming statuses in the CRM without updating the mapping, so a stage quietly stops sending.
- Purchase used for non-payments, or with made-up values
- One event reused for two different stages
- Event names not spelled and capitalised exactly as Meta's standard names
- Status renamed in the CRM but mapping not updated
Reading the events once they arrive
Once all four events flow, Events Manager shows each one separately with its volume over time. A healthy lead business usually sees a shape like a funnel: many Contact events, fewer Lead events, fewer still SubmitApplication, and a small number of Purchase events. If Lead outnumbers Contact, or SubmitApplication is almost as frequent as Contact, the stage rules are probably being applied loosely.
Example: a visa consultancy receives 400 Instant Form leads in a month. Its CRM sends 260 Contact events, 110 Lead events, 35 SubmitApplication events and 12 Purchase events. Read top to bottom, that is a believable ladder. If the same month showed 260 Contact and 240 Lead, the team is marking almost everyone as interested, and the Lead event has stopped meaning anything.
The most useful view, though, is not in Meta at all. When the same stages live in your CRM next to campaign, ad set and ad names, you can calculate cost per qualified lead and cost per customer for each campaign. Meta's events help the algorithm; your CRM's stage report helps you decide where to spend.
Comparison tables
Meta standard events for lead generation
| Event | Meta's definition (paraphrased) | Lead-gen meaning | Required parameters |
|---|---|---|---|
| Contact | Person initiates contact by phone, SMS, email or chat | Lead was reached | None |
| Lead | A sign-up is completed | Lead showed genuine interest | None (value and currency optional) |
| SubmitApplication | Person applies for a product, service or program | Lead is ready to buy | None |
| Schedule | Person books an appointment to visit a location | Appointment or site visit booked | None |
| Purchase | A purchase is made | Lead paid | value and currency |
Example mappings by industry
| Industry (example) | Contact | Lead | SubmitApplication | Purchase |
|---|---|---|---|---|
| Real estate broker, Pune | First call answered | Budget and area confirmed | Site visit done | Booking amount paid |
| Coaching centre, Jaipur | First call answered | Counselling done | Demo class attended | Fee paid |
| Visa consultancy | First call answered | Eligibility checked | Documents submitted | Service fee paid |
| Travel agency | First call answered | Itinerary shared | Quote accepted | Advance paid |
FAQ
What is the difference between the Contact and Lead events in Meta?
In Meta's definitions, Contact is when a person initiates contact with your business by phone, SMS, email or chat, and Lead is when a sign-up is completed. In a CRM, Contact usually marks a lead who was reached, and Lead marks a lead who showed genuine interest after that first conversation.
Should I send a Purchase event if my business does not sell online?
Yes, if a lead pays you in any way, send Purchase from your CRM when the payment is recorded, with the amount and INR as the currency. Purchase is the only event that tells Meta which ads produced revenue. Do not send it for steps that are not payments.
What is the SubmitApplication event used for?
Meta defines SubmitApplication as when a person applies for a product, service or program you offer. Lead businesses commonly use it for the stage where a lead is ready to buy, such as a completed site visit, a counselling session or an accepted quote.
Can I use custom events instead of standard events for lead gen?
You can, but standard events are usually better because Meta's tools recognise them without extra setup. Use a custom event only when no standard event describes the step. Meta's Conversion Leads goal is the exception: it uses your own CRM stage names in a specific payload format.
Which Meta event should I optimise my lead campaigns for?
Choose the deepest stage that still happens often enough for Meta to learn from. Purchase means the most but may be rare; Contact is frequent but shallow. Many lead businesses find a mid-funnel stage such as SubmitApplication the practical balance, while continuing to send all four events.
Where does Qualimize fit?
Qualimize uses exactly this ladder. Each workspace status can be attached to one of four signals: Contact, Lead, SubmitApplication or Purchase, with defaults of Contacted, Pre-Qualified, Qualified and Converted. Purchase carries the deal value and currency when a rep records it. If you need a different event, such as Schedule, you would need another tool or a custom integration.
Key takeaways
- Send four events for lead gen: Contact, Lead, SubmitApplication and Purchase, in order of intent.
- Keep each event close to Meta's own definition so the data stays readable.
- Only Purchase requires value and currency; never send it for non-payments.
- Use one event per stage; reusing an event for two stages erases the difference.
- Sending an event and optimising for it are separate choices; optimise for the deepest stage with enough volume.