---
title: PlainRouter Signals — Recover and measure first-party conversion signal
description: Collect consent-aware first-party conversion events, deliver eligible events to Meta, and measure delivery quality.
canonical: https://plainrouter.com/product/signals
last_updated: 2026-08-26
---

# Recover the conversion signal your campaigns are missing

Collect events from a first-party domain, apply consent and identity rules before delivery, pair browser and server events, and measure what actually reaches Meta. Better feedback helps your team and the platform make better spending decisions.

[Join design partners](/register)

## Sitemap

See the full [sitemap](/sitemap.md) for all pages.

## You cannot optimize from conversions you cannot see

Browser loss, fragmented integrations, weak identity, and consent mistakes all degrade the feedback loop between your website, Meta, and the people managing spend. Signals creates one measurable path for collecting eligible first-party events and understanding where quality is gained or lost.

- **Collection — First-party:** Receive browser and server events through a collection hostname controlled by your business.
- **Consent — Enforced:** Apply capture-time consent, identity, and downstream-delivery rules to each event.
- **Delivery — Measured:** Track event flow, Meta delivery, match quality, and reconciliation gaps.

## How Signals works

1. **Create a collection domain.** Point a customer-owned CNAME such as collect.example.com to PlainRouter and verify the ingestion path over HTTPS.
2. **Receive browser and server events.** Use the `signalq` browser queue or server ingestion to send events through the same first-party Signal.
3. **Apply consent and identity rules.** Classify every event from its capture-time inputs before storing identity or making it eligible for a downstream destination.
4. **Deliver eligible events to Meta.** Pair browser and Conversions API delivery with the same event ID so Meta can deduplicate the two observations.
5. **Measure signal quality.** Monitor event activity, delivery outcomes, match quality, and reconciliation between gateway-verified and Meta-reported counts.

## What changes for your team

- **Recover more attributable conversions:** A server-side path can preserve eligible conversion observations that would otherwise disappear at the browser boundary.
- **Give Meta clearer feedback:** Paired, deduplicated events and stronger permitted identity inputs improve the evidence available for reporting and optimization.
- **Find measurement leaks sooner:** Health diagnostics expose missing activity, delivery failures, match-quality drops, stale measurements, and reconciliation gaps.
- **Keep consent inside the data path:** Consent is not a banner bolted onto delivery. Each event is evaluated before identity persistence and destination eligibility.

## Signal quality is measured, not assumed

A green request log is not enough. Signals keeps separate evidence for what the gateway received, what was eligible for delivery, what Meta accepted, and where the counts still differ.

- A customer-controlled collection domain keeps the browser request on a first-party hostname.
- Browser and server observations share an event ID so Meta can deduplicate them.
- Consent decisions govern identity persistence and downstream delivery at capture time.
- Delivery outcomes and event match quality are recorded rather than inferred from a successful queue job.
- Reconciliation compares gateway-verified events with Meta-reported counts and surfaces unexplained gaps.

## Signals FAQ

### Does Signals replace my existing Meta Pixel and CAPI setup?

When a Meta destination is connected, the PlainRouter snippet initializes the selected public Pixel and pairs its browser event with CAPI. Separate duplicate Pixel or CAPI integrations for that dataset should be removed.

### How does Signals handle consent?

Every event is classified from its capture-time consent inputs. Those decisions govern terminal storage, identity persistence, attribution, and whether the event may reach an advertising destination.

### Can I see whether events reached Meta?

Yes. Signals records delivery outcomes, recent event activity, match-quality snapshots, diagnostics, and reconciliation measurements for an active Meta destination.

### Does better signal guarantee a lower CPA?

No. Signals improves and measures the feedback available to Meta and your team, but campaign results still depend on the offer, creative, audience, budget, and market.

## Bring us the conversion your current stack keeps losing

We are working with design partners to trace real measurement gaps from browser capture through Meta delivery and turn that evidence into a stronger campaign feedback loop.

[Join design partners](/register)