Skip to content

One integration per platform, done to that platform’s rules

How PixelCapi sends events to Meta, Google and TikTok

Three platforms, three different server APIs, three different sets of rules about how personal data must be formatted before it is sent. PixelCapi sends a browser copy and a server copy to each of them with one shared event ID, and applies that platform’s own hashing rules rather than a single generic recipe.

per platform

One integration each, done to that platform’s rules

Meta

Conversions API

The pixel fires in the browser and the Conversions API receives the same event from your server, both carrying one shared event ID so Meta can deduplicate them into a single conversion.

browser pixel Conversions API shared event_id

Google

GA4 Measurement Protocol · Google Ads tag

Events reach GA4 through the Measurement Protocol, and Google Ads through its own tag, with Consent Mode v2 respected in both basic and advanced modes. Enhanced Conversions is in development.

GA4 Measurement Protocol Google Ads tag Consent Mode v2

TikTok

Events API

The TikTok Events API receives the server copy. TikTok formats phone numbers and geo fields differently from Meta, and PixelCapi hashes to TikTok’s rules rather than reusing Meta’s.

browser pixel Events API TikTok hashing rules

verification

A green check that is allowed to fail

A verification button that always succeeds tells you nothing. PixelCapi reports per platform what it was actually able to confirm, and names what it could not.

Passed: Meta — credentials confirmed Cannot be determined from outside: Google — cannot authenticate without OAuth

Example verdicts in the format the Verify button uses.

TODO(owner: screenshot)

Platform settings with the Verify result for Meta, Google and TikTok.

consent

Both halves gated together

Browser and server

A denied choice stops the pixel and the server send. Gating only the browser half leaves the server half running, which is the failure this design avoids.

Consent Mode v2

Google Consent Mode v2 is supported in basic and advanced modes, so you can match the behaviour your consent tool already implements.

Recorded on the order

The consent decision is stored with the order, so a send triggered later by a webhook uses the choice the customer actually made.

documentation

Read the details

The reference pages for this, including the parts that are still being verified.

Questions people ask about this

Short answers. Anything we cannot confirm, we say so.

Do I need a separate add-on for each platform?

No. Everything is included at every tier, with no add-ons and no product limits. Tiers differ only by the number of sites.

Why does the Verify button say it cannot confirm my Google setup?

Because Google’s endpoint cannot authenticate credentials without OAuth. PixelCapi states what it can and cannot confirm for each platform rather than showing a green check that would pass regardless of whether your setup is correct.

Does the same event ID work across all three platforms?

Each platform gets its own browser and server pair sharing one event ID for that platform. That shared ID is what lets each platform recognise the two copies as a single conversion.

How is personal data handled per platform?

Personal data is SHA-256 hashed to each platform’s own rules, including multibyte and diacritic case folding and the phone and geo differences between Meta and TikTok. IP address, user agent and click IDs are sent raw because the platforms require them in that form. Access tokens are stored server-side only and are never logged.

What happens when a visitor denies consent?

Both halves stop. Consent gates the browser event and the server event together, Google Consent Mode v2 is supported in basic and advanced modes, and the consent decision is recorded on the order so a send triggered later by a webhook respects it.

Stop guessing. Start proving.

Check what your site is sending right now, or see what PixelCapi Pro costs.

Check your tracking — free See pricing