mixpanel.json: Usage tracking

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support Milos

    (@miloss84)

    2 months, 1 week ago

    Hi there,

    Thank you for contacting us.

    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

    Thread Starter enteroz

    (@enteroz)

    2 months, 1 week ago

    @miloss84

    Thank you for the reply.

    I’d like to clarify that this issue is not related to caching or third-party integrations, but to Elementor’s core logic.

    In the Events Manager module, the remote Mixpanel configuration is fetched unconditionally:

    $mixpanel_config = self::get_remote_mixpanel_config();

    Call happens inside get_editor_events_config() before the consent logic is used to decide whether events can be sent or the “Data Sharing” setting is applied.

    Even when Tracker::is_allow_track() evaluates to false, get_remote_mixpanel_config() still executes and triggers:

    wp_remote_get( static::REMOTE_MIXPANEL_CONFIG_URL );

    As a result, the request to
    https://assets.elementor.com/mixpanel/v1/mixpanel.json
    is made, regardless of the Data Sharing setting.

    From a code perspective, the remote request should be gated behind the same consent logic (Tracker::is_allow_track() and related checks), or avoided entirely when Data Sharing is disabled.

    Could you please confirm whether this behavior is intentional or if this is a known issue that will be addressed?

    I also noticed that this exact issue is already addressed in Elementor’s GitHub repository:
    https://github.com/elementor/elementor/pull/34420

    Best regards

    Plugin Support Milos

    (@miloss84)

    2 months ago

    Hi,

    Thank you for the detailed explanation and for sharing your findings.

    Since this issue is already raised on our GitHub repository, that is the right place to continue the discussion. Our developers actively follow GitHub threads, and you’re welcome to ask additional questions there, share your observations, or provide any further insights you’ve discovered.

    Unfortunately, we’re not able to assist further with this from the support side here, and I’m sorry about that. For core logic and tracking-related behavior, GitHub allows the development team to review everything in full technical context and respond appropriately.

    Please continue the conversation on the related GitHub pull request, as that will ensure it gets proper visibility and attention from our developers.

    Best regards,

    Plugin Support Rica

    (@ricav)

    1 month, 3 weeks ago

    Due to inactivity, this ticket has been closed.

Viewing 4 replies - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.