TrueTrackedTrueTracked

Meta (CAPI) Setup

Connect your Meta Pixel to TrueSignal to send server-side conversion events via the Meta Conversions API (CAPI). This improves event match quality, provides more reliable data, and helps overcome browser-side tracking limitations.

Prerequisites:

  • A Meta Business account with an active Pixel
  • Your Pixel ID (found in Meta Events Manager)
  • A Conversions API Access Token (generated in Events Manager > Settings)
  • TrueTracked pixel installed on your site

Step 1: Get Your Meta Pixel ID

  1. Go to Meta Events Manager at business.facebook.com/events_manager
  2. Select your Pixel from the left sidebar
  3. Your Pixel ID is the number shown under the pixel name (e.g., 123456789012345)

Step 2: Generate a Conversions API Access Token

  1. In Events Manager, click on your Pixel
  2. Go to Settings
  3. Scroll to the Conversions API section
  4. Under "Set up manually", click Generate access token
  5. Copy the token, you'll need it in the next step

Important: Store your access token securely. It provides write access to your pixel data. TrueTracked encrypts and stores this token on our servers. It is never exposed to your frontend.

Step 3: Connect in TrueTracked

  1. Go to Settings > TrueSignal in your TrueTracked dashboard
  2. Click Connect on the Meta card
  3. Enter your Pixel ID
  4. Enter your Conversions API Access Token
  5. Optionally enter a Test Event Code to verify events in Events Manager before going live
  6. Optionally give the connection a Name (useful if you have multiple pixels)
  7. Click Connect

Step 4: Verify Events

  1. If you entered a Test Event Code, go to Events Manager > Test Events to see incoming server events in real-time
  2. Trigger a test purchase on your site
  3. Check that the event appears with Server as the processing method
  4. Once verified, you can remove the Test Event Code and toggle off Test Mode

Events Sent

Out of the box, TrueSignal sends these events to Meta. Each TrueTracked event becomes the Meta event shown on the right:

TrueTracked eventMeta event
page_viewedPageView
product_viewedViewContent
product_added_to_cartAddToCart
checkout_startedInitiateCheckout
payment_info_submittedAddPaymentInfo
search_submittedSearch
contact_info_submittedLead
checkout_completedPurchase

Purchases also send NewCustomerPurchase or ReturnCustomerPurchase alongside the standard Purchase event, so you can optimise for new-customer acquisition in Ads Manager.

Each event includes enriched user data (hashed email, phone, IP address, user agent, click ID) to maximize Meta's Event Match Quality score.

Event Mapping

The table above is the default. You can change it under Settings → TrueSignal → your Meta pixel → Configure events.

  • Change a target: pick a different Meta event for any TrueTracked event.
  • Send one event as several: add another row with the same TrueTracked event on the left. For example product_viewed can fire both ViewContent and your own ProductView.
  • Turn one off: use the Active toggle to stop sending an event without deleting the row.
  • Map a custom event: any event you defined under Settings → Events appears in the left dropdown. Choose Custom event name on the right to type the name Meta should receive. For conversion data a custom event sends value and currency, and any customer details you pass are hashed and sent for matching.

Two things worth knowing. Your mapping controls both the browser pixel and the Conversions API, so the two always send the same events and Meta can deduplicate them correctly. And it applies to every Meta pixel connected to this store, not just the one you are editing.

Not sure which TrueTracked events you have? See the Events Reference, or the Custom Events guide to define your own.

Troubleshooting

  • Events not appearing in Events Manager: Check that your Pixel ID and Access Token are correct. Enable Test Mode and use a Test Event Code to debug.
  • Low Event Match Quality: Ensure your TrueTracked pixel is properly installed. The more user data captured (email at checkout, click IDs from ad clicks), the better the match quality.
  • Duplicate events: If you're also sending CAPI events through another integration, you may see duplicates. Use TrueSignal as your sole server-side sender for each pixel to avoid this.
← TrueSignal OverviewGoogle Ads Setup →