Skip to main content

Overview

The Members Portal has the three most used ad pixels built in. Add their IDs and the portal loads them on every page and sends them what customers look at, add to their cart, buy and ask about, so you can see which campaigns bring bookings and sales, and show ads to people who visited.

When the pixels load

  • Only with the visitor’s marketing consent when your cookie banner asks first (Opt-in or My own consent tool): they load as soon as the visitor accepts, without reloading the page. With the banner Off or in Notice mode they load straight away.
  • Never in the Passport app or white-label apps, in demo accounts, or while you edit pages.
  • Not while the page address contains attendee details (some event and booking checkout pages): the pixels wait for the next page.
In the EU and the UK you normally need visitors’ consent before loading ad pixels. If your cookie banner is off, turn it on with Opt-in before adding pixel IDs.

What each pixel receives

Items are named resource-12, product-45, plan-7, event-9, course-3 or pass-5, the same IDs as in Google Analytics. Each order counts once: Meta receives the order’s ID as its event ID, so it can match it if you also send orders from elsewhere.
No email address, phone number or name is ever sent to a pixel. Meta’s advanced matching is not used, and the portal turns off Meta’s automatic event setup so the pixel only receives the events above.
  1. In Google Ads, create a conversion action for purchases (category Purchase, value from the tag) and, if you want, one for leads.
  2. In each action’s tag setup, choose Use Google Tag Manager or Install the tag yourself and copy the Conversion ID (AW-…) and the Conversion label.
  3. Enter the conversion ID and the labels in Settings → Integrations → Google Ads.
The purchase value is the order’s value before tax, in the invoice’s currency.

Other ad platforms

For TikTok, Pinterest, HubSpot or any other platform, add its code with custom code and listen to the portal’s events with window.__nexudus.on(...). Tag the code marketing so it waits for consent like the built-in pixels.