Spend and results, compared
Each run compares spend and results with the last, and lists the campaigns that moved them.
Loop · in build
Is your own advertising getting better or worse?
Connect your ad accounts, read-only. On each run the audit will compare spend, results and creative with the last run and flag what moved, which campaigns moved it and which ads have run too long without a refresh.
In build · not on sale Waiting on two things outside our code: a Google Ads developer token and a confirmed Meta connection route. Not built, not on sale.
Your accounts, compared with the last run
- ChangedGoogle Ads · spendSpend up on the brand campaign; results flat
- Not checkedMeta · creativeAccount connection expired — not read this run
- NewMeta · creativeAd flagged: running long without a refresh
- GoneGoogle Ads · campaignsSummer campaign paused since last run
- Accounts connected through Pipedream Connect; we never hold your password
- Read-only
- Source: src/lib/connect/pipedream.ts (header) · checked 2026-10-13
- What Pipedream Connect is wired for in the engine today
- GA4 and Search Console
- Source: src/lib/connect/pipedream.ts (CONNECT_APP_GA4, CONNECT_APP_GSC) · checked 2026-10-13
- Google Ads API access needs a developer token we do not have yet
- Token pending
- Source: docs/LOOPS.md (branch feat/loops) "Kinds" (own_ads_audit) · checked 2026-10-13
What it will be
What it will be, and what it is built from.
A loop that reads the Google Ads and Meta ad accounts you connect, read-only, and flags what changed in your own spend, results and creative since the last run.
Spend drifts up. A campaign that used to convert stops. An ad runs for months until the audience is sick of it. Nobody compares this month with last month on purpose, so each one is noticed late.
The own-ads audit will do that comparison for you. You connect your Google Ads and Meta ad accounts read-only; on each run the audit reads spend, results and creative, compares them with the last run and lists what moved, with the campaigns behind each movement. It will also flag creative that has run long without being refreshed.
Connections go through Pipedream Connect, the same hosted sign-in the engine already uses for Google Analytics and Search Console. You authorise access with the ad platform itself; your credentials stay with Pipedream and never touch our code. We hold only an opaque account reference, and the access is read-only.
Two things outside our code stand between this page and a working loop. Google requires a developer token, granted after its own review, before any tool can read Google Ads accounts through its API; we have not got one yet. On the Meta side, the connection route has to be confirmed. Until both are in place this loop is in build, does not run for anyone and is not on sale.
Who it is for
- Owners who pay for ads but do not live in the ad accounts
- Small marketing teams who want a regular second look at their own spend
- Anyone handing ads to an agency and wanting an independent read
What it will do
What each run will look at.
Stale creative
Ads that have run a long time without a refresh are flagged for a look.
Read-only connection
Accounts are connected through Pipedream Connect, read-only. Nothing is changed in your accounts.
Your numbers stay labelled
Private account data is kept apart from public-data findings, and labelled as yours.
By hand, or with it
The same job, two ways.
By hand
- Log in to each ad platform and export reports
- Compare this month with last in a spreadsheet, if at all
- Notice tired creative only when results drop
- Rely on whoever runs the ads to report on them
With the loop, once it ships
- Accounts read on the cadence you set
- What moved since last run, with the campaigns behind it
- Long-running creative flagged
- An independent read of your own accounts
What you walk away with
What you keep.
A change list
What moved in spend and results since the last run, campaign by campaign.
A refresh list
Creative that has run long enough to deserve a look.
A second opinion
An outside read of your accounts that does not depend on who runs them.
One place
Google and Meta read side by side, once both connections are in place.
How it will work
Three steps.
Connect your accounts
Sign in with Google Ads and Meta through Pipedream Connect, read-only.
Set the cadence
How often the accounts are re-read, in whole days.
Read what moved
Spend, results and creative compared with the last run.
Limits
What it does not do.
- It is not built. It needs a Google Ads developer token (granted by Google after review) and a confirmed Meta route before any code can read your accounts.
- It is read-only by design. It will not change bids, budgets, campaigns or ads.
- It reads what the platforms report. It does not fix attribution or reconcile ad-platform numbers with your sales.
- Platforms beyond Google Ads and Meta are not planned for the first version.
Price
See current pricingNot on sale. No price yet.
The own-ads audit is being built. When it runs in production the pricing page will say which plans include it; until then nothing is charged and nothing is promised.
FAQ
Own-ads audit: questions
Can I connect my ad accounts today?
No. The audit is in build and waits on a Google Ads developer token and a confirmed Meta route. Join the loops list to hear when it ships.
Will you be able to change anything in my accounts?
No. The connection is read-only by design, and the audit only reads.
Do you see my password?
No. You sign in with the ad platform through Pipedream Connect. Your credentials stay with Pipedream; we hold an opaque account reference.
Can I connect Google Analytics instead?
The engine already supports connecting Google Analytics and Search Console from a report, read-only. The integrations page lists what connects today.
What will it cost?
Nothing is priced yet. When it runs in production, the pricing page will say which plans include it.
Get on the list for this loop.
Waiting on two things outside our code: a Google Ads developer token and a confirmed Meta connection route. Not built, not on sale.