Google & YouTube App Product ID Sync Issue: SKU vs. 'shopify_zz' Format

Shopify Apps
, ,
1

Hey everyone,

I’m hoping to get some community insight into a persistent issue I’m having with my product feed sync to Google Merchant Center (GMC). I’m using two main apps: Simprosys for multi-platform feed management (Google, Facebook, etc.) and the official Google & YouTube app primarily for tag management and conversion tracking.

The problem is specifically with how Product IDs are being sent to GMC.

The Problem

GMC expects the Product ID for each item to be the product’s SKU, which is essential for matching data in my Google Ads campaigns. Instead, the Product IDs are showing up in a global, Shopify-generated format, like:

shopify_zz_8820779319523_46242936324323

This ID mismatch is causing significant problems with my Google Ads campaigns—products aren’t matching correctly, and campaign performance is suffering.

What I’ve Tried

I’ve already been in contact with Simprosys support, and they’ve confirmed that the feed being generated by their app is correctly sending the SKU as the Product ID. They’ve indicated the override/discrepancy is coming from the Google & YouTube app.

My Question

Is there a setting within the Google & YouTube app that allows me to modify the product sync settings so that the product’s SKU is definitively used as the Product ID in Google Merchant Center, instead of the default shopify_zz format?

It seems the Google & YouTube app is interfering with the ID structure, even though I’m using Simprosys as the main feed provider.

Any help or experience with this specific conflict would be hugely appreciated!

Thanks!

2

If you want tracking to match up, then I recommend going with my free code below, where you can choose to use the SKU value as the ID for both card data in conversion tracking and remarketing.

3

Hi **Tzadik_Barak - were you able to figure this out? I am running into the same issue.

Thanks in advance**

4

Hi @Tzadik_Barak , I’m also wondering if you ever found a solution to this as I’m facing the same issue.