Uploading and maintaining product data feeds for shopping campaigns
The public Microsoft Advertising Platform Health record does not currently confirm a new incident beginning November 4, 2026; keep case 7111297556 escalated and ask Support to route it to Shopping/Product Ads engineering as a possible recurrence of incident 5025.
Incident 5025 is a strong symptom match, but it cannot establish the cause of this new event. Microsoft recorded that incident as affecting a subset of EMEA offers across Shopping, PMax Retail, and feed-based MSAN campaigns from May 13 through May 21, 2026. It caused “No targeted products,” reduced impressions/clicks/spend, and was marked fixed after engineering corrected an internal issue and reprocessed affected offers ^1^.
Add this evidence to the open case
Since the feed, store, product groups, and campaign settings have already been checked, request a backend offer-targeting investigation, not another configuration review. Add:
- Exact impact window
- Last normal delivery: November 3, 2026.
- First abnormal delivery: approximately November 4 at 01:00 UTC.
- Before/after daily impressions, clicks, spend, and number of serving products.
- Affected object IDs — privately
- Account and customer IDs.
- Merchant Center store ID.
- Campaign and ad-group IDs for both existing campaigns.
- New test-campaign ID.
- Several representative offer IDs, including:
- Active offers that stopped serving.
- Offers in
custom_label_3 = 90. - Any one or two offers that still receive impressions.
- Reproduction evidence
- Screenshot of the new campaign showing Blocked – Targeting: No products targeted.
- Screenshot/export showing the same filtered offers as Active in Merchant Center.
- The test campaign’s product-group structure and filter.
- Feed-processing result and timestamp for the corresponding nightly upload.
- A precise engineering request
Please verify whether these Active France/EMEA offers are present and eligible in the Shopping campaign-targeting index. The issue began around 2026-11-04 01:00 UTC and reproduces in a newly created Standard Shopping campaign as “Blocked – Targeting: No products targeted.” Please compare the backend state with incident 5025 and check whether offer reprocessing or reindexing is required.
- Scope comparison
- Whether both existing campaigns fail on the same offers.
- Whether the new campaign targets zero products even though its label filter matches 428 Active offers.
- Whether other stores, markets, or campaign types in the account are unaffected.
Current conclusion
- Known historical issue: Yes—incident 5025 documents this behavior for a subset of EMEA product offers.
- Confirmed November 4 recurrence: Not from the current public Platform Health feed.
- Most appropriate next action: Shopping engineering must compare Merchant Center approval state with the campaign-targeting/indexing state for the affected offers.
Do not post account, store, campaign, or offer identifiers publicly; provide them only through the private support case or a moderator’s private-message channel.
References