Steve S. this hasn’t actually worked for us consistently. Here’s an overview of the issues I’m running into and trying to solve:
I’m using /pages/ for various landing pages that we’re testing. Each landing page has one specific product, sometimes with different offers.
On those pages, I would expect a Added to Cart event to be sent to Klaviyo when someone clicks on one of our purchasing options with the relevant data.
I followed the steps on the article you set above, and while the Added to cart event shows up on Klaviyo, the payload doesn’t have any data, which prevents the flows we have from sending emails that are product specific. See screenshot below.
A few things we do that I want to callout in case that’s causing a problem:
We use permalinks that take you directly to checkout.
I have tested using the “Add to cart” interaction and haven’t seen it work either.
On a related topic, I’m also looking to validate that the current pages I have do work “out of the box” with Meta as shared on this article. I tried to setup Omega Pixel and they literally kicked me off their app saying they can’t have us as a customer because “our pages have “Add to Cart” buttons that block tracking”. I tried to get more details from their support on what that meant, but they wouldn’t give me any detail.
To summarize, my goals:
- 1.
Figure out how to get the proper payload sent to Klaviyo when someone adds a product to cart.
- 2.
Make sure our pages are correctly setup to send back data to our Meta pixels and ensure we can optimize our ads properly!
