Add ad pixels and the consent banner
Updated October 15, 2026
Fire Meta, Google Ads, GA4 or LinkedIn conversion pixels on every published page and hub, gated by a cookie-consent banner.
What it’s for
Ad tracking lets you add conversion pixels once, at the workspace level, so they fire on every published page and event hub without any per-page setup. It works with the Meta Pixel, Google Ads, Google Analytics 4 and the LinkedIn Insight Tag.
A cookie-consent banner gates the pixels: nothing loads until a visitor accepts. It is the only consent mechanism your pages have, so it stays on by default. Tracking is admin-only, and lives inside Settings → Integrations.
Open Settings → Integrations. At the bottom, the “Ads tracking” section has one row per platform (Meta Pixel, Google Ads, GA4 and the LinkedIn Insight Tag), then the consent banner. A platform that is set up shows its id and an “Active” tag. Here, the Meta Pixel already is.
Click “Add” on a platform, or “Edit” on one that is already set up, enter its id and click “Save tracking”. Google Ads needs both a conversion id and a label; a LinkedIn conversion id needs a partner id. “Remove pixel” clears a platform you no longer use.
Keep the cookie consent banner on. Turning it off asks you to confirm. Without it, Meta and LinkedIn never load (they wait for an accept) and Google runs cookieless (Consent Mode stays denied).
The consent banner is the only consent mechanism your pages have. Leave it on for GDPR.
Good to know
- Each id is checked as you type: a badly formatted id is flagged in the dialog, and nothing is saved until it is fixed. Saving an empty field clears that platform.
- Pixels fire on every published page and event hub in the workspace, always gated by the consent banner.
- Only workspace admins can change tracking. The section moved here from its own tab. The old Settings → Tracking link now opens Integrations.
Related articles
- Control access and privacyPassword-protect the page, set its visibility, redirect after registration, and cap sign-ups or close them at a set date.
- Create and revoke API keysIssue workspace keys to call the pages API from your own code. Revoke them when you no longer need them.
- Set how long registrant data is keptChoose a retention window for the personal data collected through your pages, or have your pages keep none at all.
Still need help?
Ask AI for a docs-grounded answer, or talk to our team.
Was this article helpful?