Mariusz_M

I understand the technicalities of this. I just want to know whether you are going to fix it and whether your plugin has problems with Litespeed cache.

If you your solution is to exclude the cookie from cache, then give me the specific cookie filename to exclude.

I have no idea what you have just written. Does your plugin has a problem with Litespeed Cache? Because it is the first time I have used it. All other websites I have build use CookieYes and that one has no problem with cache at all.

This is set up using event manager standard events… So please do not tell me this is custom… In facet, you cannot set any events using your plugin because your plugin is not designed to set up events at all… Your plugin is there to set up pixel and it is designed to work with Meta event manager and it is the event manager where events are set.

Also, you have not responded to my questions. You claimed that you tested the setup with my pixel ID. How, if I have never given you my pixel IDs?

Events I think should have been reported? Are you implying I am imagining things?
I have shared some screenshots already.
Here are some facts:
1. Both the plugin and the pixel show they are connected and the connection is active. I have even tried to re-install the plugin and reconnect everyhing and nothing changes.
2. All test events work. By all, I mean all types, including Purchase. They are all reported as server events on the pixel side. So Conversions API works.
3. All events, whether activated by visitors on the website, or my test visits, or test events sent directly from the plugin do appear in the pixel. Mos of them as browser events + server events.
4. But for some reason purchase is the only one that is always reported only as browser event. All other events are reported both as browser events and server events. Looks like Purchase events are no longer sent by Conversions API.

So there is some kind of problem with the plugin. If there was a problem with Conversions API link, none of the server events would show on the pixel, but most do apart from Purchase. If there was a problem with Purchase event setup, then it would not appear at all, but it does, as a browser event only. So for some reason the plugin does not send a server Purchase event, only a browser Purchase event. But the same plugin is able to send a server Purchase event as a test event. So it is able to do it, but it just doesn’t do it. A bug?

I do not know if sharing mi pixel ID here is safe, but what is the point of sharing it, if the problem affects all pixels on all my client accounts and all my client websites? It is not isolated to one website and one pixel. All of them stopped working correctly with Purchase events in the last weeks in which you have pushed at least one update to this plugin. So perhaps this is the time you look at the code and search for a bug? My screenshots will not help you because the whole problem is that something is not reported, so it will not be visible on the screenshots.

Now a simple example from one of my websites. I have a “sign up” button on a landing page. When you press the button a popup opens, where you type your name, email, and press a “send” button. The “sign up” button is set as Initiate Checkout Event. The “send” button is set as Purchase Event. Now people come to the website press the first button, type in their details and sign up. On the pixel side I first get the Initiate Checkout Event and it is sent by the browser and by the server together. And shortly after, when they type in their details, I also get the Purchase Event, but it is ALWAYS sent ONLY as a browser event. So please test this kind of setup and tell me what is wrong. It used to work, then it stopped.

See the images here: https://imgur.com/a/MuSse1d
Page views and Leads show a contiinuous line. These are actual events from actual traffic.

With Purchases Conversions API stopped sending server events around 22nd June. Since then only browser events. The dots you see at the end are server test events type Purchase. So conversion API does work and can send events, just doesn’t do it for real purchases, but keeps doing it for other types of real events. A bug?

Dear Marija,

Firstly, I am talking about Meta pixel for Wordprss plugin, not for Woocommerce.

The parameters are chosen and set by the plugin. There is nothing I can set apart from ticking one box which is “Advanced Matching”.

My website is in the EU so obviously I have a cookies popup. But the whole idea of the plugin to integrate both Pixel and Conversions API is that even if someone does not accept cookies, the event will be sent by the server via Conversions API. And again, it is done automatically by your plugin. So why is the score so low?

Yes, I need assistance. I need specific answers, not general and only related to the actual plugin I am talking about.