---
type: feature
title: "Google Shopping Ads Builder for Ecommerce"
description: "Build Google Shopping ads from verified Merchant Center and store inputs, review product partitions and budget, then approve an explicit publish action."
category: ai-marketing
h1: "Build Google Shopping Ads From Verified Product Data"
image: "https://storage.googleapis.com/download/storage/v1/b/runner-blog/o/features%2Fgoogle-shopping-ads-builder%2Fhero.png?generation=1789430874573004&alt=media"
keyword: "google shopping ads"
legacyKind: structured
---

**Google Shopping ads** in Runner AI start with a connected Google Ads account, Merchant Center identifiers, approved store facts, locations, budget, bidding strategy, and product-group rules. Runner turns those inputs into a validated Standard Shopping campaign draft that you can inspect before an explicit publish action. The differentiator is a reviewable, project-scoped handoff rather than an unverified promise to optimize ad performance.

![Product cards flowing into a structured Shopping campaign review board with a human approval checkpoint](https://storage.googleapis.com/download/storage/v1/b/runner-blog/o/features%2Fgoogle-shopping-ads-builder%2Fhero.png?generation=1789430874573004&alt=media)

## Build Google Shopping ads from connected account facts

Shopping campaigns do not use the same input shape as text-based Search campaigns. Start by identifying the exact Google Ads account connected to the Runner project and the Google Merchant Center account that owns the product feed. Supply the numeric Merchant Center merchant ID, the feed label, target country codes, campaign name, daily budget, and supported bidding strategy. These are operational inputs, not details Runner should infer from a brand name or a product image.

Runner's project-scoped action resolves the Google Ads account selected for the current workspace instead of trusting an account identifier supplied in generated text. Before publishing, the Shopping draft is parsed against the campaign schema and sent through campaign validation. A missing Merchant Center ID, invalid feed label, unsupported location, malformed product partition, or incomplete required campaign field should remain a visible problem to correct, not be silently replaced with a plausible-looking value.

The product feed remains authoritative for the product details Google uses to assemble Shopping ads. Confirm titles, descriptions, image links, prices, availability, condition, destinations, and policy status in Merchant Center. Runner can structure the campaign around the identifiers and product-group controls you provide, but it does not prove that every feed item is approved, current, or eligible to serve. If the broader account or campaign workflow is still unclear, compare the [Google Ads campaign builder](/google-ads-campaign-builder) before moving to this Shopping-specific configuration.

## Separate product partitions from Search campaign keywords

A Standard Shopping campaign groups products rather than building keyword-and-copy ad groups. Runner's Shopping campaign contract allows ad groups without Search keywords or text ads. Instead, each ad group can carry product partitions that define which feed items belong in a bidding group. That distinction prevents a Search campaign template from being reused where Google expects Merchant Center product data.

Build partitions from facts present in the feed. Supported dimensions include brand, Google product category, item ID, condition, product type, channel exclusivity, and custom labels. A partition with no dimensions can serve as the catch-all for all other products. Review parent and child relationships, duplicate paths, excluded groups, and bid values together so the final tree represents the merchandising decision you intend. Do not invent a brand, category ID, or custom label just to complete the shape.

Product grouping is also where business context matters. A merchant may separate high-margin products, seasonal inventory, house brands, or a specific category, but those are choices that require verified catalog and financial evidence. Runner can make the proposed tree reviewable; it cannot decide that a segment deserves more spend or guarantee that a grouping will improve return on ad spend. For feed fields and destinations that need correction before campaign work, the [ecommerce product feed optimization workflow](/ai-ecommerce-product-feed-optimization) owns that adjacent task.

## Review budget, bidding, locations, and feed scope together

Review the campaign as one connected decision. Confirm that the campaign name identifies the intended store and market, the daily budget is within the approved spending boundary, and the bidding strategy is supported for the draft. Check every location as an ISO country code and compare it with the feed label, shipping coverage, storefront availability, currency, and the countries approved in Merchant Center. A structurally valid campaign can still be commercially wrong when these facts disagree.

Then inspect the product partitions against the actual feed. Verify that included item IDs exist, brand and product-type values use the feed's exact spelling, category values are valid, custom labels mean what the reviewer expects, and the catch-all behavior is deliberate. An empty partition list may cause the adapter to use a catch-all, so absence is not a neutral choice. Record whether the campaign should cover the whole eligible feed or only named groups before anyone authorizes the external change.

Keep measurement readiness separate from draft validity. Conversion actions, consent, attribution settings, and reporting windows can affect later interpretation, but they do not prove that the campaign configuration is correct today. The [Google Ads conversion tracking workflow](/google-ads-conversion-tracking) explains how eligible storefront purchase context and delivery status can be reviewed without claiming that one reporting source proves causation. For this page, the reviewable output ends at the validated Shopping campaign configuration and explicit publication decision.

## Approve an explicit Shopping campaign publish action

Publishing changes an external advertising account and can spend money, so a generated draft is never sufficient authorization. The responsible operator should compare the resolved Google Ads account, Merchant Center ID, feed label, campaign name, locations, budget, bidding strategy, ad groups, product partitions, exclusions, and landing destinations. Resolve provider access, billing, policy, feed, and validation errors before attempting publication.

Runner exposes a specific publish action for a connected Google Ads campaign. The action validates the persisted draft, binds it to the current project's selected account, and asks the Google Ads adapter to create the campaign. A returned external campaign ID is evidence that the create call produced a provider campaign reference; it is not evidence of impressions, clicks, sales, profitability, or a particular serving state. Reopen Google Ads to confirm the exact campaign, status, account, and settings after the action completes.

This boundary is useful when several people participate in campaign work. A merchandiser can verify feed scope, a marketer can review structure and budget, and an authorized account owner can approve publication without treating generated prose as permission. Preserve the draft and review notes when changes are requested. If you need to compare other Runner marketing and storefront capabilities before choosing the next task, browse the [Runner AI feature catalog](/).

> Help me prepare a Standard Google Shopping campaign draft. Use my connected Google Ads account, verified store and Merchant Center details, numeric merchant ID, feed label, ISO country locations, approved daily budget, bidding strategy, and exact product-partition dimensions; return a reviewable campaign configuration, validation issues, catch-all behavior, and a pre-publish checklist without publishing it.

[Build a reviewable Google Shopping ads draft in Runner AI](https://www.runnerai.com/auth/login?prompt=Help%20me%20prepare%20a%20Standard%20Google%20Shopping%20campaign%20draft.%20Use%20my%20connected%20Google%20Ads%20account%2C%20verified%20store%20and%20Merchant%20Center%20details%2C%20numeric%20merchant%20ID%2C%20feed%20label%2C%20ISO%20country%20locations%2C%20approved%20daily%20budget%2C%20bidding%20strategy%2C%20and%20exact%20product-partition%20dimensions%3B%20return%20a%20reviewable%20campaign%20configuration%2C%20validation%20issues%2C%20catch-all%20behavior%2C%20and%20a%20pre-publish%20checklist%20without%20publishing%20it.)

## Google Shopping ads FAQ

### What inputs does Runner AI need for a Shopping campaign draft?

Prepare the connected Google Ads account, verified store destination, numeric Google Merchant Center merchant ID, feed label, ISO country locations, campaign name, approved daily budget, and supported bidding strategy. If the campaign should cover only part of the feed, also provide exact product-partition dimensions and values from Merchant Center. Runner can validate and organize those inputs, but it should not infer missing account, feed, catalog, or spending facts.

### Does a Shopping campaign need keywords and text ads?

No. Runner's Standard Shopping campaign contract does not require the Search keywords or responsive text ads used by a Search campaign. Google matches eligible products using Merchant Center product data. The Shopping draft instead uses campaign settings and product partitions, which can group products by supported feed attributes such as brand, category, item ID, condition, product type, channel exclusivity, or custom labels.

### What happens when product partitions are empty?

An ad group with empty product partitions can fall back to a catch-all product group in the supported adapter path. Treat that as an explicit scope decision, not a harmless blank field. Confirm whether the campaign should include all eligible products in the selected feed or only named groups. If only part of the catalog belongs, add validated partitions and review exclusions, paths, values, and bids before publication.

### Does Runner AI publish Google Shopping ads automatically?

No automatic publication should be assumed. Runner can prepare and validate a Shopping campaign draft and exposes a supported publish action for the connected Google Ads account, but an authorized operator must approve that consequential step. After publication, verify the external campaign ID, account, campaign status, budget, locations, feed scope, and product groups in Google Ads. A created campaign does not guarantee delivery or business results.