Send Meta only the leads that match your ideal customer

Use a form’s score or answers to send qualification events to Meta only when your criteria are met, without external tools.

Requirements

You need business administrator access to connect Meta CAPI, access to your pixel or dataset in Meta Events Manager, and a Nod form. Decide which answer or score identifies your ideal customer.

Steps

  1. Prepare your Meta CAPI connection and a qualification form.
  2. Turn off automatic Lead events for that form and create an automation with a condition.
  3. Test one qualifying submission and one that does not qualify. Follow the detailed steps below.

How it works

Your form collects answers and can assign points. An automation checks the score or a specific answer before sending an event to Meta. Conditional logic lets you adjust which questions each person sees.

By default, every form sends Lead for each submission. You can turn this off so your automations control its events. Email, phone number, and name are hashed before sending; an ad click identifier is also used when available to help attribution. The same event is not sent twice for the same submission.

For example, send CompleteRegistration only when a business reports more than €10,000 in monthly revenue. This helps Meta optimize toward people who fit your offer; it does not guarantee campaign results.

1. Connect Meta CAPI

  1. In Nod, go to «Meta Ads» and click «Connect Meta CAPI». A business administrator must complete this step.
  2. In Meta Events Manager, open your pixel or dataset and copy its ID.
  3. Go to «Settings» → «Conversions API» → «Generate access token». Generate and copy the token.
  4. Paste the ID and token into Nod. Optionally, add the code from «Test events» in Events Manager.
  5. Click «Connect», then «Send test event». Check «Test events»; it may take a few seconds to appear.
Important: while the test code is set, events do not count in reports. Remove it when testing is complete. Do not click Disconnect to test the connection.
The lower part of the actual Meta CAPI panel in English, with the connection already active: event types and the test button. Account identifiers are outside the crop.
  1. Send test event sends the test event. Check the test code in your configuration first. Disconnect disables the connection and is not part of testing.

2. Set up form scoring

  1. Go to «Forms» and create a form or open an existing one.
  2. Under «Questions», add questions and assign «Points» to each answer option.
  3. For branching questions, open «Settings», select «Conditional logic», and connect answers to questions under «Logic».
  4. Under «Settings» → «Scoring», set warm and hot lead thresholds if needed.
Answer to “How much monthly revenue does your business generate?”Points
Less than €3,0000
€3,000–€10,0005
More than €10,00010
Important: the score adds up the answers. If one specific answer is required, use that question directly as your condition.
Form builder: questions on the left, preview in the center, and question options on the right.
  1. Assign points to each answer under Scoring.
Actual Logic view for connecting answers to the form path.

3. Turn off automatic Lead events

  1. Open the form’s «Settings».
  2. Find «Send «Lead» to Meta» and turn it off.
  3. Check that the explanation now says the form does not send anything to Meta on its own and your automations decide what is sent.
Important: if this remains on, Meta receives Lead for every submission, qualified or not. This setting does not disable appointment, purchase, or subscription events.

4. Create the automation

  1. Go to «Automations» → «New automation».
  2. Under «Choose the trigger», select «A form is submitted» and choose your qualification form.
  3. Click «Add condition». By score: «Score» → «is greater than» → 9. By answer: “How much monthly revenue does your business generate?” → «is equal to» → “More than €10,000”.
  4. Click «Add a step» → «Send event to Meta».
  5. Under «Event», choose CompleteRegistration, Lead, SubmitApplication, Schedule, Contact, or «Custom event».
  6. For a custom event, enter a name such as QualifiedLead. Start with a letter and use only letters, numbers, and underscores, with no spaces and a maximum of 40 characters.
  7. Click «Save», then publish the automation.
Important: select the form in the trigger to access its questions. Enter the answer exactly as it appears in the option. If you add multiple conditions, all must be met.
Select the form submission trigger in the actual automation trigger list.
  1. Choose A form is submitted, then select your qualification form.

5. Test both cases

  1. Keep the test event code in your Meta CAPI connection.
  2. Submit the form twice: once meeting the condition and once without meeting it.
  3. In Events Manager → «Test events», check that the event appears only for the qualifying submission.
  4. In Nod, check «Meta Ads» → «Meta CAPI» for the counters showing events sent in the last seven days, queued events, and failed events.
  5. Remove the test code once everything works so events count toward reporting and optimization.

Which events Nod sends automatically

What happensEvent
A form is submittedLead, unless disabled for that form
A call is scheduledSchedule
A sale is paid through Stripe, Commas, Whop, or recorded manuallyPurchase, including amount and currency
A subscription startsSubscribe
An automation runs «Send event to Meta»Your selected event, when its conditions are met
Creating a client account in the portal does not send a registration event. The purchase is already reported through Purchase.

Best practices

Choose the same campaign optimization event your automation sends, such as CompleteRegistration.

Do not send Purchase from an automation. Purchases are already reported with their amounts.

If you also use the Meta pixel on your website, avoid sending the same event from both places without managing duplicates.

Explain in your privacy policy that you send data to Meta to measure advertising, including hashed identifiers.

Frequently asked questions

What if someone submits twice? Each submission is separate and can generate its own event if it qualifies. The same event for one submission is not sent twice.

What if Meta CAPI is not connected? The step sends nothing and displays a warning.

Can I use another form or Typeform? These answer-based conditions work with Nod forms. For other sources, it depends on the incoming data.

Can I send different events for different scores? Yes. Create multiple automations with their own conditions and events, such as hot and warm leads. Avoid overlapping conditions if you want separate groups.

How long does it take? Usually a few seconds. Check in Events Manager.

The complete workflow

  1. Create a form with scoring.
  2. Turn off automatic Lead events.
  3. Create an automation with a condition.
  4. Add «Send event to Meta» and publish.
  5. Test in Events Manager and remove the test code.

What you’ll see when it works

«Test events» shows the event for the qualifying submission, but not for the submission that fails the condition. After you remove the test code, events are used for reporting and optimization.

If something goes wrong

Nothing appears under «Test events»: check the current code, that the automation is published, that the correct form is selected, and that the answers meet the condition.

Failed events increase: the token may be expired or revoked. Generate a new token in Events Manager and reconnect Meta CAPI in Nod.

Lead events are still sent for everyone: check that «Send «Lead» to Meta» is off for that form.

Still have a question? Contact us through Report a bug or the chat.