CampaignProof beta

For PPC freelancers and small performance agencies

Prove your conversion tracking works before you pay for a single click.

CampaignProof records a real visit to your landing page, checks that GA4, Google Ads and Meta Pixel fire what they should when the lead form is submitted, and gives you a report a client can read in thirty seconds.

Install the extensionSee a sample report

Free during beta. No sign-up and no credit card.

Observed

The browser sent the expected request, and it matched what you configured.

Missing

You completed the journey, CampaignProof could see this kind of request, and it never came.

Unverified

The recording could not decide: the payload was unreadable, the journey was not finished, or it is sent server-side.

What it verifies

GA4 events

generate_lead, form_submit, sign_up, purchase or your own names, with the parameters you require.

Google Ads conversions

The conversion request for your conversion ID and label, kept apart from remarketing traffic.

Meta Pixel events

Lead, CompleteRegistration, Contact, Purchase and custom events, on the pixel you expect.

UTM parameters

Required campaign parameters, expected values, letter case and double-encoded links.

Double firing

The same conversion sent twice within seconds, flagged against the limit you set.

Lead form journey

You complete the real form; every signal is tied to the moment it fired.

How it works

  1. Step 1

    Install the extension

    Load it in Chrome. No account, no card.

  2. Step 2

    Set what should fire

    Type the events, or import a saved workflow.

  3. Step 3

    Record the journey

    Start, submit the lead form like a customer would, confirm, stop.

  4. Step 4

    Read the evidence

    Observed, missing or unverified, each with the request behind it.

Sample report

Generated by the real verification engine from demo requests for a fictional clinic, with fake tracking IDs.

Sample: Bright Smile Dental consultation form

Problems found

Some expected tracking is missing or failed a check.

Observed
3
Missing
1
Unverified
0
Failed checks
0

Results

Google Ads conversion AW-100000001/cpDemoLabel

Missing

Google Ads conversion AW-100000001/cpDemoLabel was not sent from the browser during a completed test journey. Only remarketing traffic for AW-100000001 was seen; that is not a conversion request.

  • This covers browser requests only. A server-side integration could still send it.
  • CampaignProof watches the known collection endpoints for Google Ads and first-party GA4 tagging on the approved site; a tag routed through another custom domain would not be seen.

GA4 event "generate_lead" on G-CPDEMO0001

Observed

GA4 event "generate_lead" on G-CPDEMO0001 was sent from the browser 1 time(s).

  • A browser request shows the GA4 tag sent the event; it does not show GA4 processed it or counted it in reports.

Meta Pixel event "Lead" on pixel 100000000000001

Observed

Meta Pixel event "Lead" on pixel 100000000000001 was sent from the browser 1 time(s).

  • A browser request shows the Pixel sent the event; it does not show Meta accepted, matched or attributed it.

Campaign (UTM) parameters on the landing URL

Observed

Landing URL carries utm_source=google, utm_medium=cpc, utm_campaign=implants_nov.

  • Checked on the URL the recording started on.

Journey timeline

  1. Page loaded

    https://brightsmile.example/consultation?utm_source=google&utm_medium=cpc&utm_campaign=implants_nov

  2. GA4 page_view · G-CPDEMO0001

    POST www.google-analytics.com/g/collect · unknown

  3. Meta Pixel PageView · 100000000000001

    GET www.facebook.com/tr/ · unknown

  4. Google Ads remarketing AW-100000001

    GET googleads.g.doubleclick.net/pagead/viewthroughconversion/100000001/ · unknown

  5. GA4 form_submit · G-CPDEMO0001

    POST www.google-analytics.com/g/collect · unknown

  6. GA4 generate_lead · G-CPDEMO0001

    POST www.google-analytics.com/g/collect · unknown

  7. Meta Pixel Lead · 100000000000001

    GET www.facebook.com/tr/ · unknown

What this report can and cannot show

  • CampaignProof sees requests the browser sends. It cannot see server-side events, platform processing or attribution.

What it cannot tell you

  • Whether Google Ads or Meta accepted, matched or attributed a conversion. A sent request is not a counted conversion.
  • Anything sent server to server, such as the Meta Conversions API or server-side GTM forwarding to platforms.
  • Whether your CRM received the lead.
  • Payloads the browser does not expose or that use a format it cannot read; those are reported as unverified, never as missing.

Privacy by design

  • Nothing is recorded until you press Start, and only in that tab, on the site you approve.
  • Only GA4, Google Ads and Meta Pixel requests are inspected. Cookies, headers, form values and page content are never read.
  • Emails, phone numbers, tokens and click IDs are removed from URLs and parameters before anything is stored.
  • Reports stay in your browser and your own dashboard. Nothing is shared publicly.