Skip to main content
All CollectionsFAQ
Debugging common issues with your setup
Debugging common issues with your setup

Common errors we're seeing, and how to fix them.

Updated yesterday

If you're experiencing challenges with your setup, such as duplicated events, mismatched data, or unexpected behavior, this guide will help you identify and resolve these common issues.


1. duplicate events from multiple workspaces

One common issue occurs when events are duplicated and sent from multiple workspaces simultaneously. this often happens when:

  • you switch between multiple accounts or workspaces.

  • a browser window from a previous session remains open while logging into a new account.

How to fix it:

  1. Always set the userId explicitly in events
    always pass the userId explicitly as the second argument when sending events to avoid mismatches.

    example:

    analytics.track('Event Name', { property: 'value' }, { userId: 'correct-user-id' });

  2. Override the userId in analytics.page calls
    by default, analytics.page() does not require a userId. you can explicitly set it in the second argument to ensure accuracy.

    example:

    analytics.page('Page Name', {}, { userId: 'correct-user-id' });

  3. Close unused browser windows
    ensure that old browser windows from previous sessions are closed before logging into another account to prevent stale data.

  4. Set userId dynamically on login
    update your application to dynamically assign the correct userId whenever a user logs in.


2. Events not triggering properly

If some events are not being triggered or captured as expected:

  • check your implementation for any missing or incorrect event names.

  • verify that your tracking library is correctly initialized before sending events.

How to fix it

  • Use debugging tools
    many analytics platforms offer debugging tools to help identify missed events or setup issues.

  • Validate the event schema
    ensure that the properties and structure of your events match your analytics platform’s requirements.


3. Slow or delayed event tracking

If events take a long time to show up in your dashboard:

  • check your network logs to ensure events are being sent promptly.

  • review any server-side processing delays if applicable.

How to fix it

  • optimize your event payload size to reduce latency.

  • ensure that network calls to your analytics platform are not blocked by browser extensions or firewalls.


Need more help?

if you're still encountering issues or need further assistance, feel free to contact our support team. we're here to help you get the most out of your setup!

Did this answer your question?