How to add Facebook Pixel and setup events

In this article, you will learn how to integrate the Facebook pixel on different pages on systeme.io and set up events.

You will need:

• Facebook business account
• Facebook ad account
• Systeme.io account
• Custom domain

1. Set up your Pixel

1.1 Go to your Facebook Business Settings, then click Settings.

Now, click on Data sets & Pixels under Data sources.

Click on Add, and you will be presented with a popup where you can name your Pixel. Once you have entered a name for your pixel, click on Create.

Another popup will appear that says, Your pixel isn't ready to use yet. You can close that popup as you first need to add People and Assets to your Pixel.

1.2 Click Assign people, then select your business account from the popup. Click on the slider to give Full control and then click on Assign.

1.3 Once completed, click Connect assets.

You will be presented with another popup where you only need to check the ad account, then click on Add.

2. Install the Pixel on your website

2.1 Click on All tools on the left-side menu, and then click on Events Manager.

2.2 Click on your Pixel.

2.3 Click Set up Meta Pixel.

2.4 Now, click on Install Code Manually below the Manually add Pixel code to website option.

The Meta Pixel code will appear. This needs to be added to the 'Header code' section of your funnel pages. If you want to install the code on all the pages of all of your funnels, you can put it in the Tracking Code field under sales funnel settings.

2.4.1 Adding the Facebook Pixel code to the sales funnel page settings

Note: It's important to include your Facebook Pixel code on all the pages of your sales funnel.

2.4.2 Adding the Facebook Pixel code from the sales funnel settings

You can also insert your Facebook Pixel code into the Sales Funnel settings to automatically deploy it across all sales funnels.

Click Settings under your profile picture, then Sales funnel, and insert the Facebook Pixel code in the tracking code field.

2.5 After copying the code and adding it to your website as mentioned above, click on Continue. You will be given the option to activate Automatic advanced matching. This is optional and based on your preference.

2.6 Click on Continue to proceed.

Once the Meta pixel base code is installed on your website, check it as done (Green icon). You can now set up events on your website by clicking Set up events.

The event setup tool doesn't always work, and in this example, we will be manually adding the event code to the Meta Pixel code.

2.7 For the manual option, click on Install using code on the popup that appears.

In this example, we will only use the View content event.

Add it to your funnels settings.

2.8 You will need to verify your domain now by navigating to Brand Safety and Suitability > Domains. Click Add. Enter your domain, and then click Add again.

You will be given a Meta-tag that needs to be added to the Header code of your page or in the sales funnel settings below the Meta Pixel code (ensure there is a line break between them).

After you have added the code, click on Verify domain on the Facebook side.

3. Test the installation

Now that your Pixel has been set up and installed, you can test it to see whether it is working.

Click on Test events, enter the URL of your website in the field labeled, and click on Test events.

The Test Events page should display the events from the actions you took on your website.

4. Deduplication of Events on Facebook (Pixel and CAPI)

Thanks to the deduplication of tracking for Facebook's Conversion API (CAPI) and the Pixel, you can now easily prevent double-counting of events between the browser (Pixel) and the server (CAPI). When the same event is sent via these two channels, Facebook identifies duplicates with a unique identifier (eventID), merges them automatically, and thus ensures the accuracy of the statistics.

How to implement deduplication?

To enable deduplication, ensure that both the Conversion API (CAPI) and Facebook Pixel are implemented correctly. If you haven’t set up CAPI yet, refer to this guide: How to configure the Facebook Conversions API on systeme.io.

For users with CAPI already implemented, deduplication will happen automatically by selecting the event type from the dropdown. However, the Pixel code must be updated to include the event ID placeholder. For each tracked event, the appropriate event ID's placeholder/variable must be added to ensure proper deduplication.

What is the Event ID?

The Event ID is a unique identifier generated for each conversion event (such as a purchase or an opt-in).

It allows Meta (Facebook) to avoid counting the same event twice when it is sent both via the Pixel (browser) and the Conversions API (CAPI).

• The Event ID is sent automatically through CAPI.
• In the Pixel, you need to manually add this identifier in the tracking code using the placeholders provided by systeme.io.

Below are examples of common events:

• Purchase: fbq('track', 'Purchase', {}, {eventID: '%FACEBOOK_PURCHASE_EVENT_ID%'});    
• Appointment: fbq('track', 'Schedule', {}, {eventID: '%FACEBOOK_EVENT_ID%'});               
• View Content: fbq('track', 'ViewContent', {}, {eventID: '%FACEBOOK_EVENT_ID%'});               
• Lead: fbq('track', 'Lead', {}, {eventID: '%FACEBOOK_NEW_LEAD_EVENT_ID%'});               

Important:

• These event codes are ready to use. You simply need to copy and paste them as they are, depending on the event you want to track.
• The placeholders (%FACEBOOK_EVENT_ID%  ) will be automatically replaced with the actual identifiers at the time of the conversion.

Below is a comprehensive example illustrating the configuration of deduplicating a view content event using the Facebook Pixel:

1. Select the appropriate event identifier: Write the event placeholder to generate a unique event ID.   This ID allows Facebook to recognize and merge events sent by both the Pixel and the Conversion API (CAPI). This identifier is unique for each event and automatically generated when the placeholder or variable is added. The placeholder ensures the value is dynamically replaced with the actual Facebook Event ID when the pixel is loaded.

2. Add the eventID to the Pixel code: Here’s how to send the view content event with the unique identifier:

3. Verification:

For Pixel tracking, visit the page to ensure that events like "View Content" are firing correctly with the associated Event ID  . The Facebook Pixel Helper extension will help verify that the Pixel is capturing events as expected.

For CAPI tracking, the user needs to navigate through your website to trigger server-side events.

• In the case of view content or lead detection, simply visiting the page will fire the event.
• For Purchase events, a test purchase must be completed to capture purchase amount values.
• Both CAPI and Pixel events can then be viewed in Meta Events Manager to confirm they are tracked correctly and that deduplication functions as intended.

Note: Ensure you use the exact placeholder {{FACEBOOK_EVENT_ID}}. systeme.io will automatically populate this with the unique ID from Facebook.

By following this example, you enable deduplication between the Pixel and CAPI, avoiding duplicates and ensuring accurate conversion data for your campaigns.

Tracking purchase amount using CAPI

To track the purchase amount using CAPI, follow these steps:

• Use the purchase event type.
• Capture the purchase amount along with the currency.
• If the product is physical, take the currency from the product.
• If the product is a digital offer or subscription, take the currency from the price plan.

Tracking order bumps and upsells separately

Users often ask if order bumps and upsells can be tracked separately from the main purchase event. Here’s how it works:

• The entire order value, including upsells, is sent at the time of the purchase event.
• Order bumps and upsells are typically added as digital products, similar to the main offer.
• CAPI on the Thank You Page will detect all previous purchases (main offer, bumps, and upsells) automatically.

Notes:

1. CAPI tracks the full order value, including all upsells and bumps, as long as they were part of the order at the time of the event.
2. Implementing CAPI on the Thank You Page ensures that all purchases (main offer, order bumps, and upsells) are recorded in one event.