[Customer Events] Many problems with the Custom Pixels

[JohannesOaklund]

Hello,

I've been setting up the Custom Pixel and I've run into quite some extensive amount of errors and usage problems.
I'll list them one by one below and I hope someone have found any fix to these problems.

Google Tag Manager Preview Mode don't work
You can't debug the Shopify Client-side Tracking using the Google Tag Manager Preview Mode. It does not load. Either you have to use the Facebook Test Event or check the GTM Server-side preview mode.

Facebook Pixel sending Sandbox URL
The "dl"-parameter in the Facebook request is sending the Sandbox URL. This can't be override in any Meta Tag settings.

Facebook Pixel register referrer URL instead of DL
When checking the Meta Test Event tool the URL that is being registered is the referrer URL.
My guess here is that Meta does identify the sandbox URL as a strange URL and fallbacks to the referrer URL.
So for example, when the dl=https://www.example.com/wpm@123/custom/web-pixel-123@321/sandbox/modern/sv/products/t-shirt the Meta Test Event tools shows https://www.example.com/sv/?utm_source=debug which is the "rl"-parameter

Two different behaviors — Normal vs. Incognito
When running Normal (Shopify logged in) and debugging the network request it does not mirrors how it works when running logged out in Incognito. Even if I clear all the cookies in Normal mode and runs exactly the same procedures, the tracking does not work as expected in Normal.

Event trigger behavior on Non-Shopify+ Checkout
The event "checkout_shipping_info_submitted" is being triggered whenever you edit the payment options. Shouldn't it be triggered when all the Shipping info is added — As the name of the event says?

Last words
I'm well aware that many of these issues stem from the functionality of Meta, GA4, and other tracking systems. However, these systems have been operating smoothly for years. So, wouldn’t it make more sense to create a tracking solution that integrates seamlessly with them, rather than developing a custom pixel that clearly doesn’t work well with the existing setup? The sandbox pixel is a total hassle and could have been avoided while maintaining good security measures as well.

[WizzCommerce_Co]

Hi @JohannesOaklund , thank you for posting here!

You've identified some valid frustrations with Shopify's Custom Pixel and its integration with tracking systems like Google Tag Manager and Facebook Pixel. Here's a breakdown of your points and some potential solutions:

1. Google Tag Manager Preview Mode not working:

• This is a known issue with Shopify's Custom Pixel. You can't fully debug client-side tracking in GTM Preview.
• Workarounds:
  • Use Facebook Pixel Helper Chrome extension to test Facebook Pixel events.
  • Use GTM Server-side container preview for server-side tracking (if applicable).

2. Facebook Pixel sending Sandbox URL:

• The "dl" parameter (destination URL) might include the Shopify sandbox URL by default.
• No current workaround: You can't override this through Meta Tag settings.
• Recommendation: Consider reaching out to Shopify support to see if there's a planned solution or if it's expected behavior.

3. Facebook Pixel registering referrer URL instead of DL:

• This might be due to Facebook identifying the sandbox URL as unusual and falling back to the referrer URL.
• Workaround: Use Facebook Pixel Helper to test if actual events are firing with the correct URL when published.

4. Different behavior in Normal vs. Incognito mode:

• Logged-in and logged-out sessions might trigger events differently.
• Troubleshooting:
  • Clear browser cache and cookies completely in normal mode.
  • Ensure you're testing the published version of your store, not the development version.
  • Check for any browser extensions that might interfere with tracking.

5. "checkout_shipping_info_submitted" event trigger:

• This event might trigger on editing payment options as well as adding shipping information.
• Possible explanation: Shopify considers changing payment details part of the checkout process.
• Workaround: Depending on your need, you could create a custom event in GTM that only fires when specific shipping information is added.

Last Words:

• While it's true that established tracking systems exist, Shopify's Custom Pixel offers more control over data and potentially improved security.
• The sandbox environment does add complexity, but it might be a trade-off for increased security.

Alternatives:

• Depending on your needs, consider using the built-in Shopify analytics or third-party apps that integrate with existing tracking systems.

Overall, Shopify's Custom Pixel presents some challenges. However, by understanding the limitations and using workarounds, you can still achieve your tracking goals.

If my answer is helpful, please mark us as a Solution and give a Like !!!