Google Ads guide

Set Up Google Ads Ad Assets for Growing Online Stores

Set up Google Ads ad assets for an online store by defining one product, collection, variant, bundle, gift, subscription, sale, or information route and reconciling catalog, feed, page, cart, checkout, shipping, and event data. The setup should keep the shopper’s expectation consistent from the asset through fulfillment.

Start with Google’s responsive search ads guidance and review Google Ads policy requirements. Product attributes, prices, inventory, images, offers, and delivery conditions are customer-facing claims and should be checked as a connected system.

Define the route and meaningful outcome

Choose the final URL for product, collection, variant, bundle, gift, subscription, sale, or education intent. Record identifier, title, options, image, quantity, specifications, price, stock, shipping market, returns, offer terms, and support.

Name the useful event: purchase, subscription start, qualified inquiry, or completed catalog interaction. A click or product view is useful diagnostic data but does not prove commercial success.

Keep product and service facts visible

Review size, color, material, ingredients, dimensions, quantity, compatibility, warranty, shipping, returns, and support. Keep a collection promise separate from a specific product fact.

Prepare the catalog and asset brief

Build complete product fields

Prepare fields for product, collection, category, variant, identifier, title, options, dimensions, materials, ingredients, quantity, price, sale, stock, shipping, returns, subscription, bundle, and support. Write full factual copy first and shorten it without deleting a condition that affects the decision.

Define terms such as “best,” “premium,” “limited,” “free shipping,” “sustainable,” and “sale.” Record source, product version, market, reviewer, approval date, expiry, and replacement path.

Map images to the exact item

Use actual product, package, variant, scale, material, included-item, and use images. Map each image to product and variant identifier. A collection scene should not imply that every visible product or accessory comes with one order.

Compare image, title, identifier, price, stock, URL, feed, page, cart, and checkout. Recheck when a product, package, option, or promotion changes.

Record change ownership

Keep a register of source system, product or variant, price and inventory timestamp, promotion end, shipping promise, reviewer, market, approval date, and replacement action. Assign owners who can pause or update assets when the catalog or fulfillment data changes.

Configure the campaign and catalog scope

Open the intended campaign or ad group and confirm asset type, final URL, display path, product or feed connection, market, language, policy status, combinations, and conversion action. Keep product, collection, variant, bundle, gift, subscription, and promotion routes separate when their pages or terms differ.

Synchronize catalog, page, and checkout

Compare the brief with catalog source, feed, rendered page, inventory, cart, and checkout. Confirm identifier, variant, image, price, currency, stock, sale end, shipping, returns, bundle, and renewal terms. Test that the selected option remains in the cart and that the event carries correct product, quantity, and value.

Do not assume that one catalog update changes every asset combination. Preview available variants, inspect final URLs, and resolve differences before enabling the route.

Connect assets to the store journey

Use the online-store conversion-tracking guide for product, variant, cart, checkout, purchase, refund, return, subscription, cancellation, support, and reorder events. Use the online-store location-targeting guide when shipping, currency, language, pickup, availability, or market differs.

Keep product view, option selection, cart, checkout, purchase, refund, return, subscription, cancellation, support, and repeat order distinct. Do not send names, addresses, payment details, customer notes, private profile information, or order identifiers in ad parameters.

Test before enabling the route

Read each preview as a shopper who has not opened the store. Check product, variant, image, price, stock, offer, shipping, returns, destination, and bundle or renewal terms. Follow the URL through option choice, cart, checkout, delivery, return, and support on mobile and desktop.

Choose one first question, such as whether a concrete attribute message improves qualified purchases or whether transparent shipping reduces abandonment. Keep product, price, stock, page, market, device context, and offer comparable. Record asset version, hypothesis, date, event, and review condition.

Catch common online-store setup errors

Assuming the feed is current

Compare catalog, feed, page, cart, and checkout for title, image, price, stock, URL, and variant. A successful connection can still publish stale information.

Mixing collection and product routes

Use a collection destination for comparison and a product destination for a specific item or variant. Do not let a generic image imply product-level attributes.

Hiding offer conditions

Show code, minimum spend, bundle, subscription, customer, date, market, shipping, and final-sale conditions. Remove assets when offer or inventory conditions change.

Losing variant identity in analytics

Test size, color, quantity, bundle, and subscription through checkout. Confirm the event carries the selected product, variant, quantity, currency, and value.

Selecting a shallow event

If value depends on fulfillment, low returns, repeat order, or renewal, include those outcomes in review. Do not optimize solely to clicks or first-order count.

Verify the live setup

Before enabling the route, inspect combinations, URLs, paths, product mapping, market, language, policy status, conversion action, and page metadata. Test product, variant, price, offer, cart, checkout, shipping, return, subscription, and support. Confirm one correct event with the right product, quantity, currency, and value and no private data.

Record final assets, catalog and feed versions, reviewer, approval date, inventory state, offer expiry, renewal terms, and replacement owner. Recheck after a product, variant, price, stock, feed, page, promotion, delivery, policy, or checkout change.

Online-store setup checklist

Before considering the setup complete, confirm:

  • the route and meaningful purchase or subscription outcome are explicit;
  • product, identifier, variant, image, price, inventory, URL, cart, checkout, and page agree;
  • product, offer, shipping, returns, warranty, and service claims have evidence and owners;
  • catalog, feed, page, cart, checkout, and event values have been tested;
  • private customer and order information is excluded from campaign fields; and
  • purchase, refund, return, subscription, cancellation, support, and repeat-order events are measured without private data.

adz.so can review Google Ads structure, asset organization, conversion tracking, location settings, and reporting. The online store remains responsible for catalog truth, product claims, pricing, inventory, fulfillment, integrations, returns, and customer communication.