Meta (Facebook) Pixel logo

Meta (Facebook) Pixel

SalesIntegration

About Meta (Facebook) Pixel

Meta's ad tracking for Facebook and Instagram. Bask reports purchases from your intake flows to Meta, so ad spend is attributed to real sales.

How Bask works with Meta (Facebook) Pixel

  • With a Conversions API access token, Bask sends a Purchase event for each sale straight from its servers to Meta. Without the token, no direct report is sent.
  • The event carries the order value in US dollars and the product variants that were bought.
  • Patient details such as email, phone, name, city, state, zip and country are hashed with SHA-256 before they are sent. Bask also passes the browser's fbc and fbp IDs, the IP address and the user agent when it has them.
  • This connection does not add a browser pixel to Studio sites. If you also want reports from the patient's browser, add them through Google Tag Manager.
  • The purchase data layer on Studio flows includes an event_id that matches the ID Bask sends to Meta. Pass the same event_id from a browser tag and Meta can count the sale once.
  • A test event code applies to the reports Bask sends directly. It does not redirect browser reports or switch off campaign reporting.

Set up Meta (Facebook) Pixel

  1. Open App Store in your Bask sidebar, choose Meta (Facebook) Pixel, then choose Connect.
  2. Enter the Pixel ID from Meta Events Manager. It accepts digits only, so paste the ID and not a script snippet.
  3. To send direct purchase reports, add your Conversions API access token.
  4. For live use, leave Test event code empty. To run a test, enter the code Meta shows in Events Manager.
  5. Choose Connect in the save bar.
  6. If you add a browser purchase tag in Tag Manager, pass the same event_id so Meta does not count the sale twice.

What you need for Meta (Facebook) Pixel

Your numeric Pixel ID from Meta Events Manager. Optionally a Conversions API access token for direct purchase reports, and a test event code while you verify.

Good to know

  • Leave the test event code empty in production.
  • Disconnecting stops new reports. Events already sent stay in Meta, and browser tags you installed in Tag Manager have to be managed there.

Who it is for

Usually set up by a marketing agency with permission to manage integrations in Bask. It suits teams that run Facebook or Instagram ads and want purchases credited to the campaigns that drove them.

How it installs

Installed with keys you paste in