Overview of Google Ads Product Feeds
Google Ads product feeds allow merchants to synchronise their product catalogue directly with Google's advertising platform. This integration enables dynamic product ads, Shopping campaigns, and Performance Max campaigns to pull live product data including pricing, availability, and custom attributes. Unlike marketplace feeds that push inventory to sales channels, Google Ads feeds power your own paid advertising campaigns, ensuring that ad copy, landing pages, and product information stay in sync with your current catalogue.
Merchants use Google Ads feeds to automate campaign management at scale. Rather than manually uploading product lists or maintaining static ad copy, your feed updates automatically whenever you modify prices, stock levels, or product attributes in your source system. This reduces manual work and ensures ads always reflect current product state, which directly impacts approval rates and campaign performance.
Feed Configuration and Destination Setup
When you configure a Google Ads destination in your feed management platform, you are establishing the connection between your product data source and Google's advertising systems. The destination type qualifier determines how Google Ads interprets and uses your feed data. Different qualifier settings allow you to segment feeds by geography, product type, or campaign intent, so you can run multiple feeds to the same Google Ads account with different rules or product selections.
The feed configuration page URL is the technical endpoint where your feed is hosted or processed. Google Ads periodically fetches this URL to retrieve your latest product data. This URL must be stable, publicly accessible, and return data in a format Google Ads expects (typically XML or CSV). If the URL becomes unavailable or returns malformed data, Google Ads will stop updating your product information, and your ads may disappear or show outdated details.
When setting up your destination, verify that:
- The feed URL is correct and remains stable over time.
- Your firewall or CDN does not block Google's IP ranges from fetching the feed.
- The feed returns data within Google's size and timeout limits.
- Your feed includes all mandatory fields for your campaign type (Shopping campaigns require more fields than Performance Max, for example).
Page URL Field Mapping
The page URL (often called 'link' or 'url' in feed specifications) is the landing page where a user arrives after clicking your ad. This field is critical for both user experience and policy compliance. Google Ads validates that the page URL is reachable and that the product on that page matches the product details in your feed (title, price, image, and description).
If your page URL is broken, blocked by robots.txt, or redirects to a generic category page instead of the specific product, Google Ads may disapprove your ad or reduce its visibility. The URL must also use HTTPS on live sites; HTTP-only URLs are flagged as security risks and may be rejected outright.
Common page URL issues include:
- Using a placeholder URL (such as 'example.com/products') instead of the actual product landing page.
- Redirecting users to a login page or age-verification page before showing the product.
- Linking to a product page that has since been deleted or moved without a redirect.
- Using URL parameters that expire or become invalid over time.
Map your page URL field carefully. If your product data system stores product URLs in a field called 'product_link' or 'canonical_url', ensure your feed template correctly references that field and does not accidentally insert a category URL or homepage link instead.
Custom Labels and Segmentation
Custom labels in Google Ads allow you to tag products with arbitrary metadata that you can then use for bidding, exclusions, or performance analysis. Unlike standard product attributes (brand, category, colour), custom labels are defined by you and can represent anything: margin tier, seasonal status, promotional eligibility, supplier, or internal product ID.
You can define up to four custom label fields (custom_label_0, custom_label_1, custom_label_2, custom_label_3) per product. Each label can contain any text string. Common uses include:
- Marking products as 'high_margin' or 'low_margin' so you can adjust bids accordingly.
- Tagging seasonal items as 'winter' or 'summer' to pause or boost them at certain times.
- Labelling products as 'new_launch' or 'clearance' to apply different promotional strategies.
- Assigning products to internal teams or suppliers for reporting.
When you populate custom labels, ensure consistency in naming and casing. If you label some products 'High Margin' and others 'high_margin', Google Ads treats these as two different values, which breaks your segmentation logic. Define a naming convention before you populate the feed, and document it so that anyone updating the feed follows the same rules.
Custom labels do not affect product approval directly, but they enable you to build more sophisticated bidding strategies and performance tracking. A product with a missing or empty custom label is still valid; the label is optional unless you have configured bid rules that depend on it.
Type and Qualifier Fields
The 'type' field describes the product category or classification. In some feed systems, this corresponds to Google's 'product_type' field, which you populate with your own internal category hierarchy (for example, 'Clothing > Mens > Shirts > Casual Shirts'). This is different from Google's 'google_product_category', which uses Google's standardised taxonomy.
The 'qualifier' field is a destination-level setting that modifies how Google Ads interprets your entire feed or a subset of products. Qualifiers allow you to:
- Target specific countries or regions with different product lists.
- Separate feeds for different campaign types (Shopping vs. Performance Max).
- Apply different approval policies or attribute requirements to different product groups.
When you set a destination type qualifier, you are telling Google Ads 'this feed applies to [specific context]'. For example, you might create one feed with qualifier 'country: UK' and another with qualifier 'country: US', so each region receives region-appropriate pricing and availability data.
Qualifiers are configured at the destination level, not in individual product records. Ensure that your destination qualifier matches the actual scope of your feed. If your feed contains only UK products but your qualifier says 'worldwide', Google Ads may attempt to show those products in non-UK campaigns, leading to targeting errors or disapprovals.
Currency Configuration
The Google Ads currency setting determines how Google Ads interprets all prices in your feed. You must specify a single currency per feed destination. If your feed contains prices in GBP but your currency setting is EUR, Google Ads will either reject the feed or apply incorrect currency conversion, causing price mismatches and ads to be disapproved.
When you configure the destination, select the currency that matches your product prices. If you operate in multiple currencies, create separate feeds for each currency zone, each with its own destination and currency setting.
Common currency configuration errors:
- Setting currency to GBP when prices are in EUR, causing a 27% price difference (approximately).
- Mixing currencies in a single feed (some products in GBP, others in EUR) without separate destinations.
- Forgetting to update the currency setting after changing your base business currency.
- Using a currency code that Google Ads does not recognise (for example, 'British Pounds' instead of 'GBP').
Always verify that your price field in the feed contains values in the same currency as your destination currency setting. If you need to support multiple currencies, the correct approach is to create multiple feed destinations, each with its own currency, rather than trying to mix currencies in a single feed.
Practical Feed Optimisation Tips
Before you deploy a Google Ads feed, validate it against Google's requirements. Use Google Merchant Centre (if applicable) or Google Ads' feed validation tools to check for errors before the feed goes live. Common validation failures include:
- Missing required fields (such as title, description, or image_link for Shopping campaigns).
- Malformed URLs or invalid currency codes.
- Price or availability values that do not match expected formats.
- Duplicate product IDs, which cause Google Ads to reject one or both records.
After your feed is live, monitor the feed status dashboard in Google Ads. This dashboard shows how many products were successfully ingested, how many were disapproved, and why. If you see a spike in disapprovals after a feed update, check whether you changed the page URL structure, removed required fields, or introduced invalid data.
Test your page URLs regularly. Click through a sample of ads and verify that the landing page loads, displays the correct product, and matches the ad copy. A broken landing page will cause Google Ads to pause your ads or lower their visibility.
Use custom labels strategically but sparingly. Do not create a custom label for every possible attribute; instead, reserve labels for attributes that directly affect your bidding or campaign logic. Too many labels make your feed harder to maintain and can slow down feed processing.
If you run multiple feeds to the same Google Ads account, ensure that each feed has a distinct destination and does not overlap with other feeds in terms of product IDs or target audience. Overlapping feeds can cause duplicate ads and bidding conflicts.
Summary
Google Ads product feeds are the foundation of dynamic advertising campaigns. The feed configuration page URL, custom labels, type and qualifier settings, and currency configuration work together to ensure that your products appear in the right place, at the right price, to the right audience. Proper feed setup reduces disapprovals, improves campaign performance, and automates product data management at scale. Validate your feed before deployment, monitor it regularly, and keep your page URLs and product data in sync with your live catalogue.