A desk review of one Google Ads launch pack, and why the verdict is hold

Verdict: hold. The proposed evidence specification is coherent enough for a future review, but no actual release candidate, client authority, account record or live observation was supplied. It would be misleading to approve a launch from documents that do not exist.

What to take away

Review object and method

CampaignSocial's editorial desk reviewed the evidence specification for a proposed client-owned Google Ads release operated by an agency from England. Research closed on 5 September 2026. We compared the proposed pack with current Google Ads access, preview and policy-status pages, then checked independent UK advertising, privacy and security controls and an international accessibility standard.

This was not a Google Ads performance or agency review, and no client funded this review; no affiliate links or supplier relationships, and the platform scope excludes Meta, TikTok, LinkedIn and other products. No login, campaign build, advert submission, audience upload or tracking deployment.

No creative preview, live render, invoice, incident drill or support contact. Legal, regulated-product and contract conclusions are outside the editorial reviewer's competence.

What the launch pack would need

Identity, ownership and spending authority

The pack must name the client entity, Google Ads account, legal product owner, media payer, operator, release authority, candidate version, currency, authorised ceiling and activation window. It also needs a client recovery route and planned removal of agency access. Google's account access record explains user levels and removal for this product, but no account export was provided here.

Finding: absent, so the object cannot leave hold.

Claims, disclosure and regulated-category decisions

Each objective claim, price statement, qualification and implied visual message needs dated support tied to the exact asset. CAP's UK misleading-advertising rules address substantiation before distribution. Marketing identification and any restricted-sector pathway require separate decisions. A Google status is not UK legal or advertising clearance.

Finding: no claim register, rights file or specialist approvals were available.

Audience, tracking and data responsibilities

Required evidence includes the intended England audience, source and authority for any uploaded data, controller or processor analysis, device storage or access decision, transparency, rights handling, transfers, retention and deletion. The ICO's final April 2026 storage and access guidance applies across the UK and covers more than cookies.

Finding: no data-flow map or signed privacy and PECR assessment was reviewed.

Accessible candidate and real delivery

The evidence should cover the exact creative, disclosure, captions or alternatives, motion and contrast, plus the destination task. WCAG 2.2 offers testable web-content criteria, although the actual test plan must specify users, devices, browsers and assistive technologies.

Google states that Ads previews show possible combinations and do not guarantee final appearance. A post-activation observation is therefore needed for the delivered version. No preview or real surface was inspected in this review.

Platform state, monitoring and recovery

Google's status guide distinguishes states such as under review, eligible, limited and disapproved. A launch record should capture that state alongside local approvals, not instead of them. It should also name monitors for spend authority, rendering, destination, data signals, access changes and complaints.

The NCSC's logging and monitoring guidance links monitoring with incident response. Evidence of pause, access removal, correction, withdrawal and restart rehearsal was not supplied.

Decision and route to reconsideration

The hold is not a finding that the unobserved campaign is defective. It means the review population contains zero inspectable release candidates. To request reconsideration, provide the versioned pack, separate specialist decisions, client release authority and live-check plan. After controlled activation, add timestamped served-format, destination, event and billing observations. Any material change restarts affected gates.

A named UK legal, privacy and PECR, advertising and consumer, regulated-product, security, accessibility, commercial, finance and measurement reviewer must decide within their competence. Until their evidence and the operational artefacts exist, neither platform status nor editorial plausibility supports a launch approval.

Before you act

Common questions

Why did the review end in a hold rather than an approval?

The review population contained zero inspectable release candidates. No login, campaign build or live render was provided, and no client funded the review. Approving a launch from documents that do not exist would therefore be misleading.

What evidence does the pack need for identity and spending authority?

It must name the client entity, the Google Ads account and the media payer. It also needs the candidate version, currency, authorised ceiling and activation window, plus a client recovery route and planned removal of agency access.

What must happen after controlled activation to support reconsideration?

Add timestamped served-format, destination, event and billing observations. Named reviewers in legal, privacy, security, accessibility and finance must then decide within their competence, and any material change restarts the affected gates.