Skip to content
Apply now
Ads Agent

Where your ad data goes, and what happens to it.

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 traffic quality report. Built for security reviews and customer technical questions.

Book a demo See the data flow
Dash.fi · Ads Agent

Connection matrix

Search

$84,200

Social

$46,800

More soon

—

Audit log

  • Ingesting ad spend feeds…Search
  • Cross-referencing bid history…Social
  • Running invalid-traffic audit…Search
  • Flagging billing overcharges…Social
  • Preparing traffic quality report…
32 invalid-traffic charges found$4,820

At a glance

AWS + Google Cloud
Hosted in the United States
Append-only
Evidence kept for every flag
End-to-end data flow

From a page view to a traffic quality report.

Every signal is checked, scored, and packaged with its evidence. Dash.fi prepares the traffic quality report, you submit it, and the results stay open to 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 reported.

    1. Step A

      Signal scoring

      Each visit is checked for signs of invalid traffic.

    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 estimate of the invalid spend.

    Output flagged events with supporting evidence and an estimate of the invalid spend.

The flow forks here

  • 04A Exclusion API push

    Real-time suppression

    Non-compliant profiles go into exclusion audiences on your search and social ad platforms. We also send conversion-value signals, so their algorithms learn which lookalikes to skip.

  • 04B Monthly traffic quality report

    Prepared every month

    Dash.fi prepares the traffic quality report with its evidence. You submit it to the ad platform, which reviews it.

  1. 05 Reporting and delivery

    Monthly traffic quality report

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

  2. 06 Client

    Independent verification

    Any credits the platform issues show in your ad account billing. Exclusion audiences are visible in your ad platform. 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 credits

Where the value lands: exclusions live on the platform, and any credits the platform issues land in your ad account.

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, ad 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 invalid spend.

Exclusion push and reporting

Non-compliant profiles go into exclusion audiences on your search and social ad platforms, in near real-time. We also send conversion-value signals so each platform’s algorithm learns which lookalikes to skip. Every month, Dash.fi prepares the traffic quality report and you submit it to the platform.

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, the monthly traffic quality report and platform review.

  1. 01 Enroll One time
    Day 1

    Enrollment and setup

    Kickoff call with the Dash.fi implementation manager. Platform access is provisioned through each ad platform’s partner access. The Dash.fi card is set as the default payment method. The Ads Agent pixel is installed on the client site via Shopify Theme.Liquid, manual HTML, or Google Tag Manager.

    • Ad platform access
    • 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 exclusion audiences on your search and social ad platforms, 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.

    • Exclusion audiences
    • Conversion-value signals
    • Lowest-spend first
  4. 04 Audit Monthly
    Month-end

    Monthly audit compiled

    Dash.fi compiles the month’s findings: the dollar value of the invalid traffic the audit found. Each item is tied to a real ad click ID and the actual average cost-per-click from the client’s billing. The output is the traffic quality report.

    • Click-ID evidence
    • Actual CPC from billing
    • Append-only audit log
    • IAB + MRC standards
  5. 05 Submit Monthly
    Following month

    Report submitted

    Dash.fi prepares the traffic quality report and you submit it to the ad platform.

    • Prepared by Dash.fi
    • Submitted by you
    • Evidence retained
  6. 06 Review Waiting
    Varies by platform

    Platform review period

    The ad platform reviews the report. Review times vary by platform.

    • Platform review
    • Evidence retained
  7. 07 Credits After review
    After resolution

    Credits applied

    Any credits the platform confirms are applied to the client’s ad account balance, visible in their billing section.

    • Credits in ad account
    • Visible in billing
    • Evidence retained
Data flow and process

Share the full picture with your team.

This is the Ads Agent 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
  • Append-only audit log