Pixels and tags
Report page views, leads and booked calls from your Nudge funnel to Meta or Google Tag Manager, from the browser and from Nudge's servers.
What pixels do
Your ad platforms optimise for what they can measure. Pixels and tags sends the key moments of your Nudge funnel (your forms, booking pages and the website agent) back to your own advertising stack, so you can see which campaigns bring leads and meetings, and let the platforms bid for them.
You add one or more destinations. Each destination is a pixel or a container, plus the list of moments it should hear about.
The five moments
| Moment (label in the app) | Fires when |
|---|---|
| Page view | The funnel is opened. |
| Contact left | The visitor leaves contact details. It fires once for the email and once for the phone, so a form asking for both reports twice. |
| Qualified | The lead passes the form's qualification rules. |
| Disqualified | The lead does not pass them. |
| Call booked | A meeting is booked. |
For each moment you choose the event name it is sent under. Leave a name empty and that moment is not sent to this destination.
Browser and server
For Meta, Nudge can report each moment twice, on purpose:
- From the browser, through the pixel loaded in your funnel. It carries the visitor's ad cookies, which helps attribution.
- From Nudge's servers, through Meta's Conversions API. It cannot be blocked by ad blockers. The visitor's email and phone are hashed before they are sent.
Both copies share the same event ID, so Meta counts the moment once. Page view is only sent from the browser. A destination with a token shows the Conversions API badge; without one it shows Browser only.
Visitor consent
If a form asks visitors for consent, no pixel or tag is loaded and nothing is sent until the visitor gives it.
Open Pixels and tags
In Integrations, find Pixels and tags under Advertising and data and click Configure (or Manage once a destination is active). The top of the page has one button per provider to add a destination.
Add a Meta pixel
Click Meta Pixel
Click Meta Pixel +. The Connect Meta Pixel dialog opens.
Fill in the pixel
- Name: a label for your team, for example Meta – main ad account.
- Pixel ID (dataset ID): 15 to 18 digits, from Meta Events Manager.
- Conversions API token: in Events Manager, open your dataset › Settings › Conversions API › Generate access token, and paste it. Optional but recommended: without it, only the browser half fires, and ad blockers stop a large share of it.
Choose what to report
Under What to report, Nudge prefills Meta's standard events. Change them if your campaigns optimise for other names.
| Moment | Default event |
|---|---|
| Page view | PageView |
| Contact left | Lead |
| Qualified | CompleteRegistration |
| Disqualified | (empty, not sent) |
| Call booked | Schedule |
Create and test
Click Create. On the destination, click Send a test event (paper-plane icon). Paste a Test event code from Events Manager › Test Events to see the event arrive live without it counting in your data, then click Send. The event was accepted. means the pixel ID and token are valid. Without a test code, Meta counts the event.
The token is write-only: when you edit the destination, the field stays empty with A token is stored. Leave it empty to keep it, or paste a new one to replace it.
Add a Google Tag Manager container
Use Google Tag Manager to send the funnel's moments to Google Ads, Google Analytics 4 or any tag you manage in GTM.
Create a dedicated container
In Google Tag Manager, create a web container just for your Nudge funnel. Google does not let you reuse the container already installed on your website.
Add it in Nudge
Click Google Tag Manager +, enter a Name and the Container ID (GTM-XXXXXXX).
Keep or rename the events
Each moment is pushed to the container's dataLayer under the event name you set. Defaults:
| Moment | Default dataLayer event |
|---|---|
| Page view | pipecall_view |
| Contact left | pipecall_potential |
| Qualified | pipecall_qualified |
| Disqualified | pipecall_disqualified |
| Call booked | pipecall_call_scheduled |
Each push also carries an event_id.
Build your triggers in GTM
In your container, create Custom Event triggers on these names and attach your tags (for example a Google Ads conversion on pipecall_call_scheduled). Publish the container.
When the funnel is embedded in your own page
A Nudge funnel embedded in one of your pages runs in an iframe and cannot reach the container of the page around it. Once a GTM destination exists, the Pixels and tags page shows a panel Listening from the page that embeds your funnel with a short script and a Copy button. Paste that script on the page that embeds the funnel: it forwards the funnel's moments into that page's dataLayer, with the same event names, and ignores duplicates.
Other ad platforms
OpenAI Ads destinations take a Pixel ID from the OpenAI Ads dashboard and the event names of that platform's own taxonomy (page_viewed, lead_created, registration_completed, appointment_scheduled). The LinkedIn Ads and TikTok Ads buttons are not open yet. For other platforms, send the moments through a Google Tag Manager container.
Manage destinations
Each destination card shows its name, its ID, its badge and the moments it reports (for example Call booked → Schedule). If no moment has an event name, the card says No moment reported yet — nothing will fire.
| Control | What it does |
|---|---|
| Switch | Pauses or resumes the destination. |
| Send a test event | Meta destinations with a token only. |
| Recent activity | Shows what the destination received (see below). |
| Edit | Changes the name, ID, token or event names. The provider cannot be changed. |
| Delete | Asks for confirmation, then stops reporting immediately and deletes the activity counters. Events already sent are not affected. |
You can add up to 5 Meta destinations, 3 Google Tag Manager containers and 5 OpenAI Ads destinations per workspace, on every plan. Beyond that, the dialog shows Maximum number of destinations reached for this provider.
Recent activity
Recent activity (pulse icon) lists, per moment and per source:
- Trigger and Event: the moment and the name it was sent under.
- From: Browser or Server.
- Total: how many times it was sent.
- Funnel: where the last event came from.
- Last: when it last fired.
Events appear within a minute of firing. If the Browser count is far below the Server count, ad blockers are stopping the browser pixel; that is exactly the gap the Conversions API covers.