"Confirmation #XXX was generated for this order." - not tracked in GA

[colinhall]

I have this open as a ticket with Shopify Support, but figured I'd keep a record of the issue here to a) see if anyone from the community has any thoughts and b) hopefully post any resolution from the Shopify side for anyone else facing this same issue.

The issue is that some orders aren't showing up in Google Analytics correctly, because our GA4 purchase event isn't firing properly (they come through as Transaction ID: not set). I looked into the orders which are affected, and the thing they have in common is a message in the order timeline saying "Confirmation #XXXX was generated for this order."

I can see the revenue tracked in GA4, but not as part of the purchase event, and it's missing all the additional data such as Order Name, items, etc. The checkout page is also tracked as:

https://domain.com/checkouts/co/xxx/thank_you

rather than the usual:

https://domain.com/xxx/checkouts/xxx/thank_you

Will update as I hear more, but would love to know if anyone has any ideas?

[onescales]

did you setup your own tracking or use the Shopify google channel to track orders in Google Analytics 4?

[TrackingMore_]

Hi @colinhall 

Thanks for your question. I would like to provide some ideas and hope to help you find the root cause of the problem as soon as possible.

The GA4 purchase events you mentioned were not triggered correctly, some orders were not fully displayed, and the URL format of the Thank You page was different. This may be one of the core problems. Usually, GA4 purchase events are triggered according to specific URLs. If the Thank You page URLs of some orders do not match expectations, GA4 may not be able to capture the purchase information correctly. You can check whether there are any third-party plugins or custom codes in Shopify that have changed the URL structure of the Thank You page to ensure that GA4 triggers can cover all possible page URLs.

At the same time, the problem of GA4 cannot be completely ruled out. This may require checking the specific trigger settings or codes. You can ask more professional people.

I hope this can help you.