Measure your pages with your brand’s Meta Pixel

Start with the account advertising your business

A Pixel measures actions on destination pages. An ad account contains campaigns, boosts and advertising metrics. Access to a dataset does not prove access to the ad account paying for your boosts.

Select your brand and open My Brand → Channels → Instagram → Manage. When Meta Unified connection is available, use Connect or Reconnect, authorize the correct Instagram and ad account in Meta, then return and explicitly choose this brand’s Instagram. An existing connection stays active while we verify the new account and receive a real comment or message through the new app.

Then open Set up Meta ads, also available under Results → Ads. A new Unified authorization with advertising access supplies this brand’s credential. Separate Facebook authorization remains available when needed. If the brand has connected Instagram, the ad account must be linked to that Instagram. Compare the account name and number with Ads Manager; do not select a different account just because it appears.

If the account is missing or access is denied, check Settings → People → your profile → assigned assets in the business portfolio. Check the ad account and dataset in their asset lists, including their connection. Reconnect Meta in the platform and authorize the correct assets. Menu names vary with Meta’s interface and your access level. Login permissions do not grant access to every business asset. If Meta reports that the ad account owner has not granted ads_read or ads_management, ask that account’s administrator to assign access to the correct profile and integration, then reconnect. Changing the Pixel or reconnecting without correcting asset assignment does not fix this missing access.

Choose one brand default

In My brand → Channels, open Configure measurement → Meta. The same selection is also available in Booking → Server-side conversions → Your brand’s Meta Pixel, before the server credential. Click Find Pixels in connected Meta account. The list comes from this brand’s selected ad account.

Click Use for your business’s Pixel. One available Pixel produces one option; with several, compare the ID in Events Manager before choosing. An empty list does not create a Pixel automatically: in Events Manager use Connect data → Web, when available, to configure a source, or connect an existing dataset to the ad account. Refresh the list afterward. This does not create or activate campaigns.

The selected Pixel becomes the default for link-in-bio, booking and landing pages without their own setting. An explicit landing-page Pixel or disabled setting takes precedence. Check a page through its measurement section and Meta conversions. The brand’s choice also owns Meta measurement on Intelli Labs public pages. Platform signup and subscription acquisition keep their own destinations; existing Google and OpenAI measurement remains separate.

Visitors can continue without cookies. Meta loads in the browser only after permission; visitors can change their choice on the page. Consent is scoped to the brand and Pixel; a different Pixel requires a new choice. Private previews and the editor do not send visits to Meta.

Understand the events

PageView represents a consented visit. Link-in-bio and booking clicks do not become leads or purchases. A landing page sends Lead after accepting a valid form, with the applicable permission. Replaying the same accepted response should not count the inquiry again.

Schedule means an appointment confirmed by the business. A pending request does not send it. Delivery uses the verified Meta connection or manual credential described below; the visitor must also authorize advertising measurement for the booking. That permission is separate from page cookies.

Lead and Schedule are Meta standard events. They do not require creating a custom conversion object first: the integration already sends them when the real action occurs. Setup does not fabricate a first conversion to make an event appear in a dashboard. Avoid adding a second automatic rule for the same form, which could duplicate counts.

Check automatic delivery and use a manual token only when needed

When you choose a Pixel, the platform checks whether the same Meta connection can upload events to that asset. If you see Server delivery is available through the verified Meta connection, no additional token is needed. The connection remains encrypted, and permission is checked again before every delivery. Disconnecting, changing the account or losing access stops this path. Ads management permission alone does not prove dataset upload permission.

If Schedule is unavailable, check business portfolio → Settings → Data sources → Datasets → your dataset → People for the profile used to connect Meta, including permission to upload events. Also check Connected assets and the correct ad account. Reconnect in Results → Ads and return to Pixel setup. If Meta does not expose verification for your profile, use the manual configuration below. Ask support to check feature activation if the platform reports that delivery is unavailable in this environment.

In Events Manager select the same dataset → Settings → Conversions API → Set up direct integration → Generate token, according to the options available to your account. In the platform’s Server-side conversions, enter that Pixel ID, paste the token into its dedicated field and click Save server delivery. The credential is encrypted and is not displayed again. Never put it in a page, URL or chat.

A saved manual credential takes precedence and is never replaced automatically; manual disable also remains in force. To return to automatic delivery, click Use verified Meta connection. The switch happens only if current permission can be verified. Landing browser and server destinations must use the same Pixel; the event identity supports deduplication. Booking confirmation uses the server without transmitting service details, notes or form answers to Meta.

Google Ads, Analytics and OpenAI on your brand’s pages

Open My brand → Channels → Configure measurement and choose the destination. Use the AW- tag identifier for Google Ads, not the advertising account number; use the brand stream’s G- identifier for Google Analytics. For OpenAI Ads, enter the Pixel ID, never an API key. Do not paste scripts. Saving these identifiers does not connect campaign management or change your budget.

After visitor permission, the page can record the visit. A landing form is recorded only after it is accepted. For Google Ads, copy the accepted-form conversion action’s label into its field; the integration does not invent a label. An accepted form uses `generate_lead` for GA4 and `lead_created` for OpenAI. None of these events represents a purchase.

Google booking and purchase labels are stored for their corresponding integration, but this page flow does not send them yet. Meta Schedule still follows confirmation and the conditions above. Do not treat a click as payment to populate a dashboard. Check legitimate actions in the destination’s diagnostics and preserve the visitor’s privacy choice.

The default covers the brand’s link-in-bio, booking and landing pages. A page-specific configuration or disable takes precedence. Switching brands does not reuse your identifiers; IntelliBrands acquisition advertising remains separate.

Check receipt without inventing results

After an authorized legitimate action, inspect the dataset in Events Manager and Delivery and protection → Refresh diagnostics in the platform. Received by Meta means technical receipt; it does not prove a sale or ad attribution. Declined cookies, blockers and revoked access can prevent delivery. Server diagnostics do not count browser-only visits.

Use a separate test dataset and an appropriate test procedure for rehearsals. Do not send artificial leads or purchases to production or confirm fictional bookings to populate reports.

A custom conversion is an additional rule over a source/event, useful for separating a particular offer or subset of actions. This Lead/Schedule setup does not require it. If your business needs that distinction, configure the rule in Events Manager and deliberately choose its use in the ad set. IntelliBrands does not modify existing campaigns during this setup.

Continue with the qualified conversions guide to distinguish a submitted form, a suitable inquiry and a confirmed sale.