gavinohanlon

Thank you so much for taking the time to leave a review.

Really glad we were able to help get the pixel issue sorted for you in the end. I know those kinds of tracking issues can be frustrating to troubleshoot, so happy to hear everything is now working properly.

We also really appreciate the kind words about support, it means a lot to our small team.

All the best.

Hi Valdeo,

Thanks for the update. It’s good to hear the redirect test passed, that rules out most global server issues.

The fact that about 7% of Purchase events are affected is quite specific. That usually suggests the issue isn’t happening across the entire site, but rather at the final step of the checkout flow.

To help narrow this down, could you check a few things:

First, try testing the Purchase step directly. Sometimes the WooCommerce checkout process, or a custom checkout plugin, handles URL parameters differently than the homepage. Also, if you have a “Thank You” or “Order Received” page, try also loading that type of URL with a capitalized parameter, for example:
yourdomain.com/checkout/order-received/123/?TestParam=ABC
and see if the parameter stays capitalized or gets changed.

Another thing to check is whether you have the option enabled in Pixel Cat to exclude Administrators or Shop Managers from tracking. If that setting is enabled, it’s possible the ~7% represents internal testing or staff orders. If the fbclid parameter is being stripped or altered for logged-in users, that could explain a small and consistent percentage like this.

Also, does the Meta warning mention only the Purchase event, or do you see the same warning for events like Add to Cart or Initiate Checkout? If it’s only happening on Purchase, that would usually point to something happening during the redirect to the payment gateway or when the user returns to the site after payment.

Next, did you build a custom purchase event in Pixel Cat or are you using the “WooCommerce Events for Facebook Pixel” toggle to automatically send the events?

Lastly, if roughly 7% of your orders come through a specific payment method such as PayPal or another external gateway like an instagram shop, that could also be a clue, as those gateways sometimes handle redirects differently.

Let me know what you find and we can take it from there.

All the best.

Hi Andrea, I hope you are doing well.

I just wanted to follow up on this thread.

Since we last spoke, we’ve made a number of updates to Pixel Cat, including some changes around how tracking scripts interact with other pixels.

Could you let me know if you’re still experiencing this issue when the TikTok Pixel is present on your site?

If it’s still happening, feel free to send over the page URL again and I can take another look. If it’s no longer occurring, that would also be helpful to know so we can confirm whether one of the recent updates resolved it.

All the best.

Thanks so much for the kind feedback, glad you’re enjoying Easy Pricing Tables.

Hi Michela,

Thank you for setting up that staging site.

I’ve taken a look at the console, and I’ve see a few things that could be causing this behavior on your landing pages.

While it appears that deactivating Pixel Cat “resolves” the issue, the underlying cause might actually be a conflict with how your site’s JavaScript is being optimized and cached. I noticed in your site’s source code that you are running both Autoptimize and W3 Total Cache.

When multiple optimization tools try to “minify” or “aggregate” scripts from different plugins, they can sometimes create a “Syntax Error” (which I can see in your browser console). This prevents other scripts, like your Thrive Architect dropdowns, from loading correctly. This is what I see in the console for your staging site – https://pasteboard.co/S1yyDPBA9a8n.png

To help us narrow this down, could you please try the following troubleshooting steps on your staging site?

1. Clear All Caches: Please clear the cache in both W3 Total Cache and Autoptimize.
2. Follow the Autoptimize Troubleshooting Guide: The developers of Autoptimize have a specific guide on what to do when their optimization breaks a site feature. I highly recommend following these steps to see if it resolves the form issue: Autoptimize Troubleshooting Guide
3. Exclude Pixel Cat: If disabling the optimization helps, you can try adding pixel-cat to the exclusion list in your Autoptimize settings.

Eliminating these possibilities first will help us see if there is a genuine code conflict we need to dig into further. Let me know what you find.

All the best.

• This reply was modified 4 months ago by gavinohanlon.

Hi Michela,

Thank you for reaching out. I’m sorry to hear you’re running into a snag with your landing page forms.

To help us investigate this properly and see if there is a genuine script conflict, I need to clarify a few details regarding your setup:

• License Status: Are you using Pixel Cat Free or our Premium version?

• Thrive Setup: Is Thrive Architect is a premium paid plugin?

• The Specific Error: “Issue with the contact form” can mean a few things. Does the form fail to send, does the page layout break, or does the Pixel Cat tracking simply not show up?

• Thrive’s Feedback: Did the Thrive support team provide any specific technical notes, such as a JavaScript error or a console log? This would save us a lot of time in “guessing” what they found.

Once we know exactly what the specific error is, we can investigate.

Best regards.

Hi Davy,

Thanks for checking.

I don’t think that will cause any problems with sending Mailchimp campaigns. Maybe test it with my email and see what happens. So for example make a campaign where only my email meets the criteria and see if I receive it?

As long as the contact appears in your audience and is marked as subscribed, Mailchimp should treat it like any other subscriber when you send campaigns.

From what you’ve confirmed, the signup and double opt-in process is working correctly now, and new subscribers should continue to be added as expected.

If you notice that people are no longer receiving the Mailchimp confirmation email at all, that would be something to check directly inside Mailchimp (audience settings, double opt-in, or account sending limits), as Optin Cat doesn’t control that part of the flow.

All the best.

Hi Espressivo,

Thanks for reaching out.

I haven’t heard of this happening before. My recommendation would be to try deactivating your plugins one by one and then testing again to see if the issue persists. This can help identify if there’s a conflict causing the timeout.

If you have any plugins for cookie consent, it’s a good idea to start with those, as they sometimes interfere with requests to third-party services like Facebook, and then move on to the others.

Let me know what you find after testing, and we can look further if needed.

All the best.