Run one account audit. Keep the watch with a plan.

• Connect an eligible Google Ads account and run one deterministic audit without a card.
• A trial or plan keeps repeat audits, daily monitoring, alerts, the agent and approved publishing available.
• If ongoing service ends, new reads stop and the reports already stored in your workspace remain visible.

The commitment is written down. Our terms state the same boundary: one initial deterministic audit is included per eligible account, while repeat audits, monitoring, alerts and AI require an active trial or subscription. A test reads that clause and the server gate together.

Section 03 · every check, named

Fourteen checks on a Meta account. Twenty-one Google rules in the catalog.

A Google audit selects the rules that fit the workspace: twelve for ecommerce or twelve for a service business. It never runs all twenty-one at once. When Meta and Google Ads are both connected, you get two audits, two histories and two alert streams because the numbers are not comparable across platforms. Every finding names the rule that fired and the bar it was judged against.

Section 04 · one finding, in full

This is a finding. The words are written in code, so they cannot be talked up.

Section 05 · where the bar comes from

Judged against your account. Not against an industry average.

There is no universal answer to how many clicks with nothing to show is too many, or what return on ad spend counts as profitable. Both depend on your business, so both are computed from your own numbers, and every finding prints the basis it used so you can argue with the right thing.

If you have not set a margin, the audit still runs. It falls back to breakeven on ad cost, records that it did, and the stored report says which bar it judged against, so a reader months later can tell an ad-cost audit from a profitability one instead of assuming. Withholding the whole product until somebody fills in a number they may not know is a worse answer than running and being honest about what could not be judged. Every bar the audit and the agent judge against, and where each one's number comes from, is tabled on the diagnosis page.

Section 06 · how wasted spend is computed

The exact sum. And the three things we refuse to add to it.

wasted spend = sum of spend on campaigns where
  the campaign is delivering and spent in the window
  the objective is sales
  purchases = 0
  spend >= the money floor (US$50, in your currency)
  campaign age >= 4 days

critical when that total >= 10% of live sales spend

wasted search spend = sum of spend on search terms where
  conversions = 0
  and either  clicks >= 3x your account's clicks per conversion
  or          spend  >= 2x your account's cost per conversion

reported only when that total clears the money floor
and holds >= 10% of search spend (critical at 25%)

Three things could inflate that number and none of them belongs in it.

Section 07 · what lands in your inbox

You hear from it when something changed. Not every morning.

Section 08 · what it will not do

What it will not do. Written down, so you can hold us to it.

• Changes need your permission. Scheduled checks can prepare findings and handle supported fixes only with write access, a separate current account permission, reviewed rules, qualifying evidence and your saved limits. The result is checked before it is reported as verified.
• New public work still needs you. New ads, switching ads on, new countries, destination changes and higher total spending need your exact decision. A scheduled finding or a connected account cannot supply that permission.
• Some included work uses a model. Deterministic checks use no model. Included audit summaries and static creative checks are paid by iNudge and use no customer credits. Each has its own account limit. Other requested AI-written reports use their agreed credits.
• The audit page starts with Google Ads. The controlled beta offers Google Ads accounts. Existing Meta test connections may also be audited for supervised validation, but Meta is reviewer-only while app review completes.
• Service businesses get a different Google audit. A service workspace runs twelve applicable Google checks for its selected lead outcome, campaign goals, settled spend and privacy-safe call patterns. Ecommerce runs twelve. Qualified-lead deterioration remains unassessed until a tenant-bound CRM series supplies compatible cohorts. Meta messaging campaigns are still excluded from purchase-based profit checks.
• It does not audit GA4 or Search Console. GA4 has a read-only traffic-source path and Search Console a read-only search-query path, both open to the controlled beta and read nightly and live in chat. Neither is an advertising audit engine, and no audit check reads either.
• It does not audit Shopify. Your store feeds the revenue side and the return-rate measurement that sets your profit bar. There is no commerce audit. Shopify is read-only today: no write permission is requested and no write path exists in our code.
• It does not settle yesterday by breakfast. Ad platforms keep attributing conversions for days after a day closes, so a figure read this morning can move. Nothing here pretends otherwise: every finding carries the window it was measured over and the moment the data was pulled, and the diff that decides whether to alert you compares one scheduled run against the previous one rather than against a moving target.

Section 09 · what it needs and what it can touch

What it needs, and what it can touch.

1. Meta. We ask for ads_read, ads_management and business_management, and, because Meta ties every ad to a Page, pages_show_list and pages_read_engagement to show Page details at connect. We also request optional pages_manage_ads for a separately approved, paused ad on a named Page; existing connections need a new Meta grant for that action. This does not publish a Page post. Where the connection runs through Facebook Login for Business the permission set is decided by a configuration in our Meta app rather than by our code, and Meta's own consent screen shows you the permission set you are actually granting. That screen is the authority, and we will not tell you otherwise.
2. Google Ads. There is one Ads permission Google publishes and it is read plus write. Read-only behavior is enforced by our own code and by the per-account write switch, not by the permission.
3. Shopify. Order revenue over a window is a sample taken from a capped read, and the sample size is returned and shown alongside the figure. Any blended figure built on it inherits the same caveat.

The full permission table, the exact changes and what we never collect are on the security page.

Section 10 · straight answers

Straight answers to the questions that decide it.