Hi
The Pixel Manager automatically sends all dynamic remarketing events, if it is able to detect them.
Also it depends how you’re validating this.
Please give us a way to replicate what you see so that we can confirm if it is bug, or explain how to validate the events.
Thanks for the reply.
I have checked it with google tag assistant and checking the real-time dashboard in google analytics. When I add an item to cart by using the add-to-cart button. No event is triggered. I see nothing in google analytics real-time dashboard. No tag hits are happening.
I have checked it with google tag assistant and checking the real-time dashboard in google analytics. When I add an item to cart by using the add-to-cart button. No event is triggered. I see nothing in google analytics real-time dashboard. No tag hits are happening.
Please send the shop URL so that we can double-check and narrow down the issue in your case.
Ok. I can confirm that the add-to-cart event is not processed.
It looks like a theme issue. But I can’t tell exactly where the issue is.
Let me explain:
1. The Pixel Manager triggers the add-to-cart event when the “ADD TO CART” button is clicked: https://cln.sh/yB3lg6bf
2. However. The event listeners added by the Pixel Manager and that send the event over to Google are not triggered. Here’s how it should look like: https://cln.sh/WnG16cRw
3. I ran the following snippet in the console of your page:
jQuery(document).on("pmw:event:add-to-cart", (event, product) => {
console.log("custom add-to-cart listener. Product added to cart: ", product);
})When triggered through the button it works: https://cln.sh/Tcs86cXZ
4. However, when adding that snippet to the end of the <body> tag in your page (and reload the page with an override to persist that code) then the button click trigger doesn’t work: https://cln.sh/hBq1gjgh
We have seen similar issues with themes that load jQuery more than once.
I haven’t found a second instance of jQuery in your theme.
There must be some code that loads after the page load event and removes/overrides/inhibits event listeners that have been set.
You need to fix that.
There is nothing we can do in the Pixel Manager to prevent or work around this.