TrueTrackedTrueTracked
Destination
Meta+TrueTracked

Server-side conversion tracking for Meta Ads

Send every conversion back to Meta through the Conversions API, straight from your server. Enriched with hashed customer data and deduplicated against your browser pixel.

Once it is live, you can ask your Meta ad data questions in Claude or ChatGPT.

Get StartedRead the setup guide

What you get

Conversions that survive the browser

Ad blockers, iOS, and short cookie lifetimes stop browser pixels from firing. TrueTracked sends the same conversions from the server through the Meta Conversions API, so Meta receives them either way.

Thirteen identifiers on every event

Email, phone, name, city, state, zip, country, and an external ID are SHA-256 hashed before they reach Meta. Click IDs, IP, and user agent round out Event Match Quality.

No double counting

Every event carries an event ID that both the browser pixel and the server send. Purchases key on the order ID instead, so the checkout event and the server-side order event always reconcile.

First-party click ID restoration

On a verified custom domain, _fbc and _fbp are set as first-party cookies with a 90-day lifetime, rebuilt from fbclid when missing.

Events sent to the Meta Conversions API

These eight events map to Meta standard events out of the box. You can change any mapping, send one TrueTracked event to several Meta events, or point an event at a custom Meta event name.

Orders also send NewCustomerPurchase or ReturnCustomerPurchase alongside Purchase, so you can optimise for new customer acquisition. Fifteen standard events are available in the mapping editor, plus any custom events you define.

See the full event reference →
TrueTracked eventMeta event
page_viewedPageView
product_viewedViewContent
product_added_to_cartAddToCart
checkout_startedInitiateCheckout
payment_info_submittedAddPaymentInfo
search_submittedSearch
contact_info_submittedLead
checkout_completedPurchase

What is sent with every event

Thirteen customer identifiers travel with every conversion. The more of them your store collects, the higher your Event Match Quality in Meta.

Hashed with SHA-256

9 fields
  • Email
  • Phone
  • First name
  • Last name
  • City
  • State
  • Zip
  • Country
  • External ID

Sent unhashed

4 fields
  • Client IP
  • User agent
  • _fbp cookie
  • _fbc cookie

Meta requires these in the clear. Hashing them would break matching.

Hashing happens on our servers. On the browser cookie path, email and phone are hashed in the browser before they are stored, so plaintext never leaves the visitor's device.

How deduplication works

Meta deduplicates on event name plus event ID, and TrueTracked sends the same event ID from both sides. A conversion counted twice on your side still counts once in Meta.

Purchases key on the order ID instead of a generated one, so a sale can never land twice.

Browser pixel
Server
Meta
Meta

Set up Meta in four steps

  1. 1

    Connect your Meta account

    Sign in with Facebook Login for Business. TrueTracked reads the pixels you grant and creates a configuration for each one.

  2. 2

    Pick a pixel

    Choose a Business Manager, then the pixel. Or open Advanced setup to enter a Pixel ID and Conversions API token manually.

  3. 3

    Check the event mapping

    Eight events are mapped by default. Adjust them under Settings, TrueSignal, Configure events.

  4. 4

    Verify in Events Manager

    Add a Test Event Code, trigger a purchase, and confirm the processing method reads Server.

Full walkthrough: Meta Conversions API setup guide →

Meta integration FAQ

How the Conversions API integration behaves once it is live. Still unsure? Reach out and we will give you a straight answer.

Yes. Facebook CAPI, Meta CAPI, and the Meta Conversions API all describe the same thing: the server-side endpoint you send conversions to instead of relying only on the browser pixel. Meta renamed the company and the product in 2021 and the older names stayed in circulation. Whichever name you searched for, this is the integration.

Disconnect any other tool that loads the same pixel, yes. TrueTracked loads the Meta pixel itself and pairs every browser event with a server event that shares an event ID, which is how Meta counts the conversion once. Another tool firing the same pixel sends its own events with different IDs, and Meta cannot deduplicate those against ours. Removing that connection does not delete your pixel, its event history, or your campaign learning. You are disconnecting a sender, not the pixel.

Meta deduplicates on event name and event ID, and both the browser and server events carry the same ID. Purchases key on the order ID instead, so the checkout event and the server-side order event always reconcile.

Email, phone, first and last name, city, state, zip, country, and an external ID, all SHA-256 hashed. Client IP, user agent, and the _fbp and _fbc cookies are sent unhashed, as Meta requires.

Yes. Fifteen standard events and your own custom events are available in the mapping editor. One event can map to several Meta events, and each row can be switched off. The mapping applies to every Meta pixel in your workspace.

One on Free, TrueSignal 500, and TrueSignal 2K. Three on Standard 50K and Standard 100K.

Not to send conversions. A verified custom domain lets TrueTracked set _fbc and _fbp as first-party cookies with a 90-day lifetime, which improves match rates on returning visitors.

Related integrations

Other destinations

Google AdsTikTokTikTokMicrosoft AdsMicrosoft AdsChatGPT AdsChatGPT Ads

Sources that feed Meta

ShopifyShopifyWooCommerceWooCommerceWixWixStripeStripe

Connections

ShopifyMetaShopify to Meta
Get started

Track smarter. Grow faster.

Get clear insights into what drives your sales with TrueTracked.

Get StartedBook a Demo

14-day free trial · No credit card required