Lead capture
Set up your ads so Nod can attribute every lead
Connect contacts to their first ad and measure ROAS using payments recorded in Nod.
Before you start
You need access to the ad or campaign settings in Meta Ads Manager and to the destination your visitors open.
Step by step
- Open Meta Ads Manager and select the ad you want to measure, or the campaign if you are setting parameters at that level.
- Go to Settings → Tracking → URL Parameters.
- Paste this exact string: utm_source=meta&utm_medium=paid&utm_campaign={{campaign.name}}&utm_content={{ad.id}}
- Save the settings. Meta replaces {{ad.id}} with the ad ID and {{campaign.name}} with the campaign name. Parameters set at campaign level are inherited by the ads.
- If you use a Nod landing page or form, source capture is automatic. You do not need to configure these fields in Nod.
- Open Meta Ads in Nod. Setup guidance stays visible until the first attributed lead arrives.
- Click Copy to copy the whole string, then paste it into URL parameters in Meta Ads Manager.
What Nod keeps
Forms and landing pages capture utm_source, utm_medium, utm_campaign, utm_content, and fbclid from the arrival URL and associate them with the contact. The first ad that brought the person in keeps the credit; a later visit does not replace it.
Attribution brings together scheduled calls, attended calls, closed customers, and collected revenue by ad and day. ROAS is calculated from collected revenue, not the pixel’s value.
If your landing page is outside Nod
A Nod form embedded on an external website also captures campaign source information.
If a button opens the form on another page, preserve the same parameters in the button’s link. If they are not passed to the form, the contact may arrive without the ad identifier. Alternatively, embed the form.
Attribution and Conversions API are different
Parameters let Nod connect a contact to an ad. Conversions API sends events to Meta from the server when you enable that connection. Setting up one does not replace the other.
Inform your contacts about campaign source tracking and, if you connect CAPI, data transfers to Meta. Obtain consent where required.
What to expect
The lead keeps its source and can be linked to the ad to calculate results and ROAS in Nod.
Troubleshooting
Without utm_content={{ad.id}}, the lead reaches Nod but does not count toward the ad’s ROAS. Review the ad parameters and any intermediate links.
If setup guidance remains visible, the first attributed lead has not arrived yet. An unattributed contact does not confirm that setup is correct.
ROAS is not profit: here it compares attributed collected revenue with ad spend.