Skip to main content

Meta (Facebook) Pixel Integration

Track website conversions and optimize your ad campaigns with Meta Pixel!

The Meta (Facebook) Pixel helps you track marketing events when users visit your page, browse content, go through checkout, or make purchases.

Uscreen fires a full set of standard Meta events across browsing, checkout, and purchase β€” and supports Meta's Conversions API (CAPI) to capture trial-to-paid conversions that the browser pixel can't see.

Creating a Pixel

If you don't already have a pixel, you will need to first create it by navigating to Events Manager on your Meta for Business account.

  1. On the left sidebar, hover over the Connect Data

  2. Select Web

  3. Click Connect

  4. Select Facebook Pixel

  5. Click Connect

  6. Click Continue

  7. Add your Pixel Name

  8. Click Continue


Getting your Pixel ID

After you have created the pixel, a pop-up window will appear for you to choose how to install your pixel.

Under the Manually add pixel code to website option, click on Install code manually.

In the first step, you will be asked to copy the base code.

You only need the Pixel ID to connect to Uscreen. Click the Copy Code button, then paste the snippet into a text editor so you can see it in full.

Find your Pixel ID, usually on the 11th line:

fbq('init', 'PIXEL ID');

πŸ“ NOTE: Copy only the value inside the apostrophes β€” don't include the apostrophes themselves.


Connecting to Uscreen

After copying your Pixel ID, go to your Uscreen account.

  1. Navigate to Settings > Integrations

  2. Find Facebook, and click Connect

  3. Paste your Pixel ID into the Pixel ID field

  4. (Optional but recommended) Paste a Conversions API Access Token β€” see the next section for how to generate one and what it unlocks

  5. Click Connect

ℹ️ INFO: That's all you need to do on the Uscreen side! You don't need to add the code anywhere else.


Enabling the Conversions API (optional, recommended)

Uscreen also supports Meta's server-side Conversions API (CAPI) for one specific high-value event: a free trial converting to a paid subscription.

When a trial ends and the user is charged for the first time, the conversion happens server-side β€” the customer isn't on your site, so the browser pixel can't fire. Without CAPI, Meta never sees those paid conversions and can't optimize your trial-funnel campaigns. CAPI closes that gap.

To enable it:

  1. In Meta Events Manager, generate a Conversions API Access Token for your pixel β€” see Meta's guide

  2. In Uscreen, go to Settings > Integrations > Facebook

  3. Paste the token into the Conversions API Access Token field and save

Once enabled, when a trial subscription converts to paid, Uscreen sends a server-side Purchase event to Meta with the paid amount, the customer's hashed email, IP, user agent, and Facebook click identifiers (fbclid / fbc / fbp) β€” within a 28-day attribution window from signup.

ℹ️ INFO: CAPI events are only sent when the token is configured and the user has a Facebook attribution identifier captured within the last 28 days. Sign-ups older than that, or sign-ups without any Meta click attribution, are not sent server-side.


Technical Specs for Uscreen's Meta Pixel Integration

Uscreen fires the following Meta standard events. Add the ones you want to optimize for in the Review Events section of Meta Events Manager.

Event Name

When it fires

PageView

Every page load on your storefront

ViewContent

Viewing a program or collection page

InitiateCheckout

Landing on the checkout page (offer selection or session checkout)

Lead

Signing up and moving to the Payment Details step of checkout

StartTrial

Completing checkout for an offer that includes a free trial

Subscribe

Completing checkout for a subscription offer (no trial)

Purchase

Completing checkout for a one-time purchase, donation, or gift. Also sent server-side via the Conversions API when a free trial converts to a paid subscription (requires a Conversions API Access Token).

πŸ“ NOTE: StartTrial, Subscribe, and Purchase are mutually exclusive on the checkout success page β€” exactly one fires per successful checkout, based on the offer type.

Example payload of what is pushed to the Facebook Pixel:

fbq("track", "Purchase", { content_name: "Monthly Subscription", value: 12.0, currency: "USD" })

πŸ’‘ TIP: The 'value' is the amount after any discount.

Also, note that the checkout workflow is dynamic, so you will only see certain events in Meta Pixel Helper (Google Chrome extension) during certain portions of the checkout process.

  • For example, the 'Customer Information' view may show PageView and InitiateCheckout events.

  • The 'Complete Order' view may show PageView and Lead events.

  • The confirmation page (which only appears for around 5 seconds after the Complete Order step) may show PageView and the relevant purchase event (StartTrial, Subscribe, or Purchase).

⚠️ WARNING: The Meta Pixel integration is only available for website tracking and does not track mobile app purchases.


Known Limitations

While the Meta Pixel integration covers most of the storefront and checkout funnel, there are some limitations to be aware of.

Free Trial Conversions (requires the Conversions API)

When a user signs up for a free trial, the StartTrial event fires on the checkout confirmation page. The first paid charge happens later, server-side, when the trial ends β€” and at that point the user isn't on your site, so the browser pixel can't fire.

  • Without a Conversions API Access Token configured: the trial-to-paid conversion is not sent to Meta. You can't measure or optimize trial conversions in this mode.

  • With a Conversions API Access Token configured: Uscreen sends a server-side Purchase event to Meta with the paid amount, within a 28-day attribution window from the trial signup.

πŸ“ NOTE: To capture trial-to-paid conversions, see Enabling the Conversions API above.

Recurring Subscription Payments are not tracked

Recurring subscription renewals (e.g., monthly or annual charges after the first billing cycle) are processed server-side by your payment provider without any browser interaction, and Uscreen does not send them to Meta β€” even with the Conversions API enabled.

Meta's standard ads-attribution windows are designed around the initial conversion, so renewals are not generally needed for ad optimization.

Tracking Accuracy Limitations

Even with both the Pixel and the Conversions API enabled, tracking accuracy can be reduced by:

  • Ad blockers that prevent the pixel script from loading

  • iOS 14.5+ App Tracking Transparency: users who opt out of tracking on iOS devices will not have their conversions attributed to your Meta ads

  • Browser privacy features: Safari's Intelligent Tracking Prevention (ITP), Firefox's Enhanced Tracking Protection, and similar features can limit cookie persistence and block tracking scripts

The Conversions API mitigates ad blockers and browser-side blocking for trial-to-paid conversions specifically, but does not bypass user opt-outs (e.g., ATT).

Mobile App Purchases are not tracked

The Meta Pixel integration only works on your web storefront.

Purchases made through iOS, Android, or TV apps are not tracked by the pixel, as these transactions are handled through the respective app stores.

Confirmation Page Timing

The checkout confirmation page, where StartTrial, Subscribe, or Purchase fires, only appears for approximately 5 seconds before redirecting.

If the pixel takes longer to load (due to network latency or browser conditions), the event may not fire successfully. For the trial-to-paid Purchase event specifically, enabling the Conversions API removes this timing risk because the event is sent server-side.

πŸ”— Learn more about the Checkout Purchase Flow


Verify your Domain

Make sure you've verified your domain.

πŸ”— Learn more about Verifying your Domain

If you're using a Uscreen domain, you'll need to place a <meta> tag in the Head Code Snippet.

πŸ”— Learn more about the Head Code Snippet

πŸ“ NOTE: Please be patient as the verification process may take some time, and so does the data to appear in the Events Manager, especially if newly connected.


Test the Pixel integration

To test it, add the Meta Pixel Helper extension to your Google Chrome browser. Go to the Chrome web store, search for Meta Pixel Helper, click on the plugin offered by Meta, and select Add to Chrome.

You can find the extension by clicking on the puzzle piece icon located on the right of the navigation bar of the Chrome browser.

Click on the pin icon to make it easier to find.

Go to your site's storefront and click on the Facebook Pixel Helper extension.

Return to the Events Manager page, and on the left sidebar, select Data Sources. Make sure your pixel is selected to have access to all of your pixel's details.

πŸ“ NOTE: Additionally, please note that our Support Team is not equipped to assist with troubleshooting the Meta Events Manager. For any inquiries regarding Meta and Pixels, we suggest seeking assistance from Meta support or a marketing professional.

Did this answer your question?