29 NEXT
  • Welcome to 29 Next Docs
  • About 29 Next
  • Changelog
  • Start Here
    • 🌟Get Started on 29 Next
      • General Settings & Branding
      • Link Domains
      • Invite Team Members
      • Add Locations & Languages
      • Checkout Settings & Policies
      • Customer Storefront Accounts
      • Fulfillment Settings
      • Support & Notifications
      • Add Payment Providers
    • ⚡Developer Docs
  • BUILD A STORE
    • 📦Products Catalogue
      • Add Products
      • Inventory
      • Product Variants
      • Gift Cards
      • Upsells & SEO Settings
      • Create Categories
      • Google Merchant XML Feed
      • Tax Settings
    • 🛒Storefront
      • Customer Accounts
      • Support Content
      • Custom Pages
      • Blogs
      • Storefront Redirects
    • 🪄Technical Settings
      • Metadata Fields & Tags
      • Configure Webhooks
      • Storefront API & Events
  • Manage Orders
    • 📥Orders
      • Create Orders
      • Order Management
      • Edit Orders
      • Refund Items & Orders
      • Create & Manage Returns
      • Order Statuses
      • Open Carts
      • Test Orders
    • 👥Customers Guide
      • Customer Carts
      • Checkout Links
    • 🔃Subscriptions Guide
      • Subscription Settings
      • Managing Subscriptions
      • Account Updater
      • Decline Salvage
      • Subscription Statuses
    • 📞Support Guide
  • Features
    • 🛍️Offers Guide
      • Create and Manage Offers
      • Product Ranges
      • Coupons
      • Shareable Coupon Links
      • Marketing Attribution
    • 💳Payments Guide
      • 3DS2 Payments
      • PayPal
      • Apple Pay
      • Google Pay
      • Stripe APMs
      • Authorize & Capture Payments
      • Disputes Guide
      • Block Lists
      • Payment Failure Cascading
      • Transaction Response Codes
    • 🚚Fulfillment Guide
      • Fulfillment Statuses
      • Location-Based Routing
      • Advanced Settings
  • Apps
    • 3PL Central
    • Avalara AvaTax
    • Campaigns App
    • Delivery Tracking
    • Everflow
    • Meta Pixel
    • Gorgias
    • Klaviyo
    • MaxMind minFraud
    • Chargeback360
    • TaxJar
    • ShipStation
    • Shop Sync
  • Analytics
    • Dashboards
    • Orders Reports
    • Customers Reports
    • Disputes Reports
    • Gift Card Reports
    • Fulfillment Reports
    • Transactions Reports
    • Support Ticket Reports
    • Subscription Reports
    • Tax Reports
    • Partner Marketing Reports
Powered by GitBook
On this page
  • Set Up Meta Pixel
  • Meta Settings
  • How Meta Pixel App works
  • Use Meta Pixel with External Checkouts

Was this helpful?

  1. Apps

Meta Pixel

Connect your store to the Meta Conversions API for Server-Side tracking

PreviousEverflowNextGorgias

Last updated 6 months ago

Was this helpful?

The Meta Pixel App creates a server-to-server connection to post tracking and sales attribution metrics to the (Facebook) Meta Conversions API. Server-side API tracking is the method recommended by Meta to ensure the highest degree of accuracy in the data sent to the Meta Pixel.

Meta Pixel is an installable App. Enable it from the Apps menu on your store.

Set Up Meta Pixel

To connect your store to the Meta Conversions API, navigate to Apps > Meta Pixel > Settings.

Select Add Pixel

Input the following values obtained from your Meta Business Manager account:

  • Pixel ID (Dataset ID)

  • Access Token

Select Save.

You may optionally add additional Meta Pixels to your store.

Meta Settings

Once you have added one or more Meta Pixels, choose the Default Meta Pixel to be used in your store. Configure the following optional settings

  • Enable Delay Order Confirmation - add a 10 minute delay after purchase events, to ensure that orders are completed including any upsells before being posted to the Conversions API.

  • Enable Test Data - allow data to be posted to the Conversions API.

How Meta Pixel App works

  • fb_fbc (required) - value from Meta Pixel JS to capture the click.

  • fb_fbp (required) - value from Meta Pixel JS to capture the click.

  • fb_pixel_id (optional) - pass an alternative Pixel ID to specify a different Meta Pixel than the app's Default to be used in the Meta Conversions API post.

  • fb_event_source_url (optional) - pass the url the event happened on such as an external marketing campaign.

Use Meta Pixel with External Checkouts

  • fb_fbc (required)

  • fb_fbp (required)

The Meta Pixel app automatically adds your Meta Pixel JS to the storefront. Additionally, the app creates the following attribution fields in your store, which correspond to values required by Meta Conversions API to track events accurately:

fb_test_code (optional) - this field can be used to pass test events, but should only used by developers. Additional documentation - .

For additional documentation about Click IDs and related tracking parameters, see

When creating orders via externally-hosted marketing funnels and checkouts integrated to the or the , it's important to pass the required metadata on orders to ensure that the Meta Conversions API receives the proper attribution elements.

These represent browser cookie values generated by the Meta Pixel JS, installed on your externally-hosted site. Capturing these values and appending them to orders as , will post them to the Meta Conversions API on order events.

Test Orders
Meta
Meta documentation
Admin API
Campaign API
attribution metadata
metadata