Google Ads guide

Set Up Google Ads Performance Max for Shopify Stores

Set up Google Ads Performance Max for a Shopify store by choosing one stable collection or product route, auditing product and variant data, recording theme and app dependencies, creating matching assets, defining a completed order, and testing cart, checkout, payment, confirmation, and order records. Treat a Shopify store change as a measurement and feed change when it affects the customer path.

Performance Max cannot fix a theme, validate an app’s tracking, or make a product claim accurate. The merchant owns product data, pricing, discounts, fulfillment, privacy, consent, payment, support, returns, and spending. This guide is educational and is not Shopify, legal, financial, technical, consumer, or product-safety advice.

Step 1: Write the Shopify campaign brief

Record collection or product route, included and excluded products, variant boundary, destination pages, primary conversion, budget, dates, promotion, theme and app owners, fulfillment owner, creative owner, and review evidence.

Choose a stable merchant route

Start with a collection or product type whose inclusion rule the team can explain and maintain. Do not use “all products” if the catalog mixes categories, margins, stock, subscriptions, and customer promises. Record the source field, tag, or rule that determines membership.

Assign owners for product, collection, variant, price, discount, app, theme, checkout, feed, fulfillment, support, and corrections.

Define the accepted result

Choose a completed paid order or another approved business outcome. Record order identifier, currency, value, payment state, cancellation, refund, return, exchange, subscription, and support treatment. Keep product view, cart, checkout start, signup, and inquiry separate as diagnostics.

Step 2: Audit product, variant, and collection data

Google’s Performance Max overview is the current reference for campaign behavior and eligibility. Complete the catalog and page review before launch.

Verify product fields and variants

Review identifiers, titles, descriptions, brand, category, product type, variants, price, sale price, availability, images, final URL, shipping, taxes or fees as presented by the store, and returns. Sample every included collection and select available and unavailable variants.

Confirm that product page, collection page, feed, ad, variant selector, price, image, package contents, promotion, and availability agree. Make subscriptions, discount codes, exclusions, and bundle contents clear.

Record theme and app dependencies

List theme components and apps that change product pages, cart, discounts, subscriptions, shipping, consent, payment, or order confirmation. Assign an owner and test expectation for each dependency. A page load is not proof that the order event is correct.

Set stock and promotion controls

Document in-stock, low-stock, discontinued, preorder, bundle, subscription, sale, discount, return, and support states. Decide how a stale price, product, variant, or collection rule is corrected and who reviews it.

Step 3: Build product and asset groups

Product groups and asset groups should share one Shopify collection or product route and one relevant destination.

Create durable product groups

Use collection, product type, vendor, price, margin, season, stock, promotion, bundle, or another approved field when it changes the decision. Record field, values, owner, and review date. Do not rely on an informal tag that changes without campaign review.

Prepare Shopify-aligned assets

Collect approved headlines, descriptions, logos, product images, lifestyle imagery, video where available, and calls to action. Check mobile crops, variant accuracy, promotion dates, package contents, image rights, and final URLs.

Use collection assets for discovery and product assets for evaluation. Do not send a product-specific ad to a generic collection or advertise a discount that the Shopify checkout does not apply.

Review claims and discount language

Check product, material, performance, sustainability, delivery, discount, subscription, and return language against approved evidence. Shopify discount rules, exclusions, and dates should agree with the customer-facing ad and page.

Step 4: Configure Shopify conversion tracking

Use the current Google Ads conversion tracking guide with the merchant’s approved analytics and order records.

Verify the primary purchase

Confirm that a completed paid order fires once on the approved confirmation state with order identifier, currency, value, and consent behavior correct. Test successful and failed payment, confirmation reload, canceled order, refund, return, exchange, subscription, and support contact.

Do not count page view, cart, or checkout start as a purchase by convenience. If an interim signal is approved, record what it represents and how it will be reconciled.

Test the actual store path

Run a safe test for a product, a variant, a discount, a bundle, and a subscription route where relevant. Check product selection, price, cart, discount, shipping, payment, confirmation, analytics event, Shopify order record, cancellation, return, and support. Record data lag and limitations.

Step 5: Set budget and release controls

Review Google’s budget guidance, spend guidance, and, for an eligible finite promotion, total budget guidance. These describe platform mechanics, not a universal Shopify budget.

State the funding boundary

Record currency, dates, collections, products, variants, stock, promotion, theme, apps, checkout, fulfillment, support, primary conversion, value definition, returns, and owner. State evidence needed to increase, hold, correct, or pause.

Do not scale a route with a broken theme, stale feed, discount failure, unavailable variant, checkout problem, or insufficient fulfillment and support capacity.

Keep changes traceable

Document reason, expected evidence, measurement lag, and restoration condition for product, collection, variant, app, theme, feed, asset, budget, bid, page, or conversion changes. A coordinated release still needs a dated record.

Step 6: Complete the preflight review

Before publishing, check account eligibility, product diagnostics, asset approvals, product and variant data, collections, apps, theme, discounts, final URLs, prices, stock, shipping, checkout, payment, consent, returns, conversion diagnostics, and the safe order test.

Review the customer-facing promise

Open representative destinations and confirm collection, product, variant, price, discount, availability, shipping, checkout, order confirmation, returns, and claims agree. Obtain merchant approval for product and promotional language.

Save a launch baseline

Record launch date, catalog state, included products, assets, budget, primary conversion, apps, theme, tests, risks, owners, promotion dates, and first review questions. This makes future Shopify changes visible.

Review the launch by layer

Compare reach and clicks with product views, variant selection, carts, checkouts, paid orders, payment failures, cancellations, refunds, returns, exchanges, subscriptions, and approved value.

Diagnose before editing settings

Weak reach can reflect eligibility, coverage, assets, demand, or budget. Clicks without carts can reflect product, variant, price, image, collection, app, shipping, or page clarity. Carts without orders can reflect checkout, payment, discount, consent, support, delivery, or tracking.

Fix the layer supported by evidence. A budget change cannot repair a checkout script, and a new asset cannot make an unavailable variant available.

Re-test after store changes

Repeat mobile and desktop product-to-order tests after theme, app, catalog, collection, price, promotion, variant, checkout, payment, shipping, returns, consent, subscription, or analytics changes. Confirm product, variant, price, cart, confirmation, event, and order record align.

Common setup errors

Treating collections as permanent

Collection membership can change with products and tags. Record the rule, source, owner, and review date.

Ignoring app and theme dependencies

An app or theme update can change cart, subscription, consent, payment, or confirmation. Include these dependencies in testing.

Counting shallow events as orders

Views, carts, and checkouts diagnose the route. Reconcile a completed paid order with Shopify records.

Advertising stale discounts or variants

Check price, code, exclusion, availability, and actual variant selection before scaling.

Shopify-store setup checklist

Before launch, confirm that:

  • collections, products, variants, pages, apps, theme, dates, budget, conversion, and owners are documented;
  • product identifiers, prices, discounts, images, availability, shipping, checkout, and returns agree;
  • product and asset groups use relevant, approved ecommerce imagery and claims;
  • the order event and diagnostic stages are tested against Shopify records;
  • feed, theme, app, fulfillment, privacy, promotion, support, and return constraints are approved; and
  • the merchant approves product, technical, customer, consumer, payment, and spending decisions.

Practical next steps

Choose one stable collection, audit variants and app dependencies, test one order end to end, prepare matching assets, and record the Shopify baseline. adz.so can review Google Ads structure, conversion definitions, reporting, feed alignment, landing-page alignment, and campaign overlap. It does not provide Shopify, legal, financial, technical, consumer, or product-safety advice.