How to Preserve Campaign Context and Session Evidence for Ad Quality Audits

When a paid click arrives, the first seconds decide whether you can later prove the traffic was invalid. Capture the campaign name, ad set, creative, placement, and click identifier (such as fbclid or gclid) immediately on the landing page. At the same time, start recording behavioral signals — scroll activity, mouse movement, form interaction timing, and viewport changes — so each session carries a complete, tamper-resistant record. Keep this data intact even if you pause the campaign, change targeting, or swap creatives; the evidence must remain linked to the original click so Google or Meta reviewers can trace it back to the exact impression that was billed.

Why Preserving Campaign Context Matters for Ad Quality

Ad platforms bill on clicks and impressions, not on lead quality. A campaign can show a healthy cost per lead while the sales team receives disconnected numbers, copied messages, or enquiries that never progress. Without preserved context, you cannot distinguish a weak offer from automated fraud. The source pack notes that Meta campaigns reach people across Facebook, Instagram, and partner inventory at high volume, which also means accidental interactions, low-intent traffic, and deliberately fraudulent submissions can enter the funnel. Treating every unresponsive contact as fraud risks excluding a valuable audience, so a structured audit that compares ad-platform data, website sessions, and CRM outcomes is the necessary first step.

Core Components of Session Evidence

Session evidence has two layers: attribution data that ties the visit to a paid click, and behavioral data that shows whether a human performed the actions. Attribution data includes the campaign hierarchy (campaign, ad set, creative), placement, device, timestamp, and the click identifier. Behavioral data includes scroll depth and pattern, pointer movement (linear vs. natural curves), click and typing speed, form field corrections, time on page, and navigation flow. The source pack describes 110+ independent checks across browser, hardware, network, and behavior signals, each kept as evidence rather than a verdict, then cross-checked by an AI model that reaches 99% confidence when the full pattern supports it. No single anomaly proves fraud; a consistent cluster does.

Step-by-Step Process to Preserve Attribution and Session Data

1. Capture click identifiers on landing. Read fbclid, gclid, msclkid, or other platform parameters from the URL before any redirect or consent wall strips them. Write them into a first-party cookie or local storage with a short TTL so they survive page navigations.
2. Attach attribution to every event. When you fire conversion pixels, form submissions, or custom events, include the stored click ID, campaign name, ad set, creative, and placement. This keeps the evidence chain intact even if the user moves across subdomains.
3. Record behavioral signals client-side. Deploy a lightweight script that logs scroll events, mouse coordinates, click timestamps, form focus/blur, and viewport visibility changes. Send these as a session payload tied to the same click ID.
4. Store session replays or structured logs. Keep a tamper-resistant copy — either a full session recording or a signal-by-signal JSON log — that can be exported without manual translation. The source pack emphasizes reports built in the format platform teams use to review invalid traffic claims, including click IDs, campaign details, timestamps, session recordings, and signal-by-signal reasoning.
5. Preserve evidence after campaign changes. Do not delete or overwrite session data when you pause a campaign, adjust budgets, or swap creatives. The evidence must remain queryable by the original click ID for the duration of the platform's refund window (typically 60–90 days).
6. Correlate with CRM outcomes. Match each click ID to the downstream lead record: contactability, demo booked, qualified opportunity, or repeat engagement. A high reported lead count paired with no connected calls or qualified opportunities is a strong signal to investigate.

Technical Implementation: Client-Side vs Server-Side Collection

Server-side logs (IP, user-agent, headers) catch basic scrapers but miss advanced botnets that rotate residential proxies and mimic browser fingerprints. Client-side audits analyze the visitor's browser environment — canvas rendering, WebGL, font enumeration, pointer dynamics, scrollbar metrics, iframe context — and can detect automation tools that patch or hide APIs. The source pack explains that automation tools often break when checked from another angle, such as a clean context iframe test. A practical setup uses both: server-side for fast filtering and click-ID capture, client-side for the behavioral evidence that platforms require for refund claims. BotRefund's approach combines 110+ signals across browser, network, device, and behavior, then weighs the complete pattern instead of trusting a raw rule.

Common Mistakes That Break the Evidence Chain

• Stripping click IDs at consent walls. Many cookie banners reload the page or redirect, dropping fbclid/gclid before your script reads them. Capture parameters before any consent UI renders.
• Relying only on platform auto-credits. Google and Meta automated systems catch some invalid activity, but the source pack notes they catch less than advertisers think. Manual claims with structured evidence recover the rest.
• Deleting session data when pausing campaigns. The evidence must survive campaign pauses. Export or archive before making structural changes.
• Using security logs instead of marketing-ready reports. Platform reviewers need click IDs, campaign hierarchy, timestamps, and signal reasoning in a readable format — not raw WAF logs that require manual translation.
• Treating every bad lead as fraud. Weak offers attract real people who aren't ready to buy. Compare ad-platform data, website sessions, and CRM outcomes before changing targeting or filing a refund request.

How to Verify Your Evidence Is Refund-Ready

Before filing a claim, run a verification checklist: (1) Can you query any click ID from the last 90 days and retrieve the full session payload — attribution, behavioral signals, and CRM outcome? (2) Does the export include campaign, ad set, creative, placement, device, timestamp, and click identifier in columns a platform reviewer expects? (3) Are behavioral signals presented as independent facts with cross-checked context, not a single "bot score"? (4) Does the report show signal-by-signal reasoning that a human reviewer can follow? The source pack states that BotRefund formats data in the structure Google and Meta teams use, and that 83% of clients across 2,500+ audits recover funds because the evidence meets reviewer expectations. If your export fails any of these checks, fix the collection or formatting gap before submitting.

Limitations and When This Advice Does Not Apply

• Organic or direct traffic. This process preserves context for paid clicks with platform identifiers. It does not create attribution for sessions without a click ID.
• Platforms without click identifiers. Some networks (e.g., certain programmatic DSPs) do not pass a standard click ID. You need a custom parameter strategy agreed with the vendor.
• Privacy regulations that restrict client-side tracking. In jurisdictions requiring prior consent for non-essential scripts, you may only collect behavioral signals after consent. Capture the click ID before the consent prompt, but delay behavioral recording until consent is granted.
• Single-page apps with hard navigations. If your SPA does full page reloads between steps, ensure the click ID persists in storage across reloads.
• Evidence older than the platform's refund window. Google and Meta typically review invalid activity within 60–90 days. Data older than that cannot support a new claim.

Key Terms and Definitions

• Click ID (fbclid, gclid, msclkid): A unique parameter appended by the ad platform to the landing-page URL, linking the visit to a specific impression and click.
• Attribution chain: The unbroken link from impression → click → landing page → conversion event → CRM outcome, all tied to the same click ID.
• Behavioral signals: Observable browser actions — scroll, pointer movement, typing rhythm, form corrections, viewport changes — that distinguish human interaction from automation.
• Pixel poisoning: When invalid traffic fires conversion pixels, corrupting the platform's optimization model so it bids more aggressively on similar low-quality traffic.
• Refund-ready report: A structured export containing click IDs, campaign hierarchy, timestamps, session recordings or signal logs, and signal-by-signal reasoning formatted for platform reviewer consumption.
• Cross-checked context: The practice of verifying that multiple independent signals (browser, network, device, behavior) tell the same story before labeling a session invalid.

Fact	Detail	Source
Signals analyzed per session	110+ independent browser, hardware, network, and behavior checks	S2
Bot detection confidence	99% when the full pattern supports it	S2
Client refund recovery rate	83% of 2,500+ audited brands recover funds from Google and Meta	S2
Report components	Click IDs, campaign details, timestamps, session recordings, signal-by-signal reasoning	S2
Report format	Structured for Google and Meta reviewer consumption	S2
First investigation step	Preserve attribution before changing the campaign (campaign, ad set, creative, placement, click identifier)	S1
Client-side tracking purpose	Provides logs needed to claim refunds; protects Meta Pixel from poisoning	S3
Evidence portability	Must associate session with campaign, click ID, placement, timestamp; preserve after campaign pause	S7
Case study result	FinTrust recovered $140,000 (14% of ad spend) and increased conversion rate 18%	S8

FAQ

What is the minimum data I must capture on every paid landing page?

At minimum: the click ID (fbclid, gclid, or equivalent), campaign name, ad set name, creative ID, placement, device type, and timestamp. Store these in first-party storage before any redirect or consent wall can strip them.

How long should I keep session evidence?

Keep it for at least the platform's refund review window — typically 60 to 90 days from the click. If you have an open claim, retain evidence until the claim is resolved.

Can I use server-side logs alone for a refund claim?

Server-side logs help, but platforms require behavioral evidence (scroll, pointer, timing) that only client-side collection captures. The source pack notes server-side audits struggle to detect advanced botnets that mimic headers and rotate residential IPs.

What if the user rejects analytics cookies?

Capture the click ID before the consent prompt (it's in the URL, not a cookie). Delay behavioral recording until consent is granted. You still preserve attribution; you just have a behavioral gap for non-consenting users.

How do I know if my evidence format is acceptable to Google or Meta?

Check whether your export includes: click ID, full campaign hierarchy, placement, timestamp, device, session recording or structured signal log, and a plain-language explanation of each signal's finding. The source pack states BotRefund builds reports in the format platform teams use to review invalid traffic claims.

Does preserving context hurt page speed?

A lightweight client-side script (under 10 KB gzipped) that captures click IDs on load and streams behavioral events asynchronously adds negligible latency. The source pack's detection script runs 110+ checks without blocking page interaction.

When should I involve a specialist service instead of building this myself?

If you spend over $10,000/month on paid social or search, have had refund claims denied, or lack engineering bandwidth to maintain 100+ signal checks and platform-specific report formatting, a specialist service that negotiates with Google and Meta on your behalf can be more efficient. The source pack notes BotRefund has worked through 2,500+ audits and knows how to present evidence to platform reviewers.

Further reading and comparison sources

These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.

• Persist Campaign Data On The Landing Page | Simo Ahava's blog
• How to preserve the context/session of a conversation with the api?
• Evidence Preservation: Screenshots, URLs, Metadata, and Timelines

Learn more

Visit the website for more information.