We have developers build our store while we just realized that it has two GA tracking codes firing (our GA code and extra tracking code).
The extra one is "UA-116858069-1", and it may come from Shopify payment while I cannot figure out how to remove it.
There are several tracked pages have it:
Did anyone face this before and know how to resolve it? Thanks so much!!!
Solved! Go to the solution
Hi, @resphichen !
Katy here from Shopify. I hope all is well with you, and welcome to our Community here.
Thanks so much for providing as much context as you have, this is super helpful.
I understand that you are using Shopify Payments. Do you have Google Pay Dynamic checkout linked with this by any chance? On stores that have Google Pay dynamic checkout enabled, this will then display an extra Analytics tag on the pages with the Google Pay button - which seems to be in line with the tracked pages you have listed. To date this has been appearing as UA-116858069-1 (though this may change in future).
If you do have Google Pay enabled this is likely the cause, in which case this tag is contained within the Google Pay checkout button's iframe and will not affect any tracking on your store.
Do have check in with your developers to see. If you need a hand or have any questions feel free to let me know.
Hi, @Janko1 !
Thanks for joining in here.
I'm sorry to hear that this is proving problematic for you/ your client. This property is not created by Shopify, but rather by Google Pay when offered as a payment method.
Google Pay creates a button on the cart or checkout page that customers can click to pay with their Google account. The button itself is served in an iframe, and the Google Analytics code is then firing from that iframe. If you look at the individual pageview requests in Google Tag Assistant, this should show that pay.google.com is the tracked page, with a referrer of checkout.shopify.com. You may in this case like to chat with their own team directly for further help on this.
I hope this helps to clarify for you.
|3 hours ago|
|6 hours ago|