Skip to main content
Signals is PlainRouter’s first-party conversion measurement layer. It receives website events through a managed collection subdomain or a same-origin forwarding route, records what happened, and can deliver consented events to a connected Meta dataset.

The short version

Your website sends one event to PlainRouter. PlainRouter records it, adds trusted request context at the edge, and routes eligible events to the destinations you connect.

​
How data moves

1

Your server or browser records an event

Your server can use the Conversion API. The optional Signals pixel can send browser events such as purchases, leads, checkouts, and custom events.
2

Your serving path receives it

Requests use a managed hostname such as collect.example.com or a generated same-origin forwarding route. PlainRouter validates the authorized Signal and website origin before accepting the event.
3

PlainRouter stores the event

PlainRouter records the canonical event, consent state, delivery state, and the trusted network context added by the collection edge.
4

Eligible events reach Meta

When you connect a Meta dataset and grant advertising consent, PlainRouter sends the server event through Conversions API. The managed browser Pixel sends a paired copy with the same event ID for deduplication.
5

Stored measurements become health evidence

The Signals dashboard combines the event ledger, delivery ledger, stored Event Match Quality snapshots, and daily reconciliation reports. It does not make a live Meta Marketing API call when the page loads.

​
What Signals measures

Signals health and reconciliation are account- or dataset-level measurements. They do not provide campaign, ad set, ad, spend, budget, learning-phase, or target-level CPA state.
Signals applies consent before browser measurement or advertising delivery: Connect your consent-management platform by calling signalq("consent", input) with the structured permission state whenever the visitor’s choice changes. See Track events and consent for examples. Server-side POST /events requests must include a consent_basis of consent or legitimate_interest. Requests using consent must include granted downstream advertising state. PlainRouter stores the normalized consent decision with the event and allows Meta delivery only for observed, joined, attributed events with consent.

​
Browser and server deduplication

When Meta is connected, one signalq("track", ...) call can produce both a managed browser Pixel event and a server-side Conversions API event. PlainRouter assigns the same UUID to both copies so Meta can deduplicate them. Do not keep a separate Pixel or CAPI integration sending the same events to the same dataset after you validate the managed setup. Duplicate integrations can inflate reporting.

​
Setup path

Configure DNS

Connect a first-party collection hostname.

Install the pixel

Add optional, consent-aware browser measurement.

Verify ingestion

Complete activation through the API or MCP.

Configure serving

Install the generated block for your hosting stack.

Track events

Add consent, identity, and conversion events.

Connect Meta

Select the destination ad account and dataset.