Skip to content
Apply now
Ad Pay Protection

Where your ad data goes, and how your money comes back.

How pixel data moves from your site, through Dash.fi on AWS and Google Cloud, into the ad platforms, and back out as a monthly audit report and recovery filings. Built for security reviews and customer technical questions.

Book a demo See the data flow
DASH.FI — AD AUDIT

Connection Matrix

Google

$84,200

Meta

$46,800

More soon

—

Audit Log

  • Ingesting ad spend feeds…Google
  • Cross-referencing bid history…Meta
  • Running invalid-traffic audit…Google
  • Flagging billing overcharges…Meta
  • Generating recovery package…
32 recoverable charges found$4,820

At a glance

AWS + Google Cloud
Hosted in the United States
IAB + MRC
Audited to industry standards
Append-only
Evidence kept for every flag
90–120 days
Typical platform review window
End-to-end data flow

From a page view to a recovered dollar.

Every signal is checked, scored, and packaged with its evidence — then filed for recovery and reported back for independent verification.

  1. 01 Client website

    Visitor lands on a protected page

    The Dash.fi pixel fires asynchronously and captures behavioral, technical, attribution, and network signals.

  2. 02 Dash.fi pixel endpoint

    Data intake on AWS and Google Cloud (United States)

    Signals are tidied up and checked for anything that looks off. We do not collect emails or phone numbers, and we do not track people across sites.

  3. 03 Audit engine

    How the audit works

    Each visit runs through three checks before anything is filed.

    1. Step A

      Signal scoring

      Each visit is checked for signs of contractual violations.

    2. Step B

      Standards check

      Checked against recognized industry standards (IAB and MRC).

    3. Step C

      Evidence and estimate

      Flagged clicks are packaged with their evidence and an estimated recoverable amount.

    Output flagged events with supporting evidence and an identified recoverable amount (LDA).

The flow forks here

  • 04A Exclusion API push

    Real-time suppression

    Non-compliant profiles go into a Custom Audience that Meta Ads excludes, and matching exclusions are applied in Google Ads. We also send conversion-value signals to both, so their algorithms learn which lookalikes to skip.

  • 04B Monthly audit filing

    Filed on a monthly cadence

    Primary: findings filed with the platform, with a review window. Backstop: Mastercard network recovery via the Dash.fi card.

  1. 05 Reporting and delivery

    Monthly Forensic Audit Report

    The client receives the report, a walkthrough is scheduled, and the audit log is available for independent verification.

  2. 06 Client

    Independent verification

    Credits visible in ad account billing. Exclusion audience visible in Ads Manager. Audit log reviewable.

Dash.fi infrastructure

Pixel endpoint, processing pipeline, and audit log storage. Hosted on AWS and Google Cloud, in the United States.

Audit engine

Each visit is checked against recognized industry standards (IAB and MRC), with the evidence kept for every flag.

Output and recovery

Where the value lands: exclusions live on the platform, recovered credits paid to the client.

Data classification

What we collect, how it’s handled, where it’s stored.

The data at each stage, and the controls around it — for security and privacy reviews.

Pixel signals collected

What the visitor does on the page (scroll depth, clicks, time on page, tab focus), basic device and browser details, where the click came from (UTM tags, Google and Meta click IDs, referrer), and network details (the full IP address, checked against known bad actors, plus a session ID kept in the browser).

Audit processing

Each visit is checked against recognized industry standards (IAB and MRC). The output is a list of flagged events with the evidence behind each, plus an estimate of the recoverable spend (the Legally Defensible Amount).

Exclusion push and filing

Non-compliant profiles go into a Meta Ads Custom Audience the campaigns exclude, and matching exclusions are applied in Google Ads, in near real-time. We also send conversion-value signals so each platform’s algorithm learns which lookalikes to skip. On a monthly cadence, findings are filed with Meta and Google; TikTok and AppLovin use weekly pre-invoice submissions. Review windows are about 90 to 120 days for Meta and Google and about 2 weeks for TikTok and AppLovin. If a platform does not respond to a valid filing, Mastercard network recovery is initiated.

What we collect, and what we don’t

We check the full IP address against lists of known bad actors. We do not collect names, emails, or phone numbers, and we do not track people across sites. A session ID stays in the visitor’s browser.

Audit log

Audit records are stored in an append-only log. Each finding keeps its original evidence and timestamp, so the report a platform receives matches what was generated. Hosted on AWS and Google Cloud, in the United States.

Process timeline

The customer lifecycle, end to end.

From enrollment through proactive blocking, monthly audit filing, recovery, and rebate payout.

  1. 01 Enroll One time
    Day 1

    Enrollment and setup

    Kickoff call with the Dash.fi implementation manager. Platform access is provisioned via the Meta Partner ID and a Google Ads MCC link. The Dash.fi card is set as the default payment method. The Ad Pay Protection pixel is installed on the client site via Shopify Theme.Liquid, manual HTML, or Google Tag Manager.

    • Meta Partner ID
    • Google Ads MCC link
    • Pixel installed
    • Payment method set
  2. 02 Learn Passive
    Days 1–3

    Learning phase

    The pixel collects a behavioral baseline. No exclusions are pushed during this period. The audit establishes the client’s traffic fingerprint so it can tell legitimate visitors from non-compliant traffic going forward.

    • ~3 days post-install
    • Zero exclusions active
    • Baseline built
    • No campaign changes
  3. 03 Block Ongoing
    Day 3 onwards

    Proactive exclusions active

    Non-compliant profiles go into a Meta Ads Custom Audience the campaigns exclude, and matching exclusions are applied in Google Ads, in near real-time. We also send conversion-value signals so each platform’s algorithm learns which lookalikes to skip. Identified non-compliant traffic leaves the bidding pool before the next auction fires, so the spend never happens. The lowest-spend campaign activates first under a staged rollout.

    • Meta Custom Audiences
    • Google Ads exclusions
    • Conversion-value signals
    • Lowest-spend first
  4. 04 Audit Monthly
    Month-end

    Monthly audit compiled

    Dash.fi compiles the Legally Defensible Amount (LDA) for the month: the dollar value of the contractual violations the audit found. Each item is tied to a real Google or Meta click ID and the actual average cost-per-click from the client’s billing. The output is a Forensic Audit Report.

    • Click-ID evidence
    • Actual CPC from billing
    • Append-only audit log
    • IAB + MRC standards
  5. 05 File Monthly
    15th of following month

    Formal filing submitted

    The findings are submitted to Meta and Google as a formal audit filing. For TikTok and AppLovin, weekly pre-invoice submissions are made before revenue recognition closes. Pre-invoice filings usually resolve faster than post-invoice.

    • Meta / Google filing
    • TikTok weekly pre-invoice
    • AppLovin weekly pre-invoice
    • Mastercard backstop ready
  6. 06 Review Waiting
    90–120 days

    Platform review period

    The platform reviews the filing. Meta and Google typically take 90 to 120 days. TikTok and AppLovin resolve in about two weeks, faster for pre-invoice submissions where the revenue has not yet been recognized.

    • Meta / Google: 90–120 days
    • TikTok: ~2 weeks
    • AppLovin: ~2 weeks
    • Backstop if no response
  7. 07 Recover Recovery
    After resolution

    Credits applied

    Confirmed credits are applied directly to the client’s ad account balance, visible in their Billing section. If a platform does not respond to a valid filing within the expected window, Dash.fi pursues cash recovery through the Mastercard network using the client’s Dash.fi card.

    • Credits in ad account
    • Visible in billing
    • Cash recovery via Mastercard
    • Evidence retained
  8. 08 Rebate Rewards
    Net-60

    Rebate paid

    Monthly rebates accrue on qualified ad spend and are paid Net-60 to the client’s Dash.fi rewards wallet. The 1% Rewards Accelerator applies to qualified Meta card spend specifically. Google Ads, TikTok, and AppLovin spend earns the base rebate only.

    • 2% base rebate (Meta CC)
    • 1% accelerator (Meta CC)
    • Paid Net-60
Confirmed with product

Share the full picture with your team.

This is the confirmed Ad Pay Protection data flow — built for security reviews and customer technical questions. Book a walkthrough, or talk to your Dash.fi contact.

Book a demo Talk to sales
  • Hosted on AWS + Google Cloud, in the US
  • Audited to IAB + MRC standards
  • Append-only audit log