Milos

Hi there,

Thank you for reaching out.

I understand your concern regarding the GET https://assets.elementor.com/mixpanel/v1/mixpanel.json requests being made on every page.

Since you are using Elementor 3.34.1, the issue mentioned in this thread has been resolved in this version. Elementor should no longer trigger Mixpanel requests if data sharing is disabled.

If you’re still seeing these requests, a few possibilities could be causing them:

1. Caching / CDN: Sometimes cached scripts from before the update continue to load, even after updating Elementor. Clear your site cache, browser cache, and any CDN cache (Cloudflare, etc.) and test again.
2. Plugins or theme integrations: Some third-party Elementor addons or themes may include legacy Elementor code that still references Mixpanel. Temporarily disable other plugins and switch to a default theme to isolate the source.
3. Staging / old script remnants: Check if your site is running old versions of Elementor JS/CSS from the /uploads/elementor folder or a child theme. Make sure all Elementor assets are fully updated.
4. Incorrect version or update issue: Confirm that Elementor is fully updated and that the update completed successfully.

Hope this helps.

Kind regards,

Hello there,

Thank you for your patience.

I attempted to replicate the issue on my test site using the latest version, but I wasn’t able to reproduce it.

Could you please share a few more details about what you’re seeing? If possible, please also provide a short screencast demonstrating the issue so I can follow the exact steps and try to reproduce it on my end. For reference, I’m testing on a clean WordPress installation with only Elementor and the Hello theme active.

This will help us better understand what’s happening and provide more accurate support.

Looking forward to your reply.

Kind regards,

Hi there,

Thank you for your message.

I understand your concern, the core of this issue is related to the internal behavior of the code itself, specifically around how custom-frontend.min.css is handled. Since this involves internal functionality and requires developer-level investigation, this case will need to be directed to our GitHub project, where our developers will be able to assist further.

Kindly note that our GitHub project is not a support channel; therefore, response times may vary. We appreciate your understanding.

I hope this helps. If I missed something, please reply if you have any further questions regarding this topic.

Kind regards,

• This reply was modified 4 months, 1 week ago by Milos.

Hi,

Thank you very much for the detailed feedback and for taking the time to thoroughly reproduce the issue. We truly appreciate the effort.

Since this behavior appears to be related to the internal functionality of a newer Elementor version, and may also be browser-specific, the best next step would be to report this directly to our developers so they can investigate it in more detail.

Please note that this would need to be directed to our official Elementor GitHub project, where our developers will be able to review the findings and assist further. Kindly note that our GitHub project is not a support channel, and response times may vary depending on the investigation and development priorities. We appreciate your understanding.

You can submit the report here:

• GitHub Issues: https://github.com/elementor/elementor/issues

Once reported, our development team will be able to analyze whether this behavior is expected, browser-related, or something that needs adjustment in relation to the Data Sharing settings.

Thank you again for bringing this to our attention and for sharing such clear reproduction steps.

Best regards,

• This reply was modified 4 months, 1 week ago by Milos.
• This reply was modified 4 months, 1 week ago by Milos.

Hi there,

Thanks for reaching out and for the detailed explanation.

In most cases, this type of CORS (Cross-Origin Resource Sharing) error is caused by a server-level configuration or a security rule (often from the hosting environment, a firewall, CDN, or security plugin) that blocks a request Elementor is making.

The update itself didn’t intentionally introduce a breaking change, but newer versions can trigger stricter server rules that were previously not enforced.

Here are a few things we recommend checking:

1. Hosting / Server security rules
2. Please ask your hosting provider to check if any ModSecurity, firewall, or CORS-related rules are blocking requests coming from /wp-json/ or Elementor-related endpoints.
3. Security plugins or CDN
4. If you’re using any security plugin, caching layer, or CDN (like Cloudflare), try temporarily disabling it to see if the error disappears. If it does, the issue is usually resolved by adding an exception/allow rule.

Looking forward to your reply.

Best regards,

Hello there,

Thank you for your patience and feedback.

Would it be possible for you to tell us more details about your issue, can you please provide us with a screencast demonstrating the issue?

This will be useful to us as we will better understand the issue you’re experiencing and provide you with better support.

I am looking forward to your reply!

Kind Regards,

Hello there,

Thank you for being so patient.

Elementor itself should not load api-eu.mixpanel.com by default, especially when Data Sharing is disabled.

In practice, Mixpanel requests are almost always coming from:
– another plugin (analytics, forms, marketing, automation, etc.),
– header/footer script injections,
– or the active theme/child theme.

The Data Sharing toggle in Elementor only controls usage data sent to Elementor, not third-party scripts added elsewhere on the site. To identify the source, I’d recommend:

– temporarily disabling plugins one by one and checking the network requests,
– checking if there is Custom Code and any header/footer script plugins.

Once the responsible plugin or snippet is identified, removing or disabling it should stop the Mixpanel requests.

Hope this helps.

Hi there,

Thanks for contacting us and hope you are doing well and having a great day.

To rule out the possibility of a plugin or theme conflict, please deactivate all your plugins (besides Elementor ). If it solves the issue reactivate them one by one to find the culprit. If it didn’t help, switch your theme (temporarily) to a default WP theme such as Twenty Nineteen and see if it makes any difference.

Also, this could happen due to our Elementor performance experiments you can try to deactivate them. To deactivate them you can go to Elementor > settings > features

Performance features currently in the experimental stage are:

• Inline Font Icons – This experiment renders icons as SVGs without loading the Font-Awesome and eicons libraries. Since SVGs are vector-based images which are rendered using the browser’s engine, they do not increase server requests which improves performance

I am looking forward to hearing back from you soon.

Kind regards,

• This reply was modified 4 months, 2 weeks ago by Milos.