Microsoft Ads for Ecommerce: Shopping Campaigns, Product Ads, and ROAS Strategy

Most ecommerce brands concentrate their paid search budget entirely on Google. This is rational — Google dominates search volume and Google Shopping is the default product advertising channel for most online retailers. But concentrating 100% of ecommerce paid search on Google leaves meaningful revenue untapped.

Microsoft Product Ads — the equivalent of Google Shopping — generates incremental ecommerce revenue at CPCs consistently 25-40% lower than Google Shopping. For brands with optimized Google Shopping feeds, launching Microsoft Product Ads requires minimal incremental effort and typically adds 15-25% to total paid search revenue within 60-90 days. This guide covers everything needed to build a high-performing Microsoft ecommerce paid search program: Merchant Center setup, feed optimization, campaign structure, dynamic remarketing, Performance Max, and ROAS benchmarks by category.

Microsoft Product Ads: How They Work and How They Differ from Google Shopping

Microsoft Product Ads are visual product listing ads that appear in Bing search results when users search for products. They display an image, product title, price, brand/store name, and sometimes a promotional message — the same format as Google Shopping.

Key structural differences from Google Shopping:

Lower competition: Fewer ecommerce brands run Microsoft Shopping campaigns compared to Google Shopping. This directly translates to lower CPCs — typically 25-40% below equivalent Google Shopping CPCs. The same product advertised on both platforms will almost always cost less per click on Microsoft.

Audience demographics: Microsoft's ecommerce audience skews older (35-64), higher-income, and desktop-heavy compared to Google. For mid-to-high ticket products where the buyer profile aligns with this demographic, Microsoft Shopping often matches or exceeds Google Shopping conversion rates. For low-ticket, mass-market consumer goods targeting younger buyers, the volume difference is more apparent.

Feed format compatibility: Microsoft Product Ads use the same data specification as Google Shopping. If you have an optimized Google Shopping feed, it uploads to Microsoft Merchant Center with little to no modification. The attribute names, required fields, and file formats are designed to be compatible.

ROAS benchmarks: Microsoft Shopping typically delivers 70-90% of Google Shopping ROAS on an absolute basis, with CPCs 25-40% lower. The net result is that cost per acquisition is often comparable to or better than Google Shopping, with lower volume but strong economics per dollar spent.

Microsoft Merchant Center: Step-by-Step Setup

Microsoft Merchant Center is the feed management system that connects your product catalog to Microsoft Product Ad campaigns. It's the Microsoft equivalent of Google Merchant Center. Setup process:

Step 1: Create a Microsoft Merchant Center account

Navigate to ads.microsoft.com and sign in with a Microsoft account. In the left navigation, find "Microsoft Merchant Center" (or access it through Tools in the Microsoft Ads interface). Click "Create store."

Step 2: Configure your store details

Enter your store name (typically your brand/website name), store URL (your primary domain), and select the country your products ship from. This determines which market your catalog is available in. Separate stores are needed for separate countries with different currencies and product catalogs.

Step 3: Verify and claim your domain

Microsoft requires domain verification to confirm you control the website associated with your product catalog. Two verification methods:

• Meta tag: Add a Microsoft-provided meta tag to the head section of your homepage
• DNS record: Add a CNAME or TXT record to your domain's DNS settings

After adding the verification element, return to Merchant Center and click Verify. DNS propagation can take up to 24 hours; meta tag verification is typically immediate.

Step 4: Create a catalog and upload your product feed

In Microsoft Merchant Center, create a product catalog. Then configure a feed:

• Feed file format: XML (RSS 2.0 format), CSV, or TSV
• Upload method: Direct file upload, scheduled URL fetch (Microsoft pulls from a hosted URL on your schedule), or API integration (for large catalogs with frequent updates)

If you use an ecommerce platform with a built-in Google Shopping feed, the same feed typically works for Microsoft. Shopify, WooCommerce, BigCommerce, and Magento all have feed export options compatible with Microsoft Merchant Center.

Step 5: Wait for feed review and approval

Microsoft reviews product feeds for policy compliance and data quality. Initial review typically takes 3-5 business days. Common rejection reasons: missing required attributes (title, description, price, availability, image URL, product URL), policy violations (prohibited products, misleading claims), or broken image URLs. Monitor feed status in the Merchant Center diagnostics tab.

Step 6: Link Merchant Center to Microsoft Ads and create campaigns

Once the feed is approved, link your Merchant Center store to your Microsoft Ads account through the account linking settings. Then create Shopping campaigns in Microsoft Ads that reference product groups from your catalog.

Product Feed Optimization for Microsoft Shopping

Feed quality is the primary driver of Microsoft Product Ad performance. The algorithm uses product attributes to match ads to relevant search queries, determine CPCs in the auction, and rank ads within the shopping carousel. Optimizing these attributes directly improves traffic quality, impression share, and CPCs.

Product Titles (most important attribute):

Titles are the primary matching signal for shopping queries. The algorithm reads titles to understand what product is being advertised and matches it to relevant searches.

Best practice title structure: Brand + Product Type + Key Differentiating Attributes + Variations

Examples:

• Strong: "Patagonia Better Sweater Men's Fleece Jacket Navy Large"

• Weak: "Men's Jacket"

• Strong: "Vitamix 5200 Blender Professional Grade 7-Year Warranty"

• Weak: "High-Speed Blender"

Front-load the most important terms. Microsoft reads the first 70-80 characters most heavily. Include the brand name, primary product category, and the most important variation attributes (size, color, material) in the first 70 characters.

Product Descriptions:

Descriptions are less critical for matching than titles but still contribute to relevance signals. Write 150-300 character descriptions that include: key product features, materials or composition, use cases, and secondary search terms not in the title. Avoid keyword stuffing — write for the user.

GTINs (Global Trade Item Numbers):

For branded products, including UPCs, EANs, ISBNs, or MPNs significantly improves matching accuracy. Microsoft uses GTINs to identify products definitively and can serve your ad for broader search variations when a GTIN match confirms the product identity. Missing GTINs for branded products is one of the most common and impactful feed optimization opportunities for brands with established product catalogs.

Product Images:

Images directly impact click-through rate in the shopping carousel. Requirements: 220x220 pixels minimum (1000x1000+ recommended), no promotional overlays, product on white or transparent background for consistency. Categories like apparel allow lifestyle images showing the product worn/used and typically see higher CTRs with lifestyle images versus flat-lay on white.

Availability and Price accuracy:

Mismatches between feed prices/availability and landing page prices/availability trigger disapprovals and harm feed health scores. Ensure feed updates are frequent enough to reflect inventory and price changes. Automated feed pulls (scheduled URL fetch) updated every 24 hours prevent staleness issues.

Custom Labels (0-4) for campaign segmentation:

Custom labels are free-form fields you define to enable campaign-level segmentation. Use them to segment your catalog by:

• Margin tier: High margin, medium margin, low margin — enabling differentiated ROAS targets by profitability
• Performance tier: Best-sellers, mid-performers, long-tail — enabling differentiated bidding by velocity
• Seasonality: Current season, off-season, year-round — enabling budget reallocation by time period
• Promotion status: On sale, full price, clearance — enabling promotion-specific campaigns

Custom label segmentation allows you to bid differently on your highest-margin, best-selling products versus your full catalog — a critical efficiency lever at scale.

Product Category and Product Type:

Include both Google Product Category (the structured taxonomy) and Product Type (your own category hierarchy). Microsoft accepts both attributes and uses them as additional matching signals. Product Type can include your own categorization structure (e.g., "Clothing > Men's > Jackets > Fleece") and Microsoft interprets this as additional context about the product.

Shopping Campaign Structure for Ecommerce

Option 1: Category-based structure

Create separate campaigns or ad groups for each major product category. This allows category-level budget control and enables different ROAS targets per category based on margin differences. A retailer selling electronics and apparel might structure: Electronics Search Campaign + Apparel Shopping Campaign, each with its own budget and target ROAS.

Option 2: Performance-tiered structure

Segment products by custom label performance tier. Best-sellers and hero SKUs in a high-budget, aggressive ROAS target campaign. Long-tail and new products in a low-spend exploration campaign with a higher ROAS tolerance. This concentrates budget on proven performers while maintaining discovery for the catalog's long tail.

Option 3: Brand vs. category segmentation

Separate campaigns for branded searches (users searching for your specific brand + product) versus category searches (users searching the product category without your brand). Branded shopping campaigns typically convert at higher rates and should have higher ROAS targets. Category campaigns discover new customers and should have more volume-oriented ROAS targets.

Most ecommerce advertisers use a combination of these approaches. The key principle: campaign structure should reflect how you think about budget allocation and ROAS targets, not just the convenience of keeping everything together.

Smart Shopping vs. Manual Shopping Campaigns

Microsoft Ads offers both automated and manual shopping campaign configurations:

Manual Shopping Campaigns: You set bids manually at the product group level (by category, brand, custom label, or individual product). You control which products get budget through bid adjustments and product group inclusions/exclusions. Best for: advertisers with experienced in-house paid search management who want granular control, accounts with strong conversion data that can inform manual bid decisions, and accounts where automated bidding is underperforming due to insufficient conversion volume.

Smart Shopping Campaigns: Microsoft's automated shopping campaign type that uses Target ROAS bidding with algorithm-driven bid optimization across all product groups. The algorithm allocates bids and budget across your catalog based on conversion probability prediction. Best for: accounts with 25+ monthly conversions from Shopping campaigns, advertisers who want to minimize time investment in manual bid management, and accounts where automated bidding has proven to outperform manual bids based on historical tests.

Transition path: Most ecommerce advertisers start with manual Shopping campaigns to establish conversion history and understand which product segments perform well. After 4-8 weeks with sufficient conversions, transition to Target ROAS or Smart Shopping with the historical data as the algorithm's foundation.

Performance Max for Ecommerce in Microsoft Ads

Microsoft Performance Max (PMax) for ecommerce is an automated campaign type that allocates budget across shopping, search, and audience network placements using AI optimization. When a Shopping feed is attached, PMax automatically serves product listing ads in shopping results as part of its cross-placement strategy.

How Microsoft PMax for ecommerce works:

You create asset groups — sets of text headlines, descriptions, images, optional video, and audience signals (customer lists, LinkedIn profiles, in-market audiences). Microsoft's algorithm determines which asset combinations to show to which users at which placements to maximize conversion value at your Target ROAS.

When to use Microsoft PMax for ecommerce:

• After establishing at least 25 monthly conversions from shopping and/or search campaigns in Microsoft Ads
• When you want to expand reach beyond standard shopping placements without managing multiple campaign types manually
• When performance on standard Shopping campaigns has plateaued and you want algorithmic exploration of new demand

When not to use Microsoft PMax for ecommerce:

• In new Microsoft Ads accounts with insufficient conversion history (algorithm performs poorly without data)
• When you need granular control over which products get budget (PMax limits manual product-level exclusions)
• When you need to accurately attribute performance to specific placements for decision-making (PMax's placement reporting is limited)

PMax and standard Shopping coexistence: You can run both PMax and standard Shopping campaigns simultaneously. Microsoft gives PMax priority over standard Shopping for the same products if they overlap. To maintain some manual control, consider using PMax for your top-performing product categories where the algorithm has strong conversion signals, while maintaining standard Shopping campaigns for newer or smaller product categories where you want more hands-on management.

Dynamic Remarketing Setup for Ecommerce

Dynamic remarketing shows ecommerce site visitors ads featuring the specific products they viewed or added to cart — personalized product ads served to high-intent retargeting audiences. This is consistently one of the highest-ROAS advertising formats for ecommerce.

Step 1: UET Tag with ecommerce event parameters

The base UET tag must be enhanced with product-level event parameters for dynamic remarketing to work. The UET tag should fire with the following custom events on key pages:

Product Detail Pages: event type "product", product ID (matching the product ID in your Microsoft Merchant Center feed), product price, currency

Add to Cart events: event type "addtocart", product ID, quantity, price

Purchase confirmation pages: event type "purchase", total revenue, currency, order ID, and line-item product IDs

These event parameters allow Microsoft to know which specific products each user viewed, added to cart, and purchased — enabling personalized product ads in remarketing campaigns.

Step 2: Define audience segments

In Microsoft Ads, create audience lists based on UET events:

• Product Viewers: Users who fired the product detail page event in the last 30 days
• Cart Abandoners: Users who fired the add-to-cart event but NOT the purchase event in the last 14 days
• Past Purchasers: Users who fired the purchase event in the last 180 days (for cross-sell and repeat purchase campaigns)

Cart abandoners are the highest-value segment — they expressed purchase intent but did not complete. ROAS for well-structured cart abandoner campaigns typically exceeds overall Shopping ROAS by 2-4x.

Step 3: Associate feed with remarketing campaigns

Create Audience Network or Shopping campaigns targeting your remarketing audiences, and associate your Microsoft Merchant Center feed. With the feed associated and UET product events firing, Microsoft can automatically match the products a user viewed to the product listing ads they see in remarketing.

Step 4: Creative and bidding for dynamic remarketing

Remarketing campaigns should bid more aggressively than prospecting campaigns — these users already know your brand and showed purchase intent. Increase ROAS targets slightly (you can afford lower ROAS targets because the conversion rate is higher, or set higher ROAS targets because conversion probability is higher). Test both approaches and measure actual ROAS rather than assuming.

ROAS Benchmarks for Microsoft Shopping

Setting realistic ROAS expectations for Microsoft Shopping helps evaluate performance and set appropriate Target ROAS values for automated bidding:

Overall Microsoft Shopping ROAS benchmark: Typically 3-5x for mid-market ecommerce brands with well-optimized feeds and campaigns. Highly optimized accounts with strong feed quality and mature audiences can achieve 6-8x. New accounts in the first 60 days often see lower ROAS as algorithms calibrate.

Category-specific patterns:

• Apparel and footwear: Typically 3-5x. High return rates can distort apparent ROAS if returns aren't excluded from conversion value.
• Electronics and technology: 4-7x. Price sensitivity is high; comparison shopping is common; strong products with competitive pricing and good titles perform well.
• Home and garden: 3-6x. Mid-to-high ticket items perform particularly well given Microsoft's older, homeowner-skewed audience.
• Health and beauty: 3-5x. Branded searches perform well; category searches are more competitive.
• Sports and outdoors: 3-5x. Desktop research behavior common for high-consideration outdoor gear purchases aligns with Bing's desktop-heavy audience.
• Automotive parts and accessories: 4-7x. Very strong category for Microsoft given the demographic match with vehicle-owning homeowners.

Microsoft Shopping vs. Google Shopping ROAS comparison: Microsoft Shopping ROAS will typically be 70-90% of Google Shopping ROAS in absolute terms, while CPCs are 25-40% lower. For example: Google Shopping delivering 6x ROAS, Microsoft Shopping might deliver 4.5-5.5x ROAS — but at significantly lower CPCs, making Microsoft's cost per acquisition competitive or better.

The key measurement is not ROAS in isolation but cost per revenue dollar generated (the inverse of ROAS). If Microsoft generates $1 of revenue for $0.22 in ad spend (ROAS 4.5x) versus Google generating $1 for $0.17 in ad spend (ROAS 6x), Google is more efficient per dollar of revenue. But Microsoft may still be worth running if total incremental revenue and the absolute return on Microsoft budget exceeds the opportunity cost of that spend.

Measuring Incrementality: Microsoft vs. Google

A common concern for ecommerce brands expanding to Microsoft: "Will Microsoft Ads just cannibalize Google Ads conversions, or is it truly incremental?"

The practical answer is that Microsoft Ads is largely incremental for most ecommerce brands, because: Bing search queries are separate events from Google searches (a user clicking your Microsoft Product Ad was not simultaneously being served your Google Shopping ad), and Microsoft's audience profile (desktop, older, corporate) overlaps partially but not entirely with Google's audience.

Methods to measure incrementality:

Geographic holdout test: Pause Microsoft Ads in specific geographic markets for 4-6 weeks while maintaining Google Ads. Compare revenue, sessions, and conversion rates in holdout vs. control markets. Revenue decline in holdout markets attributable to Microsoft Ads stoppage indicates incrementality. This is the most rigorous incrementality measurement method.

UTM-based attribution: Tag all Microsoft Ads with UTM parameters (utm_source=bing, utm_medium=cpc) and track conversions in Google Analytics 4 with data-driven attribution. GA4's data-driven model attempts to credit channels based on their incremental contribution to conversion probability, providing a more nuanced view than last-click attribution.

Platform comparison of unique order IDs: For direct measurement, compare order IDs attributed to Microsoft Ads versus order IDs attributed to Google Ads in your ecommerce analytics. Low overlap in order IDs indicates high incrementality. High overlap indicates potential double-counting in each platform's attribution.

Most ecommerce brands that run this analysis find Microsoft Ads is 70-85% incremental — meaning most Microsoft Ads conversions represent revenue that would not have occurred through Google Ads alone.

Budgeting for Ecommerce in Microsoft Ads

Minimum viable budget: $500/month. Below this level, Shopping campaign data accumulates too slowly for automated bidding to calibrate effectively, and impression share in most ecommerce categories will be extremely low.

Recommended starting budget: $800-1,500/month for brands launching Microsoft Product Ads for the first time. This provides enough volume to see Shopping campaign performance within 45-60 days of launch.

Scaling guidance: After establishing positive ROAS on Microsoft Shopping, scale budget by increasing the ROAS target slightly (lower ROAS target = more spend to capture more impression share) or by expanding product coverage (adding previously excluded product groups). Budget scale decisions should be driven by: is Microsoft ROAS above your target threshold? Is there impression share headroom to capture more volume at acceptable ROAS?

Budget allocation within Microsoft ecommerce campaigns:

• 70-75%: Shopping campaigns (direct product listing ads, highest intent)
• 15-20%: Dynamic remarketing (cart abandoners, product viewers — highest ROAS)
• 10%: Audience Network / Performance Max (top-of-funnel awareness and reach expansion)

Frequently Asked Questions

Does my existing Google Shopping feed work in Microsoft Merchant Center? Yes, with very few modifications in most cases. Microsoft Merchant Center accepts the same product data specification as Google Merchant Center — the same attributes, the same required fields, the same file formats (XML/RSS, CSV, TSV). The most common adjustment needed is updating image URLs if they use Google-specific query parameters that Microsoft's crawler handles differently. Most ecommerce platforms (Shopify, WooCommerce, BigCommerce) can export a single feed that works for both Google and Microsoft.

What ROAS should I target in Microsoft Shopping campaigns? Start with a Target ROAS 10-20% lower than your Google Shopping Target ROAS to allow the algorithm room to gather data and optimize. For example, if your Google Shopping Target ROAS is 500%, set Microsoft Shopping Target ROAS at 400-450% initially. After 30-45 days of conversion data accumulation, review actual ROAS and adjust the target to reflect the platform's performance characteristics. Many accounts see Microsoft Shopping converge toward 400-600% ROAS as campaigns mature.

How long does feed approval take in Microsoft Merchant Center? Initial feed review typically takes 3-5 business days. Re-reviews after fixes to disapproved items typically take 1-3 days. Common disapproval reasons: product policy violations, missing required attributes (GTIN for branded products, availability values must match the spec), broken image URLs, or price discrepancies between feed and landing page. The Microsoft Merchant Center diagnostics tab shows specific disapproval reasons per product.

Should I run Standard Shopping or Performance Max for Microsoft ecommerce? Start with Standard Shopping campaigns to build conversion history and understand product-level performance. After 6-8 weeks with 25+ monthly conversions from Shopping, test Performance Max alongside standard campaigns. Run both for 4-6 weeks, comparing ROAS and cost per acquisition. Many accounts find Standard Shopping outperforms PMax for established campaigns because the granular product-level bid control produces better efficiency than PMax's automation at the mid-scale budget level.

How do I handle product returns in ROAS calculation? Microsoft Ads conversion values reported in the interface reflect gross revenue (before returns). For accurate ROAS measurement accounting for return rates, use your analytics platform (GA4) or ecommerce backend where net revenue (after returns) is calculated. Set your Target ROAS with return rates in mind: if your return rate is 15% and your Target ROAS is 5x on gross revenue, your actual ROAS on net revenue is approximately 4.25x. Build this adjustment into ROAS targets and reporting.

Can I sell in multiple countries with Microsoft Shopping? Yes. Create a separate Microsoft Merchant Center store for each target country (with the appropriate country/currency configuration). Create separate Shopping campaigns in Microsoft Ads targeting each country. Maintain separate product feeds per country if pricing, availability, or language differs. Microsoft Shopping is available in the US, UK, Canada, Australia, France, Germany, India, and several other markets — coverage continues to expand.

What happens to my Microsoft Shopping campaigns if my feed goes offline? If your product feed becomes unavailable or errors out, Microsoft Ads will serve Shopping ads based on the last successfully processed feed data. Feed data expires after a set period, after which Shopping campaigns will stop serving. Monitor feed health daily in Microsoft Merchant Center diagnostics and set up feed status email alerts to catch issues before they cause extended downtime.

Is dynamic remarketing worth the UET implementation effort for mid-size ecommerce brands? For brands with sufficient traffic (2,000+ monthly product page views), dynamic remarketing is consistently worth the implementation effort. Cart abandoner campaigns on Microsoft Audience Network typically deliver ROAS 2-4x higher than standard prospecting campaigns because users already showed intent. The UET tag implementation for ecommerce events takes 2-4 hours for a competent developer and represents a one-time setup with ongoing high-ROAS returns.

Expand to Microsoft Shopping with Old Fox

Old Fox manages end-to-end Microsoft ecommerce paid search: Microsoft Merchant Center setup and verification, product feed optimization, Shopping campaign structure, dynamic remarketing implementation, and Performance Max testing — all integrated with Google Shopping management for a coordinated cross-platform strategy.

With 12+ years of paid search experience, Google Premier Partner Top 3% in their country status, and 130+ active accounts across ecommerce and B2B categories, we know how to make Microsoft Ads generate incremental revenue at favorable economics alongside Google Ads. Our average client achieves 4.5x ROAS across the portfolio, and ecommerce clients expanding to Microsoft Shopping typically see 15-25% incremental revenue growth within 90 days.

Our free 48-hour audit includes a Microsoft Shopping opportunity assessment: feed quality analysis, competitive CPC benchmarks for your product categories, and a budget allocation recommendation.

Get a free audit →