Google Ads Performance Max Checklist

Use this Google Ads Performance Max checklist before launch and again after the campaign has collected enough data to evaluate. The important checks are not limited to whether every field is filled in. You need to confirm that the campaign has a clear business goal, reliable conversion data, enough budget, useful assets, eligible destinations, and a review process that can distinguish real business results from platform-reported activity.

Google’s Create a Performance Max campaign guide covers the campaign setup flow, while its asset group guidance explains how creative assets are organized. Use this page as an operational checklist and pair it with Google Ads Performance Max best practices when you need the reasoning behind each decision.

Start with the business goal

Do not begin by checking headlines. Begin with the outcome the campaign is supposed to produce. A campaign optimized for qualified leads needs a different measurement plan from one optimized for ecommerce purchases, store visits, or another approved objective.

Name the primary business outcome in one sentence.
Decide which conversion action or value represents that outcome.
Separate primary optimization actions from secondary observation actions.
Confirm that duplicate tags, imported events, and test conversions are not inflating the signal.
Agree on the acceptable cost, return, lead quality, or volume range before launch.
Identify who will review sales quality or fulfillment after the ad platform reports a conversion.

For lead generation, a form completion is often only an initial event. If the sales team rejects most submissions, optimizing toward every form can teach the campaign to find more low-intent forms. Document the later stage that matters and decide how it will be brought back into measurement.

Check the campaign settings

Open the campaign settings and read them as a set rather than accepting the defaults one by one. The official evaluation guide is useful after launch, but many later problems are created by an unclear setup at the start.

Campaign name identifies the market, offer, and objective.
Location targeting matches where the business can actually serve customers.
Language settings fit the landing pages, sales process, and customer base.
The chosen conversion goal is appropriate for this campaign, not merely available in the account.
The schedule, start date, and time zone are intentional.
The final URL domain is owned, reachable, and consistent with the offer.
The daily budget fits the expected conversion volume and business capacity.
Bid strategy and target values reflect a measured objective rather than an arbitrary number copied from another campaign.
Brand exclusions, content suitability choices, and other controls have an owner and a reason.

If a business only serves a small area or has limited appointment capacity, more reach is not automatically better. A campaign can be technically healthy while creating more demand than the team can answer. Record the operational constraint before interpreting delivery as success.

Verify asset groups

An asset group should represent a coherent offer, audience context, or product theme. It should not be a storage drawer for unrelated copy and images. Check the asset group name, theme, destination, and the relationship between the creative and the page a user will see.

Text assets

Headlines explain the problem, offer, proof, or next step.
Long headlines and descriptions add information instead of repeating one short claim.
Wording is accurate at the broad combinations the system may assemble.
Prices, availability, guarantees, and qualifications match the landing page.
The call to action tells the user what will happen next.
Pinned text is used only when a legal, brand, or message-order requirement truly needs it.
There are enough distinct ideas to let combinations be meaningful.

Read the assets in unexpected combinations. A headline that is safe by itself can become misleading when paired with a description promising a different offer. Avoid claims that depend on a narrow context the assembled ad may not provide.

Image, logo, and video assets

Images show the product, service, customer outcome, or relevant setting.
Each format remains legible when cropped or shown on a small screen.
Logos are current and have adequate contrast.
Visuals do not rely on tiny text or a disclaimer that disappears on mobile.
The business has supplied an appropriate video or has a deliberate plan for the video experience that Google may create.
Every asset is approved, correctly associated, and free of avoidable policy or destination mismatches.

Use the Google Ads asset requirements and guidance as the source of truth for current format and policy details. A checklist can confirm that assets exist; it cannot replace reading them as a customer would.

Review products, feeds, and listing data

If the campaign uses Merchant Center or another feed, check the data source separately from the campaign interface. A green campaign status does not mean that every item, price, image, or destination is eligible and current.

The intended Merchant Center account or feed is connected.
Products are approved for the target country and destination.
Prices, stock, shipping, promotions, and availability match the site.
Product titles and images identify the actual item clearly.
Disapprovals and warnings have an owner and a resolution date.
Listing groups include the products meant for this campaign and exclude the products that are not part of the offer.
Feed updates have completed before judging product coverage.
The product page, cart, and checkout work from an ad click.

For a non-retail campaign, the equivalent check is the service or location data behind the asset group. Remove obsolete offers, closed locations, discontinued products, and pages that no longer lead to a meaningful action.

Audit URLs and landing pages

Performance Max can use more than the URL typed into the initial setup. The campaign therefore needs an explicit destination review. Google’s Final URL expansion documentation describes how the feature can select more relevant pages and how exclusions and rules can shape that behavior.

The final URL loads with no server error, redirect loop, or blocked resource.
Mobile and desktop versions show the same core offer.
The page has one obvious next action.
Form, phone, booking, purchase, and consent flows work in a normal browser.
Conversion tags fire once on the intended completion event.
Thank-you, login, careers, legal-only, cart, search, and other unsuitable paths are excluded where appropriate.
URL parameters do not break analytics or produce duplicate page variants.
URL exclusions and page-feed rules are documented and tested.
The message and qualification in the ad are visible on the destination.

Do not exclude an entire section merely because one page is weak. Fix or remove the weak page, then check whether the remaining destinations support the goal. An exclusion list should protect the budget from genuinely unsuitable pages, not prevent the system from reaching useful pages that the initial URL did not represent.

Confirm audiences and search themes

Audience signals and search themes can provide useful context, but they are not a substitute for a clear offer, accurate conversion data, or a usable page. Review each signal for a reason to include it:

The segment describes likely customers rather than everyone who could see the product.
First-party lists have permission, recent membership, and enough relevance.
Custom segments use current search, product, or competitor context.
Search themes describe the language customers use for this offer.
Signals are labeled as hypotheses to learn from, not promised reach limits.
The team knows what evidence would make a signal useful or disposable.

Avoid adding dozens of vague interests to make the setup look complete. A short set of defensible inputs is easier to interpret than a long collection of ideas that all change at once.

Validate measurement before launch

Complete a real test from ad destination to reported result. Use the browser, phone, checkout, or booking workflow a customer will use, not only a tag helper or a preview screen.

The conversion action records the intended event and no earlier event.
Revenue or lead value is passed in the expected currency and format.
Consent and privacy behavior match the site’s implementation.
Analytics and Google Ads do not double-count the same transaction or lead.
Call, chat, offline, CRM, or imported conversions have clear timestamps and matching identifiers where applicable.
The reporting time zone and attribution settings are documented.
A test conversion can be traced from click or visit through business follow-up.
Conversion lag is known before a launch-day report is treated as final.

If the test fails, pause the launch checklist at measurement. More creative or more budget cannot repair an optimization signal that records the wrong event.

Use a controlled launch review

Before publishing, have a second person read the campaign summary and answer these questions without opening every screen:

What outcome is the campaign buying?
Which action tells the system that the outcome occurred?
Which people and locations should be eligible?
What page will a user reach, including pages chosen through URL expansion?
What would make the team pause or change the campaign?

If two reviewers give different answers, the setup is not ready. Save screenshots or a short change record with the launch date, budget, target, assets, feed state, URL controls, and conversion test result. This makes later diagnosis possible when the interface has changed or several people have edited the campaign.

Check the first review window

The post-launch checklist should be scheduled, not improvised after a bad day. The first review is for eligibility, tracking, destinations, and obvious quality problems. It is not a reason to rewrite every asset or change the target after a small amount of noise.

Campaign and asset groups are serving as expected.
Ads and products are approved where they should be.
Search terms, pages, placements, or other available diagnostics do not reveal an obvious mismatch with the offer.
Spend is occurring in the intended market and within the operating budget.
Conversion events arrive with plausible timing and values.
Leads or orders can be checked in the CRM, support queue, or fulfillment flow.
Destination reports do not show a new concentration on unsuitable pages.
The review date accounts for conversion lag and the sales cycle.

For deeper diagnosis, use how to fix Google Ads Performance Max and compare the symptom with the goal, data, budget, assets, feed, and URL path before making a change.

Decide what to change

When a check fails, make the smallest change that addresses the evidence. A tracking failure calls for a measurement fix. A disapproved product calls for a feed or policy fix. A weak lead-quality pattern may require a better qualification event or landing page. Raising the budget is not a universal response to any of these problems.

Keep a change log with the date, hypothesis, edit, expected result, and review date. Change one meaningful group of variables at a time when possible. If a campaign has a serious destination, compliance, or conversion problem, protect the business first and document the pause rather than allowing spend to produce unusable data.

Final Performance Max checklist

Before you call the campaign ready, confirm all of the following:

[ ] Business outcome, primary conversion action, and success range are clear.
[ ] Locations, languages, schedule, budget, and bid target match capacity.
[ ] Asset groups have distinct themes and accurate destinations.
[ ] Headlines, descriptions, images, logos, and video work in combinations.
[ ] Products, services, feeds, approvals, and listing groups are current.
[ ] Final URLs, page expansion controls, exclusions, and rules are reviewed.
[ ] Landing pages, tracking, consent, values, and offline handoffs are tested.
[ ] Audience inputs and search themes are purposeful and documented.
[ ] Launch ownership, review timing, conversion lag, and pause conditions are recorded.
[ ] The first review will compare platform data with actual business outcomes.

If the checklist exposes a missing decision, resolve that decision before adding more assets or budget. For an educational review of the account’s options, visit adz.so; the site’s available tools and workflows should be confirmed before promising a product-specific implementation.