Google Ads guide

Google Ads Display Network Settings Checklist

Use this Google Ads Display Network settings checklist before launch, after a major change, and during a scheduled performance review. Confirm the campaign’s job and conversion first, then check reach, targeting, observation, inventory, placements, creative, landing pages, devices, measurement, and business quality. The checklist is designed to expose missing decisions; it is not a reason to select every possible setting.

Display campaigns can look complete while a critical boundary is still unclear. An audience may be too narrow to deliver, an exclusion may remove the intended inventory, an asset may not match its page, or a conversion may count an action the business does not value. Work through the stages below and keep the completed record with the campaign change history. For the reasoning behind the controls, read the Display Network settings best practices guide.

1. Campaign purpose and ownership

Complete these checks before editing the interface:

  • [ ] The campaign’s primary job is written as awareness, qualified traffic, leads, sales, remarketing, or another specific outcome.
  • [ ] The audience, context, geography, language, budget, sales capacity, and expected conversion lag are documented.
  • [ ] The primary conversion or value signal is named, and its business-quality stage is clear.
  • [ ] Prospecting, remarketing, and materially different objectives have a separation plan.
  • [ ] A campaign owner is responsible for settings, brand suitability, measurement, and the review schedule.
  • [ ] The hypothesis for the first test and the evidence needed to widen, narrow, pause, or rebuild are recorded.

The Google Ads overview of the Display Network can help explain the possible network reach. It does not decide whether that reach is appropriate for this brand or objective.

Confirm the decision boundary

Answer these questions in plain language: who or what should make an impression, where may the ad appear, what is never acceptable, and what result makes the spend worthwhile? If the team cannot answer them, mark the checklist incomplete. A vague objective cannot be repaired later by a precise exclusion.

2. Conversion and landing-page readiness

Before enabling spend, confirm:

  • [ ] The final URL loads on mobile and desktop without an unexpected redirect or error.
  • [ ] The headline, offer, eligibility, location, price, and call to action match the destination.
  • [ ] Forms, phone links, checkout, account creation, and other primary actions have been tested.
  • [ ] Consent behavior does not block required analytics or create an unmeasured path.
  • [ ] Analytics, auto-tagging or tracking parameters, conversion tags, and offline imports are verified.
  • [ ] Duplicate events, premature page-load conversions, refunds, and missing values are handled.
  • [ ] Qualified lead stages or revenue imports are available when the business depends on them.
  • [ ] The normal conversion lag and the minimum review window are written down.

Do not use a click metric as a substitute for a broken conversion path. If the page or tracking fails, resolve that issue before changing the campaign’s audience or inventory.

3. Campaign, network, and targeting scope

Review the campaign’s saved state against the brief:

  • [ ] The campaign type, objective, budget, bidding, and primary conversion match the intended job.
  • [ ] Network scope is understood for the current campaign type and account interface.
  • [ ] The campaign is not unintentionally mixing a separate Search-network decision with a Display measurement boundary.
  • [ ] Audience, contextual, keyword, topic, and managed-placement methods have a stated role.
  • [ ] The initial scope is large enough to learn but not broader than the brand or business can support.
  • [ ] Targeting and observation choices are deliberate and have been verified after saving.
  • [ ] Audience membership, exclusions, overlap, and remarketing windows are eligible and current.

Google’s network settings guidance and targeting and observation guidance describe the general concepts. Confirm the exact controls and labels in the current account rather than copying an old setup.

Check for conflicting scope

If delivery is unexpectedly low, look for overlapping audience exclusions, a tiny placement list, restrictive geography, schedule, language, device, or a targeting mode that was not intended. If delivery is unexpectedly broad, check whether a report-only audience was treated as a restriction or whether additional network or inventory scope was enabled.

4. Inventory, content suitability, and placements

Complete the brand-safety and placement review before launch:

  • [ ] Content categories and environments that are never acceptable are named.
  • [ ] Inventory and content-suitability choices match the written brand policy.
  • [ ] The scope of each account, campaign, or shared exclusion is known.
  • [ ] Known unsafe or irrelevant placements have narrow, documented exclusions.
  • [ ] Managed placements have a reason to exist, a relevant audience, and enough potential inventory.
  • [ ] An owner will review actual placements after delivery begins.
  • [ ] The campaign distinguishes “not yet reviewed” from “not acceptable.”
  • [ ] A blocklist will not be expanded from click-through rate alone.

Use Google’s Display content exclusion documentation to understand the available controls. A placement list is not a substitute for checking actual delivery. Review sites, apps, videos, context, spend, impressions, conversions, business quality, and policy suitability together.

Placement review decision

For each important placement, record one action: allow, watch, exclude, or escalate. Include the reason, scope, owner, date, and expected effect on reach. This creates a maintainable policy instead of a list of unexplained exclusions.

5. Creative, destination, and delivery settings

Before publishing, verify:

  • [ ] Images, logos, headlines, descriptions, video, and offers are approved and eligible.
  • [ ] The ad message is understandable in the formats and sizes the campaign can serve.
  • [ ] Claims, prices, availability, eligibility, and offer dates match the landing page.
  • [ ] Creative variations have a stated test purpose and are labeled in the change record.
  • [ ] Mobile and desktop pages render correctly for the important placements.
  • [ ] Locations and languages match the business’s service and sales process.
  • [ ] The schedule reflects service hours, call handling, fulfillment, or another real constraint.
  • [ ] Device settings are based on the complete user journey, not a click metric alone.

Do not use a creative approval state as proof that the campaign is commercially ready. A policy-compliant asset can still promise the wrong thing, attract the wrong user, or fail to explain a qualification on the destination.

6. Save and launch verification

Immediately before publishing, compare the final settings summary with the campaign brief:

  • [ ] Campaign type, objective, budget, bid strategy, and primary conversion are correct.
  • [ ] Network, targeting, observation, audience, contextual, and placement scope are correct.
  • [ ] Locations, languages, schedule, devices, final URLs, and tracking are correct.
  • [ ] Content suitability, inventory, and exclusions are correct and owned.
  • [ ] Creative assets, policy status, offer terms, and destinations are correct.
  • [ ] The final state, editor, date, hypothesis, and review window are saved in the change record.

After launch, verify eligibility and actual delivery. Check policy status, impressions, spend, placements, devices, locations, audience mix, creative delivery, clicks, conversions, value, and landing-page behavior. Do not make a second major edit before the first state has been recorded.

Confirm the first useful signal

The first review should answer whether the campaign is reaching the intended boundary and recording the intended outcome. It does not need to answer every optimization question. Note what is still unknown, the conversion lag that remains, and the next date when the evidence will be sufficient.

7. Ongoing review and optimization

At each scheduled review, mark these items:

  • [ ] Actual placements are consistent with the content and brand-safety policy.
  • [ ] Audience and contextual delivery are consistent with the intended campaign job.
  • [ ] Spend and clicks are compared with qualified conversions, value, or the planned awareness outcome.
  • [ ] Conversion lag, imported stages, consent, duplicate events, and tracking changes are accounted for.
  • [ ] Device, location, language, schedule, creative, and landing-page segments are reviewed.
  • [ ] Exclusions are narrow, justified, and not removing more reach than the business accepts.
  • [ ] Budget and bidding are evaluated against marginal quality and capacity, not blended averages alone.
  • [ ] The next action has one diagnosis, one change, a success threshold, and a rollback trigger.

Use the Display Network optimization guide when a review finds a performance constraint. If a setting is broken rather than merely inefficient, use the Display settings troubleshooting guide.

Common checklist failures

A checked box is not useful when the answer is only assumed. Watch for these weak completions:

  • “Targeting is set” without explaining whether it is a delivery boundary or an observation signal.
  • “Brand safety is handled” without naming the inventory policy, scope, and owner.
  • “Tracking works” without testing a real form, call, checkout, or imported quality stage.
  • “The placement is good” because it has clicks, without checking context and business quality.
  • “The campaign is optimized” because cost per click fell, while qualified outcomes declined.
  • “The page is ready” without testing the device, location, language, or consent path that received delivery.
  • “The review is complete” before conversion lag and reporting changes are considered.

If a check is unknown, keep it open and assign an owner. An unresolved question is safer than a false pass that pushes an untested setting into production.

Sources and related guides

For the current adz.so audit entry point, see the product overview. It describes audit functionality and does not imply that adz.so manages Google Ads campaign settings.