--- title: 'Meta Conversion Tracking and Verified Revenue' description: 'Count arrivals, verify Stripe Checkout revenue and inspect Meta Pixel and Conversions API delivery, with first-party collection and consent controls.' canonical: 'https://plainrouter.com/product/signals' last_updated: '2026-10-03' --- # Count arrivals. Verify revenue. Check Meta delivery. Count identity-free arrivals on your site, confirm Stripe Checkout revenue and connect consented browser and backend conversions. Meta Pixel and Conversions API share event IDs for paired events. See collection and delivery outcomes separately from revenue and Meta attribution, so your team can investigate the numbers with clear evidence. ## Less tracking guesswork. See the journey from conversion to Meta. ### First-party collection Own your website collection path. Choose a managed collection hostname or same-origin forwarding route. Count one identity-free arrival per page load, with bounded page, source, campaign and device context, without visitor cookies. ![Illustration of own-domain page-load collection and arrival counting without visitor cookies.](https://cms.plainrouter.com/_emdash/api/media/file/01M4223BMEP67THHVG6RHHR7RV.png?v=367bf6779f9cc8df768b6b38067891a4997df32529d9c43e84a9fa17b2c2264f) [Understand fbclid, fbp and fbc](/library/fbp-fbc) - Managed hostname or same-origin route - Identity-free arrival counts - Bounded source and campaign context ### Browser & server events Bring both sides of the sale together. Connect consented browser events and backend conversions in one workspace. Add Stripe Checkout settlement and supported refunds to compare recorded revenue with Meta reports; keep each currency separate. ![Illustration of consented browser events and backend-confirmed conversions in one workspace.](https://cms.plainrouter.com/_emdash/api/media/file/01M4223CMRJ6G9AQBEMMMNEC3J.png?v=50c7f3b39ede465d782904b839caa17ec36e7aef77d332b0584a2f5f8803807e) [Understand Meta Conversions API](/library/meta-conversions-api) - Consented browser events - Backend conversion events - Stripe-confirmed Checkout revenue ### Consent & identity Respect the choices visitors make. Connect your existing consent platform, a supported external consent signal or the configured fallback card. Identity and browser conversion events require all three advertising permissions; arrival counting remains separate. ![Illustration of the three advertising permissions required before conversion delivery.](https://cms.plainrouter.com/_emdash/api/media/file/01M4223DDQRGCF4CE17Y0T09ZP.png?v=3252617a7ff9d94e5df4f8f22fda7104d3e0485804340fe881d18fbcfccab226) - Capture-time consent - Consent-aware identity storage - Checks before ad delivery ### Pixel & CAPI pairing Help Meta count each conversion once. Send matching event names and IDs through [Pixel](/library/meta-pixel) and Conversions API so Meta can recognize [browser and server copies](/library/conversions-api-vs-meta-pixel) of the same conversion. ![Illustration of Pixel and Conversions API records sharing a Purchase event name and event ID.](https://cms.plainrouter.com/_emdash/api/media/file/01M4223E7VWHP06NT7S6F8C5F7.png?v=9ad8f5983a8964afa0d41705dc88bdfc53ee4ab974af8f0df5b551c4e44eac87) [Check Meta event deduplication](/library/meta-event-id-deduplication) - Shared event IDs - Coordinated Pixel and CAPI - Matching event names ### Delivery evidence Know what actually reached Meta. Inspect collection, eligibility, pending delivery, Meta acceptance and failures separately. Acceptance confirms receipt, not ad attribution; Stripe revenue records are a separate measurement. ![Illustration of collection and delivery stages ending in receipt rather than ad-attribution proof.](https://cms.plainrouter.com/_emdash/api/media/file/01M4223F1WJ0301MY62WB0K6KH.png?v=981cc8e035d9caa439ba277389f6344328905fe1068cdfbe4c7ca8d19fb60ac7) [Troubleshoot missing Meta events](/library/meta-capi-missing-duplicate-events) - Events cleared for delivery - Meta acceptance and failures - Delivery history ### Signal diagnostics Find the gaps behind the numbers. Compare stored arrival counts, settled revenue and Meta-reported measurements without treating them as interchangeable. Use freshness, delivery, match-quality and reconciliation checks to investigate concrete gaps. ![Illustration of stored collection, delivery and matching diagnostics available for inspection.](https://cms.plainrouter.com/_emdash/api/media/file/01M4223G0266WBQY97WVJ7P107.png?v=1cfefb2699c95f2626a6a0556ff44eecdf8f78b896e16bf83d6cbffddb22f8b0) [Diagnose low Event Match Quality](/library/meta-event-match-quality) - Recent event activity - Event match quality - Reconciliation warnings ## How Signals works ### Verify a collection domain Choose a managed hostname or supported same-origin route, then verify HTTPS forwarding and a real arrival. ### Connect your consent choices Pass the visitor consent state before browser tracking. Include the required consent information with server events. ### Send browser and server events Send consented browser events and backend conversions; optionally connect Stripe Checkout to record settled revenue. ### Coordinate eligible Meta delivery Pair browser Pixel and server Conversions API events with the same event name and event ID. ### Measure signal quality Review arrivals, revenue by currency, delivery outcomes, match quality and reconciliation as separate measurements. ## Signals FAQ ### Does Signals replace my existing Meta Pixel and CAPI setup? For the events you move to Signals, the managed snippet pairs Meta Pixel and Conversions API delivery. Validate the new setup, then remove other integrations sending those same events to the same dataset. ### How does Signals handle consent? The snippet counts an identity-free arrival before consent. Visitor identity and browser conversion events wait for all three advertising permissions; server events have their own consent and delivery checks. Withdrawal changes what remains eligible. ### Can I see whether events reached Meta? Yes. Signals shows destination acceptance, failures, and pending delivery. Event Match Quality and reconciliation are separate stored measurements; acceptance does not prove ad attribution. ### Does better signal guarantee a lower CPA? No. Signals improves and measures the feedback available to Meta and your team. Results still depend on the offer, creative, audience, budget, and market. ### Does Signals count visits before consent? The snippet records one identity-free arrival per document load without visitor cookies. It retains bounded page, source, campaign and device context, not visitor identity. These are arrival counts, not unique visitors or proof of ad attribution. ### Can Signals verify Stripe revenue? Yes. Connect Stripe to record paid Checkout settlement and supported refunds, grouped by currency. A checkout redirect or an unpaid Session is not confirmed revenue. Revenue records do not prove Meta delivery, ad attribution or incrementality. ### Can I use my existing consent banner? Yes. Use the documented consent adapter or a supported external consent signal. The configured fallback card is a separate option. Verify accept, partial consent and withdrawal; a first-party route does not remove consent requirements. [Read the setup guide](https://plainrouter.com/docs/signals/overview) ## Products [Overview](/product) · [Signals](/product/signals) · [Actions](/product/actions) · [Launch](/product/launch) ## Get started [Start for free](/register) or [view pricing](/pricing).