Q3 Meta demo launch — Launch Record 01

Read-only sample

Summary

Launch record

Server delivery proof — correlated destination evidence

Ready with warnings

Your customer pipeline reported acceptance for every required destination, but did not supply browser/server deduplication evidence for all of them.

Proof stops at: Browser/server deduplication

Next action

Configure event_id deduplication between the Meta browser Pixel and the CAPI event, have your pipeline report "deduplicated": true on its receipt, then run one new controlled conversion.

Fix before launch

https://trialflow.example/get-started?utm_source=meta&utm_medium=paid-social&utm_campaign=q3-trialScanned Jul 8, 2026 · 17:02 UTCQ3 Meta demo launch

Conversion signal chain →

Fix before launch

1 warning

Proof stops at: Browser/server deduplication
Browser/server deduplication — not proven. A browser Meta Pixel "Lead" event was observed directly, and your pipeline reported Meta CAPI acceptance for a "Lead" event with the same observed platform event ID. No receipt states these were deduplicated.
Configure event_id deduplication between the Meta browser Pixel and the CAPI event, have your pipeline report "deduplicated": true on its receipt, then run one new controlled conversion.
View evidence

Signal path

Browser conversion → server event → destination request → destination acceptance → browser/server deduplication.

Conversion signal chain

One controlled conversion, followed hop by hop. Each hop stands only on its own evidence.

Browser/server deduplication

Deduplication not provenNot proven

Browser/server deduplication — not proven. A browser Meta Pixel "Lead" event was observed directly, and your pipeline reported Meta CAPI acceptance for a "Lead" event with the same observed platform event ID. No receipt states these were deduplicated.

Fix this hop

Meta: No deduplication statement supplied

Run b7f3d2a1-4c5e-4f6a-9b8c-1d2e3f4a5b6cVerifiedStopping hop: Browser/server deduplicationExpires Jul 10, 2026 · 17:05 UTC

Browser conversion — observed directlyForm submitted and confirmed · 2 post-submit events

Controlled test conversion

Authorization: acknowledged by user

Classification: supported-lead-form · /api/lead

Submission: confirmed · https://trialflow.example/get-started/thank-you

Field handling: email → input[name=email]

Fields identified: email

Hidden attribution observed, not modified: utm_source (populated), utm_medium (populated), utm_campaign (populated)

Post-submit events: Meta Pixel Lead, GA4 generate_lead

Browser-visible network outcomes: POST trialflow.example → 200, GET www.facebook.com → 200

User-authorized controlled test conversion

This test submitted a user-authorized controlled test conversion. It does not prove CRM ingestion, server-side conversion delivery, lead qualification, or offline conversion feedback unless those systems are verified separately.

ObservedObserved directly

Form classified: supported-lead-form

The form maps to a low-risk lead request with one supported email field. single supported email field trial-request heading

ObservedObserved directly

Controlled test conversion confirmed by meaningful browser evidence

At least one visible success state, confirmation redirect, form-success callback, or conversion event plus meaningful form-state change was observed.

ObservedObserved directly

Visible success state observed

The page displayed a recognized success signal: thank-you message.

ObservedObserved directly

Confirmation redirect observed

The form flow reached a confirmation-style URL: https://trialflow.example/get-started/thank-you.

ObservedObserved directly

Conversion event accompanied a meaningful form-state change

Meta Pixel Lead fired and the form disappeared.

ObservedObserved directly

Conversion-ish browser event observed after submission

Meta Pixel Lead, GA4 generate_lead

ObservedObserved directly

Server verification — pipeline receipts1 receipt received

Receipts are your pipeline's own statements. Postclick verifies their identity against the observed browser event; it does not independently confirm them with the destination.

Verification run

Verify one controlled source handoff through HubSpot, or verify one controlled product analytics event and its campaign values in Mixpanel. Browser observation and aggregate provider activity never count as a destination receipt.

1Setup
2Receipt-kit handoff
3Controlled conversion
4Awaiting receipts
5Decision

VerifiedExpected event Lead

Proof stops at: Browser/server deduplication

Expires: 7/10/2026, 5:05:00 PM

Last refreshed: not yet refreshed in this session

Your customer pipeline reported acceptance for all required destinations, but did not supply explicit deduplication evidence for all of them.

Supporting evidence

Connected-provider reads, manual proof, configuration, and non-gating evidence that support the signal path.

Connected-provider and manual proofSupporting evidence from CRM, analytics, and pasted exports

Connected-provider evidence and manual proof support the chain above. They never replace browser/server signal path verification.

CRM record check — did the lead land with its source?

HubSpot contact carries campaign source

Needs validation

A form was detected on this page. Confirm that the resulting HubSpot contact record actually receives the UTM parameters and click ID observed on the landing page, not just the raw form fields.

expects: hs_analytics_source, utm_source, utm_medium, utm_campaign

HubSpot lead reaches a qualified CRM outcome

Needs validation

Confirm the test contact reaches an explicitly expected lifecycle stage, lead status, deal pipeline/stage, custom outcome field, or a closed-won deal. Contact or deal existence alone is not qualification.

expects: lifecyclestage, hs_lead_status, associated_deal, pipeline, dealstage

Configure qualification criteria and run all available proof from a saved report.

Sample HubSpot export used for this demo

Verified sample

Connected HubSpot verification is available in live scans; this demo uses a seeded verified proof state.

HubSpot source handoff

HubSpot source proof not started

No HubSpot source proof is attached to this Launch Record.

Start a HubSpot source handoff verification from this Launch Record.

Browser conversion

Verified

Controlled conversion was confirmed in the browser.

Server receipt

Missing

No matching HubSpot receipt has arrived.

Post a normalized receipt from your server pipeline.

Event ID match

Unconfirmed

Receipt identity has not matched the browser event.

Propagate the browser event ID into the server receipt.

Event name match

Unconfirmed

Receipt event name is not proven for this run.

Send the expected event name in the normalized receipt.

Campaign context

Unconfirmed

Campaign context is missing or not comparable in the receipt.

Include UTM source, medium, and campaign in the normalized receipt.

Click context

Unconfirmed

No comparable receipt digest is available.

Supply only a SHA-256 digest in the normalized receipt; never the raw click ID.

Destination acceptance

Unconfirmed

Receipt did not prove HubSpot acceptance.

Add explicit accepted/rejected destination evidence to the receipt.

Deduplication

Unconfirmed

Deduplication is not inferred from matching browser/server evidence.

Only claim deduplication when the receipt explicitly reports it.

HubSpot contact

Unconfirmed

The HubSpot source check has not run for this report.

Re-enter the controlled test identity and run the source handoff check.

HubSpot source fields

Unconfirmed

Configured source fields have not been checked yet.

Check or fix source fields on the HubSpot contact.

HubSpot campaign fields

Unconfirmed

Configured campaign fields have not been checked yet.

Map UTM fields into HubSpot before rerunning.

HubSpot click-ID fields

Unconfirmed

Click-ID fields are presence-only in this proof.

Configure click-ID fields if click continuity matters for this launch.

Analytics record check — connected reads

Meta Conversions API configured

Needs validation

Meta Pixel was observed in the browser. Browser-only pixels are degraded by ad blockers, ITP, and consent gates — confirm a server-side Conversions API path exists and is deduplicated against the browser pixel via event_id.

Verifiable via a connected Meta integration.

Google Enhanced Conversions / offline import mapped

Needs validation

A Google click ID or Google Ads/GA4 tracking was observed. Confirm Enhanced Conversions (hashed customer data) or an offline conversion import ties this click back to a closed-won or qualified-lead event in Google Ads.

Verifiable via a connected Google Ads integration.

Google Ads receives the intended offline conversion

Needs validation

Confirm the intended conversion action is enabled and documented upload diagnostics show recent successful receipt. Conversion-action configuration alone does not prove delivery.

Verifiable via a connected Google Ads integration.

Qualified-lead feedback loop to ad platforms

Needs validation

Capturing a lead is not the same as telling the ad platform which leads were actually qualified. Confirm a feedback loop (CRM stage change → ad platform conversion event or offline import) exists so campaigns can optimize toward pipeline, not just form fills.

Verifiable via a connected Google Ads integration.

GA4 key event configured and firing

Needs validation

GA4 was observed in the browser. Confirm the conversion you're paying for is configured as a GA4 key event and has fired recently — a page_view alone doesn't prove conversion measurement. Connect GA4 (read-only) to verify this from the property's configuration and recent data.

Verifiable via a connected Google Analytics 4 integration.

GA4 conversion data carries campaign context

Needs validation

Campaign parameters were observed on the landing URL. Confirm GA4's recent conversion data actually carries the matching session source/medium/campaign — attribution can be dropped by consent gates, redirects, or misconfigured tagging even when the tag fires. Connect GA4 (read-only) to check recent data.

Verifiable via a connected Google Analytics 4 integration.

Coverage summary

HubSpot record — lead landed with its source — Supported — connect the provider to check. Connect HubSpot and look up a test contact created through this landing page, or paste a redacted export.
HubSpot pipeline — qualified outcome — Supported — connect the provider to check. Supply expected lifecycle/status/pipeline/stage criteria and run HubSpot against a test contact.
Meta Conversions API delivery — Supported — connect the provider to check. Connect Meta to verify configuration, then run a controlled event and inspect Events Manager diagnostics for delivery/deduplication.
Google enhanced conversions — Supported — connect the provider to check. Connect Google Ads, select the expected action, then verify recent upload diagnostics or run a controlled event externally.
Google Ads offline conversion — Supported — connect the provider to check. Select the offline action and re-run after an external uploader sends a controlled event.
CRM to ad-platform feedback loop — Supported — connect the provider to check. Verify a qualified CRM outcome, the matching ad-platform action/rule, and direct upload/receipt diagnostics for that outcome.
GA4 key event — Supported — connect the provider to check. Connect GA4, name the expected event, and generate a test event if no recent row exists.
GA4 campaign context — Supported — connect the provider to check. Run a tagged test conversion, then re-run GA4 proof after processing completes.

Connected proof is read-only. Configuration, recent activity, and documented diagnostics are reported as separate claims. Pair-level browser/server deduplication and provider receipt gaps remain test-event or manual-evidence requirements.

Support map — how the surrounding systems line up

Ordered evidence chain. Every relationship is scored independently; green nodes never imply an end-to-end loop.

1. Campaign

Paid campaign parameters were present on the scanned URL.

Next link: Proven — Landing capture must preserve the paid-click context.

Proven

2. Landing/form

Attribution-style fields were visible on the landing form.

Next link: Proven — Run an authorized conversion test to prove this transition.

Proven

3. Browser conversion

A conversion outcome/event was observed during an explicit conversion-path check.

Next link: Unresolved — A CRM contact must carry the expected source/campaign/click-ID fields.

Proven

4. CRM source handoff

One sample contact does not prove every lead is attributed.

Next link: Unresolved — Contact existence or an associated deal alone does not prove qualification.

Not connected

5. Qualified outcome

A deal or amount alone does not prove qualification or collected revenue.

Next link: Unresolved — Current aggregate analytics reads cannot correlate one CRM outcome to one analytics event without a shared non-PII key.

Not connected

6. Analytics

Recent aggregate rows do not prove identity-level linkage to the CRM record.

Next link: Unresolved — Analytics activity and ad-platform configuration are separate facts.

Not connected

7. Ad platform configuration

Configured actions/rules do not prove event delivery.

Next link: Test event required — Configuration-only evidence never becomes delivery evidence.

Not connected

8. Ad platform delivery

Receipt evidence must come from a documented provider diagnostic or report.

Next link: Test event required — Requires verified CRM outcome mapping plus matching platform receipt diagnostics.

Test event required

9. Qualified-pipeline optimization

CRM qualification and ad receipt must refer to the intended qualified outcome; isolated green nodes are insufficient.

Test event required

End-to-end closed loop: not proven.

Landing page evidenceutm_source, utm_medium, utm_campaign present · 3 hidden attribution fields

Campaign context

utm_source=metautm_medium=paid-socialutm_campaign=q3-trial

Campaign parameters detected in URL

Found: utm_source=meta, utm_medium=paid-social, utm_campaign=q3-trial.

ObservedObserved directly

Page and CTA path

Call-to-action detected: "Start Free Trial"

A recognizable conversion CTA was found on the page.

ObservedObserved directly

Form / source handoff

hidden fields: utm_source, utm_medium, utm_campaign

Form carries attribution data in hidden fields

Hidden field(s) observed: utm_source, utm_medium, utm_campaign. This is a client-side handoff path from page context into the form submission.

ObservedObserved directly

Configuration and technical evidenceMeta Pixel, GA4 detected

Browser-visible tracking

detected: Meta Pixel, GA4

Tracking scripts detected: Meta Pixel, GA4

2 event call(s) observed firing: Meta Pixel PageView, GA4 page_view.

ObservedObserved directly

No duplicate tracking observed

Each analytics event fired once per destination during the scan window.

ObservedObserved directly

No PII leak observed

No plaintext personal data was observed reaching an ad platform or GA4 during the scan window.

ObservedObserved directly

Server-side conversion readiness

No server-side tagging endpoint visible

No first-party server-side collection endpoint was observed in browser traffic. This doesn't rule out CAPI or sGTM run entirely server-to-server — that path is invisible from the browser and requires internal confirmation.

Needs validationNot proven

Paid-platform feedback loop

Meta Conversions API configured

Needs validationNot proven

Google Enhanced Conversions / offline import mapped

Needs validationNot proven

Google Ads receives the intended offline conversion

Confirm the intended conversion action is enabled and documented upload diagnostics show recent successful receipt. Conversion-action configuration alone does not prove delivery.

Needs validationNot proven

Qualified-lead feedback loop to ad platforms

Needs validationNot proven

Cannot verify (8)What no outside tool can prove about this setup — and what would prove it.

HubSpot contact carries campaign source