Microsoft Shopping today converts at a CPC 24 to 38% lower than Google Shopping on verticals observed in public Google Ads benchmarks, with a ROAS often 15 to 30% higher on premium e-commerce (high average basket, 35-55 year-old audience). Microsoft Advertising holds 4% of desktop search internationally and 9% in the US in Q4 2025 (StatCounter) — modest volume, but ROAS margin that largely compensates.
Yet, the majority of US e-commerce merchants have never opened Bing Merchant Center. The main reason isn't unknown: it's the false idea that everything must be rebuilt. False. Direct import from Google Merchant saves 80% of setup. What distinguishes accounts that scale to $33k/month on Microsoft Shopping from those that plateau at $2.2k is feed optimization specifically Microsoft: titles, brand/mpn attributes, Microsoft category, exploitable custom labels. This guide unfolds the complete procedure. For the global Microsoft Ads strategy, read in parallel our Microsoft Ads vs Google Ads 2026 comparison.
Bing Merchant Center vs Google Merchant Center: key differences
Bing Merchant Center (officially renamed Microsoft Merchant Center since 2023) is the interface where you host and maintain the product feed that powers Microsoft Shopping — the strict equivalent of Google Merchant Center, but on the Microsoft ecosystem (Bing.com, Yahoo Search, AOL, Edge browser shopping panel, and certain MSN placements).
On paper, both tools serve the same objective: get a product feed validated by the advertising network to enable Shopping Ads delivery. In practice, six differences weigh on performance and setup.
Three differences are worth dwelling on. Attribute weighting: Microsoft Bing pushes brand and mpn higher in its intent matching than Google. On long-tail queries with explicit brand ("sennheiser hd 660s2"), a product without brand filled in clearly loses 30 to 45% of impressions vs a product with complete brand and mpn. On Google side, it's more the title that dominates. Country coverage: 19 countries is largely sufficient for 95% of US e-commerce merchants but blocking for those exporting to LATAM (excluding Brazil) or Africa. No CSS: Microsoft doesn't have the EU antitrust obligation to go through a third-party Comparison Shopping Service — you save operational complexity, but also lose the 20% CPC discount that exists on Google side.
To understand the Microsoft vs Google budget arbitrage on e-commerce, see our Microsoft Ads vs Google Ads ROAS analysis. Our free ROAS calculator computes gross ROAS + margin ROAS with vertical-specific interpretation.
On accounts observed in public benchmarks, a Microsoft feed with complete brand + mpn on 100% of the catalog shows an average CTR 22 to 34% higher than an identical feed but with empty brand. It's the #1 optimization to do before any other tuning. On Google, the same work yields 8 to 14% additional CTR — significant but less critical. Brand and mpn are neglected attributes on Google because they don't arbitrate anything; on Microsoft they decide your eligibility for 30% of long-tail impressions.
Bing Merchant feed setup: the 2026 procedure
The complete setup of a functional Microsoft Merchant Center wraps up in 5 to 7 days. Five mandatory steps, in this order. Skipping a step (often step 2 — domain verification) guarantees a feed disapproved 48h later.
Step 1 — Create the store in Microsoft Advertising
Log in to ui.ads.microsoft.com. Tools > Microsoft Merchant Center > Create store. Fill in brand name, default country, currency. If you manage multiple markets, create one store per country — Microsoft doesn't support multi-country on a single store, unlike Google Merchant.
Step 2 — Verify and claim the domain
Two methods to choose from. Meta tag: Microsoft provides a <meta name="msvalidate.01" content="..."> tag to paste in the site's <head>. Fast method, sometimes broken by CDNs. HTML file at the root: upload a BingSiteAuth.xml file at the domain root. More robust method, recommended for any site in production. Validation is instantaneous once the file is read by Microsoft. Note: if you've already connected the domain to Bing Webmaster Tools (the Search Console equivalent on Microsoft side), verification is inherited — appreciable time savings.
Step 3 — Link the Microsoft Advertising account
In Microsoft Merchant Center > Settings > Linked accounts, add your Microsoft Advertising account ID. Without this link, the feed exists but stays invisible on Shopping campaign side. With each Microsoft Advertising account addition (e.g.: sub-brand, additional market), you'll need to redo the step — linking isn't multi-account automatic.
Step 4 — Configure taxes, shipping, return policy
In Settings > Tax > define country and sales tax rules (in the US, configure by state or use destination-based defaults, modifiable based on your nexus status). In Shipping > define at least one delivery zone with cost and estimated delay — Microsoft refuses feeds without minimum shipping config. Return policy is required since 2024 (aligned with Google requirements): URL pointing to your return page, or short integrated text.
Step 5 — Submit the feed
Three options. Google Sheet: Microsoft provides a pre-formatted template, you paste your products in (up to 50k SKU for the Sheet option). XML or TSV feed in HTTPS: URL served from your server or e-commerce plugin. Import from Google Merchant Center: see section 3, it's the fastest path for an existing Google account. Once submitted, validation takes 24 to 72h. Follow the Diagnostics tab: any disapproved product is listed with reason (missing image, invalid GTIN, inconsistent price, stock at 0...).
For the complete launch sequence of Microsoft Ads account from scratch, see our Microsoft Ads 2026 beginner guide.
How to migrate a Google Merchant feed to Bing?
It's the royal road for 80% of e-commerce merchants who already have a functional Google Merchant Center. Microsoft has offered since 2022 an Import from Google Merchant Center option integrated into Microsoft Merchant Center, which automatically copies your validated Google feed to Bing in 24 to 48h.
Automatic sync procedure
In Microsoft Merchant Center > Catalog > Add catalog > Import from Google Merchant Center. You authorize Microsoft to read your Google Merchant via OAuth (read-only, no write). Select the target country (Microsoft creates a store per country). Microsoft then pulls your validated Google feed every 24h automatically.
What is synced: all standard Google Merchant attributes (id, title, description, link, image_link, availability, price, brand, gtin, mpn, google_product_category, product_type, custom_label_0 to 4). This covers 95% of the feed.
What isn't synced: Google-specific attributes (e.g.: Merchant Promotions promotions, Product Reviews ratings, certain Shopping Actions metadata). For this data, you must either recreate manually on Microsoft side (separate Promotions in Microsoft Merchant), or ignore them.
Import limits and work to do after
The import is fast but lazy. On referenced accounts, a feed simply imported from Google Merchant and left as-is performs 12 to 18% under a feed reworked specifically for Microsoft. Three minimum adjustments to do after import:
- Rewrite titles to exploit the first 35 Microsoft characters (instead of 40 on Google) with brand + model. Microsoft truncates earlier on certain MSN/Edge placements.
- Verify brand + mpn on 100% of the catalog. E-commerce merchants often leave these fields empty on Google because GTIN suffices; on Microsoft side, empty brand = -22% observed CTR.
- Re-map category to the Microsoft taxonomy. The taxonomy is very close to Google but diverges on certain branches (technology, beauty, sports apparel) — verify mappings on the official documentation help.ads.microsoft.com.
For the global Google ↔ Microsoft orchestration on an e-commerce account, see also our Google Shopping setup and optimization guide.
Feed optimization: Microsoft priority attributes
A healthy Microsoft feed yields 20 to 35% additional ROAS at iso-budget vs a minimal feed. The rule we repeat at every Shopping audit: healthy feed = healthy ROAS. No shortcut via bid strategies, no magic via Performance Max — feed quality amplifies or caps everything downstream. Here are the 10 attributes to master in this Microsoft priority order.
Three operational details. Title: Microsoft truncates earlier than Google on certain placements (Edge panel, MSN homepage). Optimal format: "[Brand] [Model] [Key Attribute]" in the first 35 characters, the rest as complement. Example: "Sennheiser HD 660S2 Wired Hi-Fi Audio Headphones" (first 35 = "Sennheiser HD 660S2 Wired Hi-Fi Aud"). On our Microsoft Shopping audits, titles with brand in the first 35 characters show CTR 22 to 34% higher than titles where the brand comes after.
Brand + MPN: the winning combination on Microsoft side. Empty brand breaks 22% of CTR. MPN absent when GTIN is present remains tolerable, but MPN absent when GTIN is also absent makes the product nearly invisible in long-tail. For private label brands without official GTIN, brand + mpn remain mandatory — leave identifier_exists=FALSE in parallel.
Custom labels: Bing Merchant supports the same 5 custom_labels as Google. Standard strategy we apply: custom_label_0 = margin tier (high/mid/low), custom_label_1 = seasonality, custom_label_2 = historical ROAS, custom_label_3 = best-seller boolean, custom_label_4 = free. This segmentation then conditions the structure of Microsoft Shopping campaigns (by margin tier, exactly like on Google side). See our 2026 Google Ads e-commerce playbook for the margin segmentation logic applied to both networks.
Microsoft Shopping vs Google Shopping: observed ROAS and CPC
The pragmatic question for the e-commerce merchant: "how much extra do I earn by activating Microsoft Shopping?". Orders of magnitude observed on 2025-2026 Google Ads benchmarks, at iso-feed and iso-bid strategy.
Two important readings. Microsoft ROAS outperforms Google on premium verticals (high-end fashion, tech, hi-fi, home deco). Structural reason: Bing/Edge demographics bias toward an older (35-55 years) and more affluent audience than Google. Higher average basket, lower cart abandonment rate, lower mobile conversion but stronger desktop conversion. The result: at CPC 25-35% lower, ROAS ends up 15-30% higher. For premium accounts, Microsoft Shopping is rarely a nice-to-have — it's a missing channel. Our average order value calculator gives the AOV with benchmarks by e-commerce vertical.
Microsoft ROAS is neutral or even unfavorable on fast fashion / Gen Z. Bing demographics poorly penetrate this target (15-30 years majority on Google and TikTok). On this vertical, Microsoft Shopping remains relevant for testing but doesn't deserve more than 5-10% of Shopping budget.
Volume remains 4 to 8× lower than Google. Don't project your Google volumes onto Microsoft. On an account doing 3,000 orders/month on Google Shopping, expecting 400 to 600 orders/month on Microsoft Shopping after ramp-up is realistic for a premium vertical; 200 to 300 on a less favorable vertical. It's a complement, not a replacement. For the complete budget perspective, see our Microsoft Ads worldwide budget and CPC analysis.
The ROAS gap observed between Microsoft and Google on premium isn't a demographic fluke alone — it's also because Microsoft Shopping competition remains undersaturated. On long-tail technical queries ("sennheiser hd 660s2 headphones"), Google Shopping pulls up 12 to 18 competitor results, Microsoft 4 to 8 on average. Less competition = more accessible position 1-3 = mechanically higher CTR. This undersaturation window progressively closes as the US market adopts Microsoft Ads — taking it now is an option with diminishing value.
For detailed Shopping vs Search arbitrage on Google side, also read our Shopping vs Search allocation guide — the logic transfers to Microsoft.
Microsoft Smart Shopping: when to activate it?
Microsoft Advertising renamed in 2025 its former Smart Shopping to Performance Max for Microsoft Advertising — nomenclature alignment with Google PMax, same principles: automated multi-inventory campaign (Bing search, Audience Network MSN, Edge shopping panel) with automatic bid strategy, asset groups, audience signals. The promise: extend reach beyond standard Microsoft Shopping.
The activation timing question is the same as on Google: too early = erratic learning, too late = volume left on the table. Our methodology in 3 cumulative conditions.
- Condition 1 — Clean feed. Microsoft Shopping Standard must run for at least 21 to 30 days, validated feed, zero disapproved on main SKUs, brand + mpn filled at 100%. Launching Performance Max on a dirty feed is guaranteeing 6 weeks of algo optimization in the wrong direction.
- Condition 2 — Sufficient conversion volume. Microsoft Performance Max requires 30 conversions / 30 days minimum on the account to exit a clean learning phase. Below this threshold, the algo explores without converging. On small accounts (less than $1,650/month on Microsoft), stay in Shopping Standard.
- Condition 3 — Stable attribution. UET tag installed, Enhanced Conversions activated, conversions reported consistently between Microsoft and internal analytics. See our UET conversion tracking guide for setup.
When the 3 conditions are met, the recommended switch sequence:
- Allocate 30 to 40% of Shopping budget to Microsoft Performance Max (no more for the first month).
- Keep Microsoft Shopping Standard at 60 to 70% to maintain granularity, query report and negatives.
- Activate Performance Max brand exclusions — otherwise PMax buys back your brand on Bing search like on Google side.
- Measure at 28 days the Microsoft brand Search cannibalization: if it exceeds 18 to 22%, adjust the PMax share downward.
- If positive performance after 28 days and controlled cannibalization, progressively scale to 50/50 or 60/40 PMax/Standard.
The recurring pitfall — observed in about 1 in 3 accounts referenced on Microsoft Performance Max — is the absence of brand exclusion list. Microsoft PMax bids on your brand Bing search, inflates its apparent ROAS (brand conversions are expensive in organic, so easy to buy back), and the global account CPA rises 12 to 22% in 30 days without anyone noticing. Activating brand exclusions is mandatory from launch.
Three typical scenarios where Microsoft Performance Max makes sense immediately after a mature Standard phase:
- Large catalog (1,000+ active SKUs) with a long tail difficult to manually sculpt by product group. Microsoft PMax exploits the feed and automates allocation per SKU better than a human can do beyond a certain volume.
- Rich LinkedIn audience (B2B account with defined ABM targets). The LinkedIn audience signal injected into a Microsoft PMax asset group clearly outperforms the same audience exploited in Standard — the PMax algo integrates the LinkedIn signal beyond simple targeting.
- Seasonal peak (Black Friday, sales, end of year). Microsoft PMax ramps faster than Standard on demand peaks, reacts to intent variations, and captures incremental volume that Standard would leave on the table due to slow bid adjustment.
Conversely, on small-volume Microsoft Shopping accounts (below $1,650/month), on catalogs below 100 SKUs, or on launch phases where the feed isn't yet stabilized, staying on Standard is almost always the right choice. Simple rule: Standard as long as you gain by controlling granularly, PMax as soon as volume exceeds your manual arbitrage capacity. For the Performance Max counterpart on Microsoft Ads in general, see our global Microsoft Ads vs Google Ads comparison.
For e-commerce accounts already mature on Google Shopping that want to extend toward Microsoft without blind audit, our free SteerAds audit verifies the quality of the existing Google feed, projects expected ROAS on Microsoft by vertical, and proposes a 30-day extension plan. For accounts that already have active Microsoft Shopping but suspect a performance ceiling, the audit identifies poorly optimized attributes (typically empty brand or wrongly mapped category) that silently weigh on ROAS.
Sources
Official sources consulted for this guide:
FAQ
Can the Google Merchant feed be reused as-is on Bing Merchant?
Technically yes via the "Import from Google Merchant Center" option available in the Microsoft Merchant Center UI, which automatically syncs your existing Google feed and pushes it to Bing in 24-48h. It's the fastest path to start. However, the feed isn't optimized for Microsoft: attribute priorities differ slightly (Microsoft weights brand and MPN attributes more, Google weights title and category more), and some Google title sculpting practices don't yield the same results on Bing. On accounts observed in public Google Ads benchmarks, a simply imported feed performs 12 to 18% under a feed reworked specifically for Bing.
What ROAS to expect on Microsoft Shopping vs Google Shopping?
The median gap observed on 2025-2026 Google Ads benchmarks: Microsoft Shopping shows a CPC 24 to 38% lower than Google Shopping for comparable products, and a ROAS often 15 to 30% higher on B2B verticals, premium fashion and premium services (older audience, higher average basket). On young verticals, fast fashion, or low-ticket products, the gap narrows or even reverses — Bing audience is less represented. Volume remains 3 to 6× lower than Google Shopping, so Microsoft Shopping doesn't replace Google Shopping: it complements, at very favorable marginal cost.
Should you activate Microsoft Smart Shopping (PMax equivalent) or stay on Standard?
Microsoft renamed Smart Shopping to Performance Max for Microsoft Advertising in 2025, aligning the nomenclature with Google. Our 2026 recommendation: start 100% in Shopping Standard for 30 to 45 days to accumulate signal, keep bid control, exclude unprofitable SKUs. Then switch 30-50% of budget to Microsoft Performance Max once the feed is clean and 30+ conversions accumulated. Going straight to Performance Max on a new feed is guaranteeing 6 weeks of erratic learning and an apparent ROAS inflated by brand. See also our Microsoft Ads beginner guide for the complete sequence.
Do custom_label attributes work in Bing Merchant Center?
Yes, Bing Merchant Center supports the 5 custom_labels (0 to 4) with exactly the same semantics as Google Merchant. You can reuse as-is the labels you already configured on Google side: margin, seasonality, historical ROAS, best-seller, clearance. It's one of the practical interests of the Google → Bing sync: your margin or seasonality segmentation logic is preserved and exploitable in Microsoft Shopping ad groups. Note, the Microsoft UI also offers an additional "product custom labels" attribute that has no Google equivalent — useful for Microsoft account-specific cuts without polluting Google.
What countries does Bing Merchant Center cover in 2026?
By end of Q1 2026, Bing Merchant Center distributes in 19 countries — covering most of Europe (FR, DE, UK, IT, ES, NL, BE), North America (US, CA, MX), Australia, India, Brazil and a few Asian markets (JP, TW, HK). It's about 3× narrower than Google Merchant coverage (60+ countries), but it covers 85%+ of the global e-commerce market for DTC brands that export. For US e-commerce merchants with international ambition, coverage is largely sufficient. Official documentation on Microsoft Advertising help center. No LATAM coverage outside Brazil or North Africa, to monitor if your catalog targets these zones.