# Meta Pixel Tracking for Events > Learn how to add Meta Pixel tracking to GHL Customer Care Events, map RSVP and ticket actions, track conversions, and send purchase data to Meta campaigns. - Source: https://docs.ghlcustomercare.com/docs/marketing/events/meta-pixel-tracking-for-events - Section: Marketing / Events - Reading time: 5 min - Images: 7, each explained below - Modified on Wed, 2 Sep at 10:40 AM --- Meta Pixel tracking in GHL Customer Care Events helps organizers measure how visitors move from viewing an event to completing an RSVP or ticket order. By connecting a Meta Pixel to an individual event, you can map attendee actions to Meta events and measure important conversion points. Ticketed events can also send purchase details such as order value, currency, ticket quantities, and ticket identifiers. --- **TABLE OF CONTENTS** - [What is Meta Pixel Tracking for Events?](#what-is-meta-pixel-tracking-for-events) - [Key Benefits of Meta Pixel Tracking for Events](#key-benefits-of-meta-pixel-tracking-for-events) - [Supported Meta Pixel Tracking Events](#supported-meta-pixel-tracking-events) - [Purchase Data Sent to Meta](#purchase-data-sent-to-meta) - [How To Setup Meta Pixel Tracking for Events](#how-to-setup-meta-pixel-tracking-for-events) - [Frequently Asked Questions](#frequently-asked-questions) - [Related Articles](#related-articles) --- # **What is Meta Pixel Tracking for Events?** Meta Pixel Tracking for Events connects attendee activity in a GHL Customer Care event with Meta conversion events. This gives organizers better visibility into registration intent, completed registrations, and ticket purchases generated through their event marketing. Meta Pixel tracking is configured independently for each event under **Settings → Link & tracking**. --- ## **Key Benefits of Meta Pixel Tracking for Events** - **Conversion visibility:** Measure attendee activity from the initial event page visit through a completed RSVP or ticket order. - **Flexible event mapping:** Choose which Meta event should fire for each supported attendee action. - **Event-level configuration:** Configure Meta Pixel tracking independently for each event. - **Ticket purchase insights:** Track multiple stages of the ticket checkout journey. - **Revenue context:** Send supported purchase details with completed ticket orders. - **Duplicate-event protection:** Session-based deduplication helps reduce repeated conversion signals. --- ## **Supported Meta Pixel Tracking Events** RSVP and Ticketed events have different attendee journeys, so GHL Customer Care provides tracking actions that correspond to the steps visitors complete for each event type. | Event type | Supported attendee actions | | --- | --- | | **RSVP Events** | Event page viewed, RSVP started, RSVP completed | | **Ticketed Events** | Event page viewed, Checkout started, Ticket selection completed, Registration form submitted, Payment details submitted, Ticket order completed | | Event Type | Attendee Action | When It Fires | | --- | --- | --- | | **RSVP** | Event page viewed | When a published event page is loaded | | **RSVP** | RSVP started | When a visitor opens the RSVP form | | **RSVP** | RSVP completed | When the RSVP is successfully confirmed | | **Ticketed** | Event page viewed | When a published event page is loaded | | **Ticketed** | Checkout started | When the attendee begins checkout | | **Ticketed** | Ticket selection completed | When ticket selection is completed | | **Ticketed** | Registration form submitted | When the registration form is submitted | | **Ticketed** | Payment details submitted | When payment details are submitted | | **Ticketed** | Ticket order completed | When the ticket order is successfully completed | Completed ticket orders are tracked for both paid tickets and **$0 orders**. **Purchase data:** Completed ticket orders can also send order value, currency, ticket quantities, and ticket identifiers to Meta. **Deduplication:** GHL Customer Care uses session-based deduplication to help prevent the same attendee action from being reported multiple times because of browser back navigation, page refreshes, payment redirects, or repeated completion checks. ![Supported Meta Pixel Tracking Events (image 1 of 7)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155079933950/original/2wr708qTk62B0A5O1VZdWhvpdHEjWn6eiw.png) **Supported Meta Pixel Tracking Events (image 1 of 7)** This screenshot appears in the "Supported Meta Pixel Tracking Events" section of "Meta Pixel Tracking for Events". The text alongside this image reads: Deduplication: GHL Customer Care uses session-based deduplication to help prevent the same attendee action from being reported multiple times because of browser back navigation, page refreshes, payment redirects, or repeated completion checks. Immediately after, the guide continues: A completed ticket order can provide more context than a registration count alone. Commerce details help organizers evaluate the value and composition of ticket purchases generated through their event marketing. - What this covers: Deduplication: GHL Customer Care uses session-based deduplication to help prevent the same attendee action from being reported multiple times because of browser back navigation, page refreshes, payment redirects, or repeated completion checks. - Controls: RSVP Events, Ticketed Events, RSVP, Ticketed, $0 orders - Next: A completed ticket order can provide more context than a registration count alone. Commerce details help organizers evaluate the value and composition of ticket purchases generated through their event marketing. --- ## **Purchase Data Sent to Meta** A completed ticket order can provide more context than a registration count alone. Commerce details help organizers evaluate the value and composition of ticket purchases generated through their event marketing. Completed ticket orders can include: - **Order value:** The value associated with the completed ticket order. - **Currency:** The currency associated with the order. - **Ticket quantities:** The number of tickets represented in the order. - **Ticket identifiers:** Identifiers associated with the tickets included in the transaction. This additional data is associated with completed ticket orders and can support campaign reporting focused on revenue outcomes rather than registrations alone. --- ## **How To Setup Meta Pixel Tracking for Events** Using the correct Meta Pixel ID and mapping the attendee actions that matter to your campaign ensures the conversion data represents the event journey you want to measure. ### 1\. Locate Your Meta Pixel ID Locate the Pixel ID for the Meta data source you want to connect to your event. GHL Customer Care's existing Meta documentation explains how to locate the Dataset ID used as the Pixel ID in Meta Events Manager. ![1. Locate Your Meta Pixel ID (image 2 of 7)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155079934081/original/Qk4kMpRcJ9x7MQmEjdhVOKSFdfdIVwLzRg.png) **1. Locate Your Meta Pixel ID (image 2 of 7)** This screenshot appears in the "1. Locate Your Meta Pixel ID" section of "Meta Pixel Tracking for Events". The text alongside this image reads: GHL Customer Care's existing Meta documentation explains how to locate the Dataset ID used as the Pixel ID in Meta Events Manager. Immediately after, the guide continues: How to set up a Funnel Event Pixel for Facebook Conversion API? - What this covers: GHL Customer Care's existing Meta documentation explains how to locate the Dataset ID used as the Pixel ID in Meta Events Manager. - Next: How to set up a Funnel Event Pixel for Facebook Conversion API? [**How to set up a Funnel Event Pixel for Facebook Conversion API?**](https://docs.ghlcustomercare.com/docs/integrations/facebook-integration/how-to-set-up-a-funnel-event-pixel-for-facebook-conversion-api) ### 2\. Open Link & tracking 1. In your GHL Customer Care sub-account, go to **Memberships → Events**. ![Step 1 of 4: In your GHL Customer Care sub-account, go to Memberships → Events](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155079934348/original/wbJEUuNvvYHsDawbdh1YP838tNuPskUXMw.png) **Step 1 of 4: In your GHL Customer Care sub-account, go to Memberships → Events** This screenshot accompanies step 1 of 4 in the "2. Open Link & tracking" section of "Meta Pixel Tracking for Events". At this point in the walkthrough you in your GHL Customer Care sub-account, go to Memberships → Events. The next step is to select the event you want to track. - What this covers: In your GHL Customer Care sub-account, go to Memberships → Events. - Controls: Memberships → Events, Settings, Link & tracking, Meta Pixel - Next: Select the event you want to track. Full procedure: 1. In your GHL Customer Care sub-account, go to Memberships → Events. <- this image 2. Select the event you want to track. 3. Open Settings andSelect Link & tracking. 4. Locate the Meta Pixel settings. 2. Select the event you want to track. 3. Open **Settings** andSelect **Link & tracking**. 4. Locate the **Meta Pixel** settings. ![Step 4 of 4: Locate the Meta Pixel settings](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155079934419/original/dMdBG7IG1iyv6dQ__wosrkxfGorpxLvH1g.png) **Step 4 of 4: Locate the Meta Pixel settings** This screenshot accompanies step 4 of 4 in the "2. Open Link & tracking" section of "Meta Pixel Tracking for Events". At this point in the walkthrough you locate the Meta Pixel settings. For context, this section explains: In your GHL Customer Care sub-account, go to Memberships → Events. Select the event you want to track. Open Settings andSelect Link & tracking. Locate the Meta Pixel settings. - What this covers: Locate the Meta Pixel settings. - Controls: Meta Pixel, Memberships → Events, Settings, Link & tracking Full procedure: 1. In your GHL Customer Care sub-account, go to Memberships → Events. 2. Select the event you want to track. 3. Open Settings andSelect Link & tracking. 4. Locate the Meta Pixel settings. <- this image ### 3\. Add the Meta Pixel ID Enter the **Meta Pixel ID** associated with the Meta data source you want to use for this event. Meta Pixel tracking is configured independently for each event, so confirm that you are editing the correct event before configuring the mappings. ![3. Add the Meta Pixel ID (image 5 of 7)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155079934567/original/OUp8f5LCNZIc8mxoFisPGUee1zyQ0oDpQA.png) **3. Add the Meta Pixel ID (image 5 of 7)** This screenshot appears in the "3. Add the Meta Pixel ID" section of "Meta Pixel Tracking for Events". The text alongside this image reads: Meta Pixel tracking is configured independently for each event, so confirm that you are editing the correct event before configuring the mappings. Immediately after, the guide continues: Use the Event mapping options to choose which Meta event should fire for each supported attendee action. - How to confirm: Meta Pixel tracking is configured independently for each event, so confirm that you are editing the correct event before configuring the mappings. - Controls: Meta Pixel ID - Next: Use the Event mapping options to choose which Meta event should fire for each supported attendee action. ### 4\. Map Attendee Actions to Meta Events Use the **Event mapping** options to choose which Meta event should fire for each supported attendee action. For RSVP events, configure mappings for: 1. Event page viewed 2. RSVP started 3. RSVP completed For Ticketed events, configure mappings for: 1. Event page viewed 2. Checkout started 3. Ticket selection completed 4. Registration form submitted 5. Payment details submitted 6. Ticket order completed ![4. Map Attendee Actions to Meta Events (image 6 of 7)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155079934781/original/cwnhhJHVQf4bqr0na5-4hqBCXbA4N_6CqA.png) **4. Map Attendee Actions to Meta Events (image 6 of 7)** This screenshot appears in the "4. Map Attendee Actions to Meta Events" section of "Meta Pixel Tracking for Events". The text alongside this image reads: Event page viewed Checkout started Ticket selection completed Registration form submitted Payment details submitted Ticket order completed. This part of the guide covers 8 fields, listed below. Immediately after, the guide continues: Use the published event experience to verify the actions that matter to your tracking plan. The Event page viewed action is defined for published event-page loads, so testing against the public experience is the appropriate way to…. - What this covers: Event page viewed Checkout started Ticket selection completed Registration form submitted Payment details submitted Ticket order completed - Fields: Event page viewed, RSVP started, RSVP completed, Checkout started, Ticket selection completed, Registration form submitted, Payment details submitted, Ticket order completed - Controls: Event mapping - Next: Use the published event experience to verify the actions that matter to your tracking plan. The Event page viewed action is defined for published event-page loads, so testing against the public experience is the appropriate way to validate that part of the journey. Full procedure: 1. Event page viewed 2. RSVP started 3. RSVP completed ### 5\. Test the Attendee Journey Use the published event experience to verify the actions that matter to your tracking plan. The **Event page viewed** action is defined for published event-page loads, so testing against the public experience is the appropriate way to validate that part of the journey. For an RSVP event, test the page view, opening the RSVP form, and a successful RSVP. For a Ticketed event, test the relevant checkout stages through a completed order, including a $0 ticket order when that is part of your use case. ![5. Test the Attendee Journey (image 7 of 7)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155079934969/original/oj3FhtZr5neYQkb-b848rkEnTd4b-16Lfg.png) **5. Test the Attendee Journey (image 7 of 7)** This screenshot appears in the "5. Test the Attendee Journey" section of "Meta Pixel Tracking for Events". The text alongside this image reads: For an RSVP event, test the page view, opening the RSVP form, and a successful RSVP. For a Ticketed event, test the relevant checkout stages through a completed order, including a $0 ticket order when that is part of your use case. Immediately after, the guide continues: Q: Is Events Meta Pixel tracking the same as an Ad Manager conversion pixel? No. Events Meta Pixel tracking is configured directly within an individual GHL Customer Care event under Settings → Link & tracking. Ad Manager conversion tracking…. - What this covers: For an RSVP event, test the page view, opening the RSVP form, and a successful RSVP. For a Ticketed event, test the relevant checkout stages through a completed order, including a $0 ticket order when that is part of your use case. - Controls: Event page viewed - Next: Q: Is Events Meta Pixel tracking the same as an Ad Manager conversion pixel? No. Events Meta Pixel tracking is configured directly within an individual GHL Customer Care event under Settings → Link & tracking. Ad Manager conversion tracking uses a separate configuration process. --- ## **Frequently Asked Questions** **Q: Is Events Meta Pixel tracking the same as an Ad Manager conversion pixel?** No. Events Meta Pixel tracking is configured directly within an individual GHL Customer Care event under **Settings → Link & tracking**. Ad Manager conversion tracking uses a separate configuration process. **Q: Do I need to install Funnel tracking code to use Meta Pixel tracking for Events?** The native Events integration is configured directly in the event using the Meta Pixel ID and Event mapping settings. Funnel tracking code belongs to a separate Funnel or Website tracking setup. **Q: Are $0 ticket orders tracked?** Yes. Successfully completed $0 ticket orders are tracked as completed ticket orders. **Q: Can Meta Pixel tracking report attendee check-ins?** Check-in is not listed as a supported Meta Pixel tracking action for this feature. GHL Customer Care provides separate Events workflow triggers for registration and check-in automation. **Q: Does previewing an unpublished event trigger Event page viewed?** The feature defines **Event page viewed** as occurring when a published event page is loaded. --- ## **Related Articles** - **[How to Create and Manage Events in GHL Customer Care](https://docs.ghlcustomercare.com/docs/marketing/events/how-to-create-and-manage-events-in-ghl-customer-care) ** - **[How to set up a Funnel Event Pixel for Facebook Conversion API?](https://docs.ghlcustomercare.com/docs/integrations/facebook-integration/how-to-set-up-a-funnel-event-pixel-for-facebook-conversion-api) ** - **[Facebook Conversions API Trigger in Workflows](https://docs.ghlcustomercare.com/docs/integrations/facebook-integration/facebook-conversions-api-trigger-in-workflows) ** - **[Events and Workflows Integration](https://docs.ghlcustomercare.com/docs/marketing/events/events-and-workflows-integration) ** - [**Embed Events with Code Snippet**](https://docs.ghlcustomercare.com/docs/marketing/events/embed-events-with-code-snippet) --- Documentation for GHL Customer Care. Support: support@ghlcustomercare.com