A space to discuss online store customization, theme development, and Liquid templating.
@Shopify
While checking the standard events that shopify provides in the sandbox for webpixel, came across https://shopify.dev/api/pixels/customer-events#customer but not able to see customer object anywhere in the events that are received from pixel.
Another thing is in the entire user journey from added to cart, till checkout.
- In checkout_started event the order id is anyway null or undefined.
- if the user is logged in with phone number and email provided pre checkout events doesn't have `phone` .
Is an expected behaviour ?
Can someone clarify this ?
Hey @hireng - the customer object is something that should be able to be captured by a Web Pixel if it is configured correctly. Can you confirm if you've set up the event subscriptions for your Pixel as mentioned here in the docs? This should subscribe your pixel to all events emitted by Shopify.
If you've done this and the events still don't appear to be captured by the pixel, just reply back here and we'd be happy to take a deeper look into this with you. Hope this helps!
Developer Support @ Shopify
- Was this reply helpful? Click Like to let us know!
- Was your question answered? Mark it as an Accepted Solution
- To learn more visit Shopify.dev or the Shopify Web Design and Development Blog
Yes this is configured correctly, we subscribe to all the standard events that are described as per this documentation.
We are having the same issue as well. Can someone please look into this? Without having the shopify user ID in the clientside, it's not possible to link the serverside data with the client side events.
Do you have tag you can identify a user with? Client side if you track by cookie you can make a call during on either checkout-start and checkout_contact_info_submitted subscribed events. When either of those events happen I am making an event call back that includes the cookie (which our SDK adds) and the email and/or shopify id in the event. This then tells me the front end and client side are the same. Along with some additional functionality I am able to stitch the two paths together.