A Facebook pixel is a snippet of code that allows you to track the key actions your audience takes on your event page. Those actions, or events, are sent straight to your Facebook Event Manager for you to analyze.

On this page:

Creating a Facebook pixel

You can create a Facebook pixel with a few simple clicks inside the Facebook Events Manager.

Facebook pixels and Splash

Facebook pixels can be installed by a member of Splash support on a single event page, or even better, on any branded or custom theme. If the latter, the pixel will be applied to any event page created from that theme moving forward so you don’t have to lift a finger.

The pixel can fire on certain events:

1. Initial page load

2. Opening the RSVP or Ticket form (not compatible with inline forms)

3. Loading the ticketing checkout page (ticketed events only)

4. After submitting an RSVP or ticket purchase

The Splash Support team can help set up the pixel to fire on page load, but other events require additional scoping and are completed as a service at cost. Additionally, if you need a pixel to fire on page load and another event, this will also be a service that the Splash Support team cannot complete on your behalf.

Verifying your event domain

Apple recently announced changes to iOS 14 that impact how conversion events are received and processed from tools like Facebook. Read more about the release.

As a result, there are a few actions Facebook requires you to take to ensure the pixel will perform as expected:

• Your Splash event page should have a valid vanity domain.
• Once your domain is set up, it should be submitted for verification within your Facebook Business Manager account. Read Facebook's step by step instructions for how to complete this verification. Keep in mind these steps cannot be completed by Splash.
• Once verified, take the TXT DNS record that the Facebook Business Manager provides and add it to your existing DNS settings for that domain.

Implementing a Facebook pixel

Reach out to the Splash Support team with the following information to get the process started:

1. The pixel in a .txt file attachment. Why? Sometimes copy or pasting the the pixel into the body of an email can alter the formatting of the code, which could lead to an error upon implementation. Using an external .txt file to store this code will avoid that. We want to make sure that we get this right on the first try!
2. The URL(s) of the Splash event pages and themes you'd like this pixel placed on. Please note that if the scope includes multiple pages, the work will be scoped for time and potential cost. 

3. When you would like this pixel to fire. As a reminder, you have four options:

   1. Initial page load

   2. Opening the RSVP or Ticket form

   3. Loading the ticketing checkout page

   4. After submitting an RSVP or ticket purchase