--- title: "Meta Pixel Analytics on Event Landing Page" description: "Learn how to implement Meta Pixel analytics handling in your event in Meeting Application" url: https://help.meetingapplication.com/en/articles/9497480-meta-pixel-analytics-on-event-landing-page collection: "Technical stuff" updated: 2026-10-12 language: en alternates: [pl] --- # Meta Pixel Analytics on Event Landing Page Learn how to implement Meta Pixel analytics handling in your event in Meeting Application ## Meta Pixel on Your Event's Landing Page in Meeting Application Meta Pixel allows you to track user actions on **your event's Landing Page in Meeting Application** and send Meta information about subsequent stages of the purchase journey — from entering the page, through adding a ticket to the cart, to the purchase. You can connect Meta Pixel to your event's Landing Page in **two ways**: - **Path A — Meta Pixel embedded in the Landing Page** — we configure the integration on the Meeting Application side. - **Path B — Meta Pixel via your Google Tag Manager** — you configure the Pixel yourself in your GTM container. > **Warning:** Before you start. > > For one event, use only **one Meta Pixel integration path**. > > Do not run the embedded Pixel and Meta Pixel tags in your Google Tag Manager at the same time. In such a case, the same events and conversions may be sent to Meta twice. > > If you are unsure which configuration is active for your event, **contact us before launching the Pixel**. ## Two integration paths — key differences

	Path A — Built-in Pixel	Path B — Pixel via Your GTM
Who configures Meta Pixel?	Meeting Application	You or a specialist / agency managing your GTM
Where does the configuration work?	Directly in the Landing Page code	In your Google Tag Manager container
Pixel ID	You pass it to us	You use it exclusively in your own GTM — you do not pass it to Meeting Application
Later changes	Require a change on the Meeting Application side	You can make them yourself in GTM
Scope of basic events	Full purchase funnel + `CompleteRegistration` for free joining without a cart	Full purchase funnel
eventID at Purchase	Handled automatically	You configure it according to the instructions below

If you do not manage Google Tag Manager independently, the simpler option is **Path A**. If you have your own GTM specialist or agency and want to manage the Meta Pixel configuration independently, choose **Path B**. ## Before you choose a path — prepare the shared configuration Both options use the same basic elements. ### 1\. Prepare Meta Pixel Create a Pixel in your **Meta Events Manager**: **Connect data sources → Web** In the data set settings you will find **Pixel ID** — a string of 15–16 digits. Meta currently also uses the term **data set — dataset**. Dataset ID and Pixel ID refer to the same identifier here. You will need the Pixel ID in the further configuration: - in **Path A** you will pass it to Meeting Application, - in **Path B** you will use it independently during tag configuration in your GTM. ### 2\. Configure Cookiebot **Cookiebot is required in both paths.** Landing Page runs marketing scripts according to the consent provided by the user. Without proper Cookiebot configuration, Meta Pixel will not work according to the intended consent mechanism. Prepare: - Cookiebot account and configuration, - Cookiebot identifier, - the domain of the Landing Page event added in your Cookiebot panel. > ### 📌 Before you proceed > > If you have not yet configured Cookiebot and Google Tag Manager for your event's Landing Page, start with this configuration. You will find detailed instructions in the article: [**Sales Analysis via Google Analytics — Google Tag Manager and Cookiebot**](https://help.meetingapplication.com/pl/articles/9497444-analiza-sprzedazy-poprzez-google-analytics.md) ### 3\. Prepare Google Tag Manager Your event's Landing Page must have your Google Tag Manager container connected. Its identifier has the format: `GTM-XXXXXXX` Please provide us with: - **GTM container ID**, - **Cookiebot identifier**. On our end, we will connect both identifiers to your event's configuration. Ta konfiguracja pozwala Landing Page załadować Twój kontener GTM oraz przekazywać do `dataLayer` zdarzenia i sygnały zgody. > **Success:** ID kontenera GTM i identyfikator Cookiebot są elementami konfiguracji Landing Page **w obu ścieżkach Meta Pixel**. Warto przekazać nam oba identyfikatory na początku konfiguracji analityki wydarzenia. ### 4\. Wyłącz automatyczne zdarzenia Meta W **Meta Events Managerze**, w ustawieniach Pixela, rekomendujemy wyłączenie: **„Śledź zdarzenia automatycznie bez kodu” Track events automatically without code** Konfiguracje opisane w tym artykule korzystają z konkretnie zdefiniowanych zdarzeń. Wyłączenie automatyki pomaga uniknąć dodatkowych zdarzeń generowanych samodzielnie przez Meta i utrzymać czytelne dane. ## Ścieżka A — Meta Pixel wbudowany w Landing Page > **Info:** In this variant, Meta Pixel integration is maintained directly in the Landing Page Meeting Application code and is enabled for a specific event. You do not need to manually map Meta events in Google Tag Manager. ### What do you need to provide us with? After preparing the joint configuration, please provide us with: - **Pixel ID**, - confirmation that your GTM container **does not trigger Meta Pixel tags for this Landing Page**. > ### ⚠ If you already have Meta Pixel in your GTM > > Before we launch the built-in integration, disable Meta Pixel tags running in your GTM for the event's Landing Page. > > If both sources are active at the same time, events may be counted twice. After receiving the necessary information, we will configure Meta Pixel for your event. Subsequent changes to this integration require modification on the Meeting Application side. ### What events will you receive in Path A?

Meta Event	When is it sent?	Key parameters
`PageView`	Landing page entry and every page change	—
`ViewContent`	Just before adding an item to the cart	`content_ids`, `content_name`, net value, currency
`AddToCart`	Adding a ticket, add-on or workshop to the cart	`contents`, value of added item, currency
`InitiateCheckout`	Payment initiation	`contents`, net value of cart, number of items
`AddPaymentInfo`	Payment method selection	`contents`, net value, currency
`Purchase`	Confirmed payment	gross value, currency, `contents`, `eventID`
`CompleteRegistration`	Free event registration without cart	`status`

### How does this path work? Pixel: - does not send events before obtaining marketing consent, - does not duplicate `PageView` while navigating the Landing Page, - has Meta automatic events disabled, - can handle more than one Pixel, e.g. organizer and agency Pixel, - passes `eventID` during purchase, which prepares the event for potential future deduplication with Conversions API. If a participant obtains a **free ticket through the cart**, they go through the standard purchase process and complete it with an event: `Purchase` with value: `0` `CompleteRegistration` applies to free participation in an event taking place **without a cart**. ## Path B — Meta Pixel through Your Google Tag Manager > **Info:** In this path, you, your GTM specialist, or agency perform the configuration in **your own Google Tag Manager container**. Landing Page Meeting Application provides a ready-made `dataLayer` with e-commerce events and consent signals. Your task is to map these events to the appropriate Meta Pixel events. ### What do you provide to Meeting Application? Provide us with: - **GTM container ID** in the format `GTM-XXXXXXX`, - **Cookiebot identifier**. Also make sure that the Landing Page event domain has been added in your Cookiebot panel. ### Pixel ID - In this path, you **do not share your Pixel ID with us**. You use it exclusively in your own Meta Pixel tags configured in GTM. > **Warning:** Before you start configuration > > Make sure that the **built-in Meta Pixel from Path A is disabled** for your event. If you are unsure — contact us before publishing the tags in GTM. Events use GA4 naming and structure with an object: ```javascript ecommerce ``` Before each e-commerce event, the following is also sent: ```javascript { ecommerce: null } ``` This way, previous e-commerce data is cleared before the next event.

Event	Ecommerce parameters
`view_item`	`currency`, `value`, `items`
`view_item_list`	`currency`, `items`, `item_list_name`
`add_to_cart`	`currency`, `value`, `items`
`remove_from_cart`	`currency`, `value`, `items`
`view_cart`	`currency`, `value`, `items`
`begin_checkout`	`currency`, `value`, `tax`, `items`, optionally `coupon`
`add_shipping_info`	`currency`, `value`, `items`, `shipping_tier`
`add_payment_info`	`currency`, `value`, `items`, `payment_type`
`purchase`	`transaction_id`, `value`, `currency`, `tax`, `items`, optionally `coupon`
`checkout_progress`	`checkout_step`, `checkout_option`
`set_event_id`	`event_id` — Event ID in Meeting Application
`default_consent` / `update_consent`	`consent.ad_storage`, `consent.analytics_storage` and other Consent Mode v2 information

Each element of the `items` array contains: - `item_id`, - `item_name`, - `item_category`, - `price`, - `quantity`, and optionally: - `discount`, - `coupon`. > **Warning:** IMPORTANT > > The net and gross value `ecommerce.value` passed by the Landing Page is a **net** value. Tax is located separately in: `ecommerce.tax.` > > For the `Purchase` event, Meta requires a **gross** value. Therefore, during configuration you will create a separate variable that will sum: `value + tax` ## Step 1. Map events Basic mapping looks as follows:

dataLayer GA4	Meta Pixel	Notes
`view_item`	`ViewContent`	Landing Page does not have a separate product page.`view_item` is sent just before `add_to_cart`, therefore the numbers of both events may be very similar.
`add_to_cart`	`AddToCart`	`value` means the value of the added item, not the entire cart.
`begin_checkout`	`InitiateCheckout`	—
`add_payment_info`	`AddPaymentInfo`	—
`purchase`	`Purchase`	Use gross value, currency, `contents`, `content_type: 'product'` and `eventID = transaction_id`.

## Step 2. Create variables in GTM In Google Tag Manager, go to: **Variables → User-Defined Variables → New → Data Layer Variable** Create the following variables: - `DLV - ecommerce.value` - `DLV - ecommerce.tax` - `DLV - ecommerce.currency` - `DLV - ecommerce.transaction_id` - `DLV - ecommerce.items` - `DLV - consent.ad_storage` For each one, select: **Data Layer Version → Version 2** ![](https://files.gleap.io/pf/gattachments/wFEWDC7eHj0biiCoqdiugabd1YIvsdso2ApynsRML7zTBudFrlFwxf3g1urdUBuH6Ft6kBoXHe1.png?v=1&k=a&s=api&e=1794528000&sig=8pzXP4fFTu2nFDA6D5OJpu5f60eGIC6Tr2qtoekfIYg) ![](https://files.gleap.io/pf/gattachments/d7L1bv1doGVuCmwJE8iFcwQRlO6F7n4oJQof96a30cvxvuaUaTakuvpnib7zjikH0X0WbHiCOgB.png?v=1&k=a&s=api&e=1794528000&sig=IVQ5BoTTqRTB9guYaaLgK3kMKtgVh41aG0RuJpGNjkY) Then create two variables of type: **Custom JavaScript Code — Custom JavaScript** ### CJS - Meta value gross ```javascript function () { var net = Number({{DLV - ecommerce.value}}) || 0; var tax = Number({{DLV - ecommerce.tax}}) || 0; return Math.round((net + tax) * 100) / 100; } ``` This variable calculates the gross value: `net value + tax` ### CJS - Meta contents ```javascript function () { var items = {{DLV - ecommerce.items}} || []; return items.map(function (item) { return { id: String(item.item_id), quantity: item.quantity || 1, item_price: item.price }; }); } ``` This variable maps the `items` array from the Landing Page to the `contents` format required by Meta. ![](https://files.gleap.io/pf/gattachments/ux37erYXEghoKlApapIXjchFxEw6sinGFbssHZ6hZKEDmq4nG7arhr37vkDLfdUZisEakbAySWr.png?v=1&k=a&s=api&e=1794528000&sig=3IanKa92JsT_P6X39lM2bzkqYNeYaYru6kMySRTHrXc) ## Step 3. Create triggers Create triggers of type: **Custom Event** The event name must be exactly the same as the name sent by the Landing Page to `dataLayer`. Create: - `CE - view_item` - `CE - add_to_cart` - `CE - begin_checkout` - `CE - add_payment_info` - `CE - purchase` Additionally, create: - `CE - update_consent (marketing granted)` Set: - event name: `update_consent`, - trigger: **Some custom events**, - condition: `DLV - consent.ad_storage` **equals** `granted` ## Trigger PageView for Landing Page Landing Page Meeting Application works as an SPA application — the URL can change without a full page reload. Therefore, for subsequent `PageView` create a trigger of type: **History Change — History Change** **(**(History Change; `HC - all history changes`, without conditions)**,** without additional conditions. ![](https://files.gleap.io/pf/gattachments/IpihQg3MmbQdiBSrGW4BzweqQMx5XYgT33E9I5xza54hhiuQWo90duPmGsNZP8c5JMh4iNFJEwb.png?v=1&k=a&s=api&e=1794528000&sig=WVbvhRf9dtuFaAfo4qjXTXoo-TDW-Gkb-OspaNNpsjc) ## Step 4. Add base Meta Pixel tag Create a tag of type: **Custom HTML** Set as trigger: `CE - update_consent (marketing granted)` Then go to: **Advanced settings → Tag firing options** and select: **Once per page** Paste the code below: ```html ``` ![](https://files.gleap.io/pf/gattachments/KqNEx6xmTdVZ6cI82o52xiOQeyjTPPdgVq7DtrqdHxSPMgFafc9iSOtpZeZKOlxPFSm4cAXKvLZ.png?v=1&k=a&s=api&e=1794528000&sig=qSTwqHo9w-ZND1E7_q4HoIDLwTuZnNXgaUm6Z01gX8k) Replace: `TWOJ_PIXEL_ID` with your correct Pixel ID. `autoConfig=false` disables automatic Meta events. `disablePushState = true` disables automatic `PageView` sent by `fbevents.js` during URL changes in your SPA application. You will configure PageView during navigation yourself in the next step. > ### What happens before marketing consent? > > The base tag only launches after receiving the signal: `consent.ad_storage = granted` > > Events occurring earlier — including the first `PageView` before accepting Cookiebot — will not be sent to Meta. ## Step 5. Add event tags Create each of the following tags as: **Custom HTML** In the code, replace: `TWOJ_PIXEL_ID` with your correct Pixel ID. ### PageView Trigger: `HC - all history changes` ```html ``` The condition comparing `location.pathname` protects against sending two `PageView` events if the Landing Page changes history in more than one step. ### ViewContent Trigger: `CE - view_item` ```html ``` ### AddToCart Trigger: `CE - add_to_cart` ```html ``` ### InitiateCheckout Trigger: `CE - begin_checkout` ```html ``` ### AddPaymentInfo Trigger: `CE - add_payment_info` ```html ``` ### Purchase Trigger: `CE - purchase` ```html ``` In this event: - `value` is the gross value, - `currency` specifies the currency, - `contents` contains items from the cart, - `eventID` uses `transaction_id`. The same `eventID` can be used for deduplication if you implement server-side Conversions API in the future. ![](https://files.gleap.io/pf/gattachments/BMZncbby3WJmz1MFwZZkAdugZMusT9Tn43uCdBJ4DE5ZYhOBSB9s08z9GVJN8wDDyLCMV7iPuUs.png?v=1&k=a&s=api&e=1794528000&sig=tSNwCAGWmZ2kuRI4NO3xB4sRaZ0qrT8kDcwntD7Ld5k) > ### ⚠ Do not use tag sequencing > > Do not set the base Meta Pixel tag as the trigger for subsequent event tags. > > The base tag works with the **"Once per page"** setting. On the next GTM trigger attempt, it may block its re-execution, and as a result, also block the event tag. > > In the codes above, a condition is used instead: `if (window.fbq)` > > If the user has not given consent and the base Pixel has not been triggered, subsequent events will not be sent. > ### ⚠ Use `trackSingle`, not `track` > > For `PageView` on Landing Page SPA use: > > `fbq('trackSingle', ...)` > > Regular `fbq('track', 'PageView')` can be deduplicated by `fbevents.js`, which means subsequent PageView calls triggered by History Change will not be sent correctly. > > `trackSingle` additionally specifies a specific Pixel ID. ## Alternative — Facebook Pixel template from Community Template Gallery Instead of Custom HTML tags, you can use the template: **Facebook Pixel** from **Community Template Gallery**, publisher: `facebookincubator` The template supports: - base code, - standard events, - Object Properties, - Event ID. Parameter mapping remains the same as in the configuration described earlier. > ### Remember > > The template does not set `disablePushState`. > > If you choose this variant, during testing verify in particular whether duplicate `PageView` events do not appear during navigation on the Landing Page. ## Custom events — optional The basic configuration includes events that have direct equivalents among [Meta standard events](https://developers.facebook.com/docs/meta-pixel/reference#standard-events). You can use other events from `dataLayer` as **custom events**.

dataLayer Event	Standard Meta Event	Possible Mapping
`remove_from_cart`	none	`RemoveFromCart`
`view_cart`	none	`ViewCart`
`view_item_list`	none	`ViewItemList`
`add_shipping_info`	none	skip - in Meeting App this is a technical step "Email", not an actual shipment
`checkout_progress`	none	`CheckoutProgress`

### What custom events are for — and what they're not for You can send custom events via: `fbq('trackSingleCustom', ...).` - **They do not power** standard campaign optimization the way `Purchase` or `AddToCart` do — Meta doesn't know what they mean. - **They are used to build custom audiences** — for example, retargeting people who reached step 2 of checkout (`CheckoutProgress` with `checkout_step ≥ 2`), but don't have `Purchase`. This is their main value. - You can define **custom conversions** based on them in Events Manager and then optimize your campaign on such a conversion. - Format limitations: name up to 50 characters, parameter keys without spaces. > **Success:** **Recommendation:** to start, skip this section. Add custom events only when a specific retargeting scenario that needs them comes up — each tag is additional traffic and noise in Events Manager. ## Example: RemoveFromCart Trigger: `CE - remove_from_cart` ```html ``` ## Example: CheckoutProgress First, create an additional Data Layer Variable: `DLV - checkout_step` Key: `checkout_step` Then use: ```html ``` Just like in basic events, use: `if (window.fbq)` instead of tag sequencing. ### What about free tickets? If a participant obtains a free ticket through the basket on the Landing Page Meeting Application, they still go through the standard flow: **basket → checkout → finalization** Therefore, registration ends with the event: `Purchase` with: `value: 0` You do not need to create an additional registration event for such a process. ## Step 6. Check your configuration ![](https://files.gleap.io/pf/gattachments/XVm6KgHrLSWZoqeNAhn9hDIRbLA2XzkJQ61jXAwruCND88bVcoClYH1LpOoYvY6zY85zUkODpmt.png?v=1&k=a&s=api&e=1794528000&sig=CgmZbXG2ICJXW8IHF7Q7wAlseWVl2nhfE4RPrMYbt1g) Before launching your campaign, perform a full test. If you are using Path B, open simultaneously: - **GTM Preview**, - **Meta Events Manager → Test Events**. Then go through the user process on the Landing Page.

What are you doing?	What should happen?
You open the Landing Page before accepting Cookiebot	No requests to Meta to `facebook.com/tr`
You accept marketing consent	A `PageView`
You navigate between subpages	Exactly one `PageView` per navigation
You add a ticket to your cart	`ViewContent` + `AddToCart`
You start checkout	`InitiateCheckout`
You select a payment method	`AddPaymentInfo`
You finalize your purchase	`Purchase` with gross value and Event ID
You reject marketing consent	No traffic to `facebook.com/tr`

For purchase events, also check the following parameters: - `value`, - `currency`, - `contents`. For `Purchase` additionally check: - gross value, - `Event ID`. ## Most common pitfalls ### Events are counted twice First, check whether both of the following are active simultaneously for your Landing Page: - built-in Meta Pixel from Path A, - Meta Pixel tags in your GTM. One event should use **one Meta event source**. ### Purchase has net value Do not use directly: `ecommerce.value` as the value of `Purchase`. `ecommerce.value` is the net value. For `Purchase` use: `CJS - Meta gross value` which is: `ecommerce.value + ecommerce.tax` ### PageView is counted twice Check if the base code contains: `fbq.disablePushState = true` Without this `fbevents.js` may independently send PageView when the URL changes, in parallel with your tag triggered by History Change. ### `contents` does not contain `quantity` Meta requires `id` and `quantity` for each item. Variable: `CJS - Meta contents` ensures their correct mapping. ### Currency has incorrect format `currency` should contain the currency code, e.g.: `PLN` not the symbol: `zł` Landing Page passes the currency code in the correct format. ## Before launching the campaign Make sure that: - you are using only one Meta Pixel path, - Cookiebot is properly configured, - the Landing Page domain has been added in Cookiebot, - the correct GTM container is connected to the event, - automatic Meta events are disabled, - you have completed a full user path test, - `Purchase` passes the correct value, currency, and Event ID. If you are unsure which Meta Pixel configuration is active for your event, **contact us before publishing tags or launching a campaign**. **Successful event with Meeting Application!**