Tracking
The Meta Pixel on your published site, with the visitor's consent.
Paste your Pixel id under SEO & GEO. Your published pages load Meta's script after the visitor accepts the cookie banner, and record a page view for your ad reporting.
How you connect
Where Meta Pixel is switched on
The screen, the path to it in the sidebar, and what happens when you press the button. Nothing else to install.
Site console
- Site & SEO
- SEO & GEO
Press Save tracking. The Tracking card takes the Pixel id (digits only, from Events Manager) and refuses anything else. The next visit to the published site carries it.
Consent first
The banner does the asking, and the pixel waits for the answer.
The Meta Pixel sets cookies, so as soon as an id is set your published pages show a consent banner at the foot. Accept loads the pixel on that page and records a PageView; Decline is remembered and nothing loads. The first-party analytics is not behind the banner.
Shown only while an id is set
Clear the field and the banner goes with the pixel.
An answer is kept
The visitor's choice lives in their browser on your own domain and is asked again after it expires.
Your words, your policy link
Write the sentence and point at your privacy page, or keep the built-in one.
- Days a visitor's answer is kept
- 180
Counted in the product, not estimated.
What you get
Meta Pixel with Cliux
One field, a Pixel id
The numeric id from Events Manager. Anything with letters is refused before it is saved.
Loads after consent
fbevents.js is added in the browser once the visitor accepts, and not before.
A PageView per page
Every published page records the standard PageView event when the pixel loads.
Every published page
Home, site pages, blog posts and member pages carry the same pixel; nothing to place per page.
Alongside first-party analytics
Cliux's own traffic and realtime view keep working with or without the pixel.
Undo is clearing the field
Remove the id and save: the pixel and the banner are gone on the next visit.
Not included
Said plainly, so you can decide
What this connection does not do today. If one of these is the thing you need, tell us through the contact form; the list is prioritised from those requests.
- Standard events beyond PageView
- Purchase, Lead, AddToCart and the rest are not sent. Store orders and form submissions do not reach Meta.
- Conversions API
- There is no server-side relay to Meta; the pixel runs in the visitor's browser only.
- Catalogue sync
- Store products are not exported to a Meta catalogue.
- Advanced matching
- No visitor data (email, phone) is passed to the pixel.
- Consent-mode signals
- Cliux does not send Meta a consent flag. It withholds the pixel until the visitor accepts.
Frequently asked questions
Have other questions?Use the contact form
In the site console under Site & SEO → SEO & GEO, in the Tracking card, beside the Google Analytics field. Save, and the next visit to the published site carries it.
Yes, while an id is set and the banner switch is on, which it is by default. The pixel sets cookies, so the site asks first. Turn the banner off in the same card and getting consent is your responsibility.
PageView, on every published page, once the visitor has accepted. No other standard or custom event is sent.
No. Orders stay on your site and in your Stripe account. There is no Purchase event and no Conversions API relay.
Yes. The two fields sit side by side, one banner covers both, and each loads after the same acceptance.
Get started
Try Meta Pixel on a Cliux site.
Building and previewing costs nothing. Publishing with your own domain is $9 a month on a personal site, and the agency Starter plan publishes 2 client sites for free.