Browse guidesTracking & analytics

Choose what each action sends to Meta

Set the Meta event name, browser and server channels, scroll depth and registration value for each action on your landers.

6 min read Updated 30 Sept 2026 For admins
On this page6 sections
  1. 01What each action sends by default
  2. 02Change an action
  3. 03Tell Meta who showed up
  4. 04What the badges mean
  5. 05Which event to optimise campaigns for
  6. 06Rules Bottega always applies

The defaults suit most webinar funnels, so you only need this page to rename an event, add a value to registrations or switch a channel off. As with the rest of tracking, only Space admins can edit it, and only when GOATEDX allows it.

BottegaTrackingEvents sent to Meta
ActionMeta eventSent whenLimit
Page viewPageViewEvery load of a lander page, including thank-you and upsell pages.10 per session
Engaged visitViewContentThe visitor scrolls past 50% of a page.1 per session
CTA clickClickCTAA click on any element marked data-cta.5 per session
Form openedOff (OpenForm)The registration form opens or its first field is focused.1 per session
RegistrationLeadThe server saves a new seat for this email and webinar.Once per seat
WhatsApp bonus clickContactA click on an element marked data-wa. On a page with none, any wa.me or WhatsApp link outside the footer counts. A footer contact link never does.3 per session
Showed up on ZoomWebinarAttendedA registrant spends 20 minutes or more on the first night (both can be changed in the event map). Needs Zoom connected, or an attendance CSV.Once per person per run
Joined from their linkJoinChallengeSomeone goes through their personal join link (the lander's /join) into Zoom. Sent from the server as they're forwarded.Once per person per night
Call bookedInterviewBookedSomeone is marked Call booked in Sales › Closing Room.Once per person

Each row also shows the parameters sent with the event, whether it is a standard or custom Meta event, and how many were sent in the last 7 days.

  1. Pick the Meta event

    Use the dropdown in the row. Registration offers Lead or CompleteRegistration. CTA click offers ClickCTA, InitiateCheckout, ViewContent or Custom name…. Form opened offers OpenForm or InitiateCheckout. WhatsApp bonus click offers Contact or Schedule. Page view and Engaged visit keep fixed names.

  2. Set the channels

    Click Browser or Server to switch each side on or off. Leave both on where you can. The badge below them tells you what you get.

  3. Adjust the extras

    Engaged visit has a Scroll depth of 25%, 50%, 75% or 90%. Registration has a Value and currency, which Meta receives with every registration (leave it at None if you don't value leads).

  4. Click Save

    The page shows when it saved. Landers use the new map within a minute.

A custom CTA name must start with a letter and use only letters, numbers and underscores, up to 40 characters. Click Presets to go back to the list. PageView, Lead and CompleteRegistration can't be used for clicks, so a button can never inflate your registrations.

A registration tells Meta who signed up. Showed up on Zoom tells it who actually came, so you can see cost per attendee and, with enough volume, have Meta look for people who attend rather than people who only register.

  • Bottega sends it by itself: within an hour of each date ending, once Zoom's attendance report arrives (or straight after you import an attendance CSV). There is nothing to do on the night.
  • It only counts registrants matched to a Zoom participant who stayed at least the time in Counts after (1, 5, 15 or 30 minutes). Each person is sent once per run, however many dates they join.
  • It carries the same hashed details as the registration, plus minutes_attended and the webinar name, so Meta matches it just as well.
  • It is server only. Attendance happens on Zoom, so there is no browser side to pair it with.
  1. Create a custom conversion in Meta

    In Events Manager, open Custom conversions, click Create, choose your pixel and pick WebinarAttended as the event. To count only people who stayed, add a rule such as minutes_attended greater than 30.

  2. Report on it first

    In Ads Manager, add the custom conversion as a column. You now see attendees and cost per attendee next to each ad.

  3. Optimise for it once there is volume

    Meta learns best from about 50 events a week per ad set. Until a campaign reaches that, keep optimising for registrations and use attendance for reporting.

BadgeMeaning
DeduplicatedBrowser and server both send, with one event ID. Meta counts it once.
Server onlyOnly the Conversions API sends it. Ad blockers can't stop it.
Browser only · ad blockers hide itOnly the pixel sends it, so visitors with ad blockers are missed.
Needs access tokenThe server side is on but no access token is saved.
Needs pixel IDThe browser side is on but no pixel ID is saved.
OffNothing is sent for this action.

Optimise for your registration event. Button clicks are cheap and plentiful, so a campaign optimised for them finds people who click rather than people who register. To report clicks per button, create a custom conversion in Events Manager on your CTA event and filter it by cta_position.

  • A registration always reaches Meta by at least one channel. Switching off the only remaining side switches the other one back on.
  • Registrations are sent only for a new seat. Repeat submits, double clicks, bots and previews never send one.
  • Browser and server use the same per-session limits, so a browser event never goes out without its server twin.
  • After any change here, run the test again. See Test your Meta tracking with Test Events.

Something here out of date? Tell us and we'll fix the guide.

Still stuck?

Ask a person, not a bot.

Tell us your space and the page you were on. A screenshot helps. Someone on the GOATEDX team reads every email and replies.

bottega@goatedx.com