How to Audit a Google Ads Account for Agencies

To audit a Google Ads account for an agency client, establish the client’s commercial contract and data boundaries before reviewing settings. Then trace campaigns to search intent, destinations, conversions, approvals, CRM or commerce outcomes, and the report the client receives. An agency audit should reveal both account performance and whether the operating process can reproduce a trustworthy result across client teams.

This is an educational process, not legal, privacy, financial, or platform-policy advice. Use approved evidence and consult Google Ads Help and Google Ads policy guidance.

Establish the client contract and account owner

Record the client, products, markets, business model, customer stages, reporting currency, time zone, date range, budget authority, agency scope, client owner, and approval path. Write what the client has hired the agency to improve: qualified pipeline, purchases, bookings, profitable revenue, retention, reach, or another outcome. Keep an account audit distinct from a general marketing strategy review.

Separate impression, click, visit, lead, qualified lead, sales acceptance, opportunity, closed deal, order, payment, refund, repeat value, and margin. Define which stages the agency can observe and which require a client-side join. A report cannot prove a stage the agency has never been given reliable evidence for.

Check manager-account boundaries

Confirm the account, manager account, analytics property, tag container, CRM, commerce platform, call system, product analytics, and reporting dashboard all refer to the same client and market. Review user access, ownership, agency and client permissions, billing responsibility, shared audiences, shared budgets, and account links. Unexplained access or inherited settings are operational findings, not harmless background detail.

Record consent assumptions, customer-list rules, enhanced or offline conversion approvals, data retention, vendor access, and the process for removing an agency user. Do not copy customer records into an audit worksheet simply to make a join easier.

Review structure, intent, and change history

Map campaigns and ad groups to client goal, product or service, market, landing page, audience, conversion, budget, and owner. Inspect search terms, locations, languages, devices, schedules, networks, audiences, exclusions, negative keywords, budgets, bid strategies, and change history.

Classify demand as category, brand, product, service, pricing, comparison, competitor, support, job, supplier, existing-customer, or irrelevant intent. Look for campaigns that combine different clients, countries, languages, products, sales motions, or reporting goals without a documented reason.

Use change history to separate inherited account behavior from agency changes. Mark client-requested, agency-approved, automated, platform-recommended, test, emergency, and unknown changes. A performance shift should not be attributed to an agency action when the account history does not support that conclusion.

Inspect ads, pages, and client claims

Follow representative searches through the ad and destination. Confirm that product, audience, market, price, availability, proof, qualification, consent, privacy, and CTA agree. Review current client approvals for logos, reviews, credentials, comparisons, savings, guarantees, performance claims, promotions, and regulated-service language.

Test mobile and desktop routes, forms, calls, calendars, carts, checkout, signup, trial, or demo paths. Record whether the page delivers the promised action and whether the client can actually fulfill it. A good ad and a broken client process are still a bad acquisition path.

Verify tracking, reporting, and value

Use approved test journeys to trace click identifiers, consent, analytics events, calls, forms, ecommerce or product events, CRM stages, invoices, payments, refunds, and repeat value. Check event creation, deduplication, source fields, attribution windows, timestamps, time zones, currencies, offline imports, and reporting filters.

Compare the platform report with the client’s source of truth. Keep reported, accepted, booked, invoiced, collected, recurring, refunded, cancelled, and contribution amounts separate. Do not turn an agency dashboard’s calculated metric into a client fact without documenting the formula, source, cohort age, exclusions, and limitations.

Test report reproducibility

Pick a representative client question such as “which campaigns produced qualified opportunities?” Rebuild the answer from the underlying data and compare it with the dashboard. Check that filters, date ranges, conversion actions, attribution, currency, time zone, sampling, deleted entities, and access permissions do not silently change the result.

Record the report version, owner, refresh time, source fields, and known gaps. If the agency cannot inspect sales or margin, say that the report measures media and observed lead stages only. Precision in a chart does not create evidence that the source lacks.

Review client operations and agency controls

Compare demand with the client’s response time, sales coverage, service capacity, inventory, onboarding, implementation, support, and fulfillment. Record whether a campaign runs when the client is closed, out of stock, out of territory, or unable to respond. An agency may optimize media, but the client controls many of the stages that determine value.

Review the agency’s change-control process: who can edit, who approves, how tests are labeled, how emergency fixes are recorded, how client instructions are stored, and how rollbacks are handled. Check automated rules, scripts, recommendations, experiments, budgets, alerts, and scheduled changes for ownership and expiry.

Check privacy, policy, and client risk

Review forms, calls, customer lists, remarketing, enhanced conversions, offline conversions, CRM imports, analytics, vendors, access, retention, deletion, and client instructions together. Keep names, phone numbers, addresses, health or financial details, credentials, API keys, source code, security findings, and confidential client information out of ad parameters and uncontrolled worksheets.

Check claims against current client evidence and applicable platform requirements. Escalate legal, privacy, security, regulated-industry, employment, housing, finance, health, trademark, promotion, and contractual questions. An agency should record the owner and decision, not quietly make a client’s regulated determination.

Prioritize, hand off, and retest

Give each finding an account location, evidence, impact, owner, action, expected behavior, proof condition, and client approval requirement. Prioritize broken conversion paths, wrong account ownership, unreliable joins, unapproved claims, access gaps, duplicate events, unsafe data sharing, uncontrolled automation, and campaigns the client cannot fulfill.

Repeat the original test after each repair. Preserve query, ad, page, device, market, consent state, event IDs, timestamps, report filters, and expected client record. Compare mature cohorts after unrelated changes are annotated.

Agency audit handoff

Deliver a client-readable summary with what is proven, what is not proven, what requires client action, what requires agency action, and what remains unknown. Attach the account map, change-history notes, tracking tests, report definitions, approvals, data boundaries, owners, and retest dates. For related context, see Google Ads audit checklist for local businesses, Google Ads audit checklist for lead generation, and best Google Ads audit tools. adz.so can help organize account structure, conversion tracking, and reporting review where its connected workflow supports those checks; the agency and client remain responsible for approvals, claims, data, and final decisions.