Stape Shopify Plugin checkout extensibility

I have a client using ‘checkout extensibility’ in Shopify which means that the normal checkout script can’t be placed but instead ‘customer events’ needs to be used. The pixel is sandboxed so can’t be tested with the normal GTM preview mode.

I’m using the Stape Server GTM Shopify plugin, on the second tab ‘datalayer’ there is an option to check the use of ‘checkout extensibility’ and a script that needs to be copied into the pixel.

Testing the purchase event, does not show the ‘purchase’ event in console tab in the dev tools. I do see all kinds of other events such as ‘checkout_started’ and ‘checkout_contact_info_submitted’.

Questions:

  • Is the console tab the right tab to look at?
  • Is the script in the plugin enough or should I add additional parts?

I would recommend checking how your events work just based on network requests.
That is, you need to configure the events you need based on the data layer:https://help.stape.io/hc/en-us/articles/13693436542877-Shopify-App-dataLayer
Publish these changes and see if network requests go out with your events.

This works really well, not sure why I didn’t see it in the first place. It would be helpful if you could guide a bit how to test sandboxed pixels, I’ve found my way with the dev console, but I can imagine there are easier ways.

We’ve got a little description of that here: How to use the stape app for setting up Shopify server-side tagging
Unfortunately the easiest way is to look at network requests.

Hello, @Alex
I am struggling with a similar issue.

I have watched one of your webinars where Dan thoroughly goes through each step of the process.

I have now also checked the network tab as you show on your guide and it seems to be picked-up.

However, I am not receiving any information on my server container

I have double checked the begin checkout tag on my web container and verified that the ga4 event name (begin_checkout) and event trigger (begin_checkout_stape) are correct.

Hi @Jogvan_Simonsen

Your screenshot does not show where this request is sent. I think it is not sent to your server container, but directly to GA.
This may be due to implementation problems or if you have for example also active GA integration in plugins and it also sends additional events and overwrites the configuration in your GTM container.

1 Like