Whathead
  • Builder
  • MCP server
  • Transfer
  • Guardrails
  • Pricing
  • Blog
  • Docs
Log inSign up free
  1. Home
  2. Signal (private pilot)
Signal (private pilot)

Server-side tracking for every ad platform you buy on

Whathead Signal is server-side tracking for paid media. A first-party snippet or Google Tag Manager setup collects events, and Signal forwards them through each platform's server API: Meta Conversions API, TikTok Events API, Snapchat Conversions API, X Conversions API, LinkedIn Conversions API, GA4 Measurement Protocol and Google Ads conversion upload. It also routes ad-platform leads to Zoho CRM or Google Sheets. Signal is in private pilot, enabled per workspace on request.

Updated 18 Nov 2026
Ask to join the Signal pilotSee pricing
Destinations
7: Meta, TikTok, Snapchat, X, LinkedIn, GA4, Google Ads
Install
Direct snippet, GTM, or developer API
Consent
Consent Mode v2, custom CMP, or none
Lead sources
Meta, Snapchat, TikTok and LinkedIn lead forms
Availability
Private pilot, on request
On this page
Why move conversion tracking server-sideWhere Signal sends eventsWhat the tracker does and does not doLead routing and offline conversionsHow a pilot setup runsFAQRelated

Why move conversion tracking server-side

Browser pixels lose events to ad blockers, browser privacy limits and pages that close before the tag fires. Every platform now offers a server API to send the same events from your side, but each has its own payload, token, hashing rules and test tools. Running four of them by hand means four integrations to build and keep alive.

Signal gives you one event stream and one place to map it. You decide which events go to which platform, and Signal handles each API's format.

Where Signal sends events

DestinationAPI used
Meta (Facebook, Instagram)Conversions API, with dataset quality readback
TikTokEvents API v1.3
SnapchatConversions API v3, with validation diagnostics
XConversions API
LinkedInConversions API
GA4Measurement Protocol (global or EU endpoint)
Google AdsClick conversion upload

What the tracker does and does not do

The Signal SDK is explicit: it sends the events you call or that your GTM container defines. It does not scrape the page, attach form listeners, guess purchases or fingerprint devices.

  • Consent first: with no consent, nothing is tracked. Click IDs and hashed identity are sent only with marketing consent. Consent Mode v2 and custom CMPs are supported.
  • Hashing in the browser: email and phone passed to identify are SHA-256 hashed before they leave the page; fields that look like names, addresses or tokens are stripped from event properties.
  • Click IDs: fbclid, gclid, gbraid, wbraid, ttclid, ScCid and twclid are captured so the server event can be matched to the click.
  • Deduplication: each event carries an event ID, so platforms can drop the duplicate when the browser pixel also fires.
  • Reliability: events queue and retry; on the server, each delivery attempt is logged and failed ones can be retried.

Lead routing and offline conversions

Signal pulls leads from Meta, Snapchat, TikTok and LinkedIn lead forms by webhook or bulk read, and routes them to Zoho CRM or a Google Sheet. As the lead moves through stages (raw lead, qualified, sales opportunity, converted, unqualified), Signal sends that stage back to the ad platform as a conversion event, so campaigns can optimize toward qualified leads instead of form fills. Lead lists can also be uploaded as audiences.

How a pilot setup runs

  1. Add the site

    Register the domain, choose browser plus server, server only or browser only, and the consent mode.

  2. Install

    Paste the snippet, or let Signal plan the tags, triggers and variables in your GTM workspace.

  3. Connect destinations

    Link each pixel or dataset with an existing Whathead integration, OAuth or a server token.

  4. Map and test

    Map site events to each platform's event names, send test events, and watch the debugger and quality checks.

  5. Go live and monitor

    Watch delivery attempts and quality per destination, and retry failures.

Frequently asked questions

Is Signal available on the standard plans?

Not yet. Signal is in a private pilot and is switched on per workspace by the Whathead team. Contact us if you want to join.

Does Signal replace the Meta Pixel or TikTok Pixel?

It can run alongside them. With browser plus server collection, both send the same event with the same event ID and the platform deduplicates.

Is Reddit supported?

Not as a Conversions API destination today. The seven live destinations are Meta, TikTok, Snapchat, X, LinkedIn, GA4 and Google Ads.

How is this different from Meta Conversions API Gateway?

Conversions API Gateway is Meta's hosted option for sending events to Meta. Signal sends one event stream to seven destinations and adds lead routing and lead-stage feedback.

Can I manage Signal from Claude or ChatGPT?

Not yet. Signal is configured in the Whathead app. The Whathead MCP server covers campaigns, reporting and platform APIs.

Where are personal data and tokens handled?

Identifiers are hashed in the browser before sending, and platform tokens are stored server-side. See Security and data practices for details.

Related

  • Paid media tracking QA (blog)blog.whathead.com
  • Security and data practices
  • GA4 MCP
  • Meta Ads MCP
  • Ad anomaly detection
  • Meta to Snapchat transfer

Run it from one workspace

Every plan starts with a 14-day free trial. Only successful live work is metered.

Ask to join the Signal pilotCompare plans
Whathead© 2026 Whathead. Multi-platform ad operations and an Ads MCP server.
Product
PricingMCP serverMeta Ads MCPGoogle Ads MCPCross-platform transferAd anomaly detectionServer-side trackingGoogle Sheets add-onLooker Studio connector
Compare
Supermetrics alternativePipeboard alternativeRyze AI alternativeWhathead vs Meta’s official MCP
Resources
BlogDocsAboutSupportContact
Legal
Terms of ServicePrivacy PolicyRefundsSecurity & DataLog in