PixelYourSite

@georgcantor the trigger you have a problem with is part of the paid plugin and we are not allowed to offer support for it here.

We got your request and we try to understand what happens. Please follow the emails from our support. Since we don’t see the problem with Fluent forms on other sites, we asked for an example of such a form where we can replicate the issue. Once we have it, we will take a proper look and fixit it.

There are multiple ways to track conversions for Google Analytics, including by using a Google Ads destination ID (or tag ID). If such an ID is used (supported by our paid add-on), it’s possible to configure conversions the way it’s explained on the linked page: create a conversion inside Google Ads, add the conversion label to a PixelYourSite event.

It’s also possible to track/share conversions from Google Analytics.

We get those values when possible, including when the pixel tag is blocked. Sending them when there is no user consent is not permitted.

We also don’t support URL tracking for fbb or fbc.

We don’t see a quick fix for this situation with the current code.

However, this is not an urgent matter, because it only affects AddToCart value parameter. Since AddToCart are never the final conversion, tracking this event value is not relevant. It’s actually not recommended, because it can lead to misleading data (ads will show the sum of all add to cart actions as conversion). The correct event that must send value is the Purhcase event, and this one works fine with Staggs.

So, while it is an incovenient, it’s not a major issue and will not have an impact on the way ads are tracked.

The second event is NOT ours. It’s probably related to an option from your Meta Events Manager, Settings, called automated events without code. You need to turn it OFF. More details here: https://www.youtube.com/watch?v=4eMKGxT7qMk

It can also be related to something called Events Setup Tool, also a Meta setting. Make sure no events are configured there as well.

You can easily recognise our events by the high number of parameters. We also have a parameter with the plugins name.

@angeliti

Emails are also supported for both URL parameters and forms (for forms we usually detect them automatically).

Chances are that you saw a video that I recorded before this particular features was added.

I am not aware of any significant issue with Litespeed, or any other popular cache solution.

It’s a good idea to describe the actual problem that you have and send a link where we can replicate it. You mentioned Referrers, do you mean the data we track as events parameters, or the data some of the scripts track (like Google Analytics).

As for tutorials about using caches, you can direct the request to the cache plugin itself since this is the factor that modifies the behaviour of other plugins.

@tmsn10 I had no email from them. They should send us a message on our site directly the contact page and mention this conversation. I will close this for now.

Yes, there is, but it’s part of our paid solution. Send me a message on our site, and mention this discussion, please.

Each event is sent using both tag and API. The same is true for the Purhcase event. So the answer is that pair of tag/API events tracks the same action and is sent in the same time. In this case, it tracks purchases.

There is a separate feature that sends API events for orders that were never tracked by the usual tag/API purhcase event when such order status is changed to completed. It’s called Advanced Purhcase Tracking, controlled on the plugin’s WooCommerce page.

The free plugin takes the prices as they are on the site, taxes included (if that’s the case). The paid plugin has additional options and you include or exclude taxes or shipping cost.

Unfortunately I don’t know what to suggest here. We take the prices from WooCommerce, so if they use the correct WooCommerce hooks, filters, and prices, it should be fine. If you can share a site with this problem, we can tae a look.

Yes, their first tier support is not aware of the problem. You can easily demonstrate that it’s pixel related by installing a different pixel ID and show them that that event is no longer present.

In fact, that’s the only solution I know about.

By the way, you never share the URL here, so I am simply guessing this is the cause of the problem. You can share it, and I will take a look, just to be sure it’s not something else.

I don’t’ have an answer for that. It might be a one time error with a very particular reason. Do you still see it reported? Is there anything else on the site that can send API events? Another plugin?

That extra event with very little parameters is not ours. I expect it’s browser only, right? My suspicion is still the “fire events without code” option. You can confirm this by replacing the pixel ID and repeating the test.

Other possible sources for such events: Meta event setup tool, GTM, custom code, another plugin, events manually configured on our plugin’s Events page (unlikely, we add some parameters to those as well).