# RudderStack Assistant Troubleshooting Guide


This guide contains solutions for common issues you may encounter while using RudderStack Assistant.

{{< info >}}
This guide covers troubleshooting the extension itself. 

If you're looking to debug your RudderStack SDK implementation, use the different tabs (**Overview**, **Events**, **Advanced**) described in the [Interface Reference]({{< ref "sources/event-streams/sdks/rudderstack-javascript-sdk/events-tracking-assistant/interface-reference.md" >}}).
{{< /info >}}

## Extension issues

| Issue | <div style="width: 350px">Solution</div> |
| :----| :-----|
| Extension blank or not loading | <ul><li>Right-click the extension icon > **Inspect popup** and check for errors.</li><li>Reload the extension (Chrome: `chrome://extensions/`, Firefox: `about:addons`).</li><li>If issues persist, temporarily disable other extensions or reinstall the extension.</li></ul> |
| Extension taking too long to load | <ul><li>Refresh the web page and wait for it to fully load before opening the extension.</li><li>Check browser console for errors.</li></ul> |
| Extension icon not visible in toolbar | <ul><li>Chrome: Click the puzzle piece icon (Extensions) and pin the extension.</li><li>Firefox: Right-click the toolbar > **Customize Toolbar** and drag the extension icon to the toolbar.</li></ul> |
| Extension shows stale data | Close and reopen the extension. The extension shows data for the currently active browser tab. |
| Extension not in Developer Tools | Close and reopen Developer Tools. The **RudderStack Assistant** tab should appear in the **>>** menu. |

## SDK detection issues

| Issue | <div style="width: 350px">Solution</div> |
| :----| :-----|
| SDK not detected | <ul><li>Refresh the web page with the extension open and wait 2-3 seconds.</li><li>Verify the SDK is installed by checking `window.rudderanalytics` in the browser console.</li><li>If undefined, the SDK is not installed on this page.</li></ul> |
| SDK injection not working | <ul><li>Some websites have strict Content Security Policy (CSP) headers that prevent script injection. The extension indicates if injection is not supported.</li><li>For production use, install the JavaScript SDK on the website instead.</li></ul> |

## Events and data issues

| Issue | <div style="width: 350px">Solution</div> |
| :----| :-----|
| Events not appearing in **Events** tab | <ul><li>Open the extension **before** triggering events. The extension can only capture events sent after it is opened.</li><li>To capture page load events, open the extension and refresh the page.</li></ul> |
| Events count differs from dashboard | <ul><li>This is normal behavior. The extension shows events sent from the browser, while the dashboard shows events received by RudderStack, including data from **all** user sessions.</li><li>The count can differ due to processing delays, failed events, filtering, or different time ranges.</li></ul> |
| **Overview** tab shows empty data | <ul><li>Wait for the SDK to fully initialize. Verify the SDK is detected (check for SDK version in the header).</li><li>Some data may be empty if no user ID is set or no destinations are configured.</li></ul> |

## Destination issues

| Issue | <div style="width: 350px">Solution</div> |
| :----| :-----|
| Destination not loading or showing as failed | Check **Overview** > **Destinations** for error details. Common causes include:<ul><li>Ad blocker interference: Disable ad blockers temporarily or configure custom domains/proxies</li><li>Incorrect base URL: Verify destination configuration in the RudderStack dashboard and check **Advanced** > **Custom Domains</li><li>Slow CDN response: Check network connectivity and browser console for network errors</li><li>Incorrect configuration: Verify the destination is enabled in the RudderStack dashboard and device-mode is enabled</li></ul> |
| Destination showing as filtered | <ul><li>Destinations can be filtered due to consent requirements, SDK loaded in pre-consent mode, destination not enabled in the dashboard, or explicitly disabled via integrations object in load options.</li><li>Check your RudderStack dashboard and SDK configuration.</li></ul> |

## Feature issues

| Issue | <div style="width: 350px">Solution</div> |
| :----| :-----|
| Copy to clipboard not working | <ul><li>Check browser clipboard permissions in extension settings. Try downloading as a file instead, or manually select and copy text.</li></ul> |
| Export not working | <ul><li>Check if popup blockers are enabled. Try **Copy to Clipboard** instead.</li><li>Ensure the SDK is detected and fully initialized before exporting.</li></ul> |

## Get help

If you've tried the above solutions and still have problems, report the issue on the [GitHub repository](https://github.com/rudderlabs/events-tracking-assistant/issues). Include:

- Browser and version
- Extension version
- Steps to reproduce the problem
- Screenshots (if applicable)
- Browser console errors

{{< warning >}}
Do not include write keys, credentials, or personal user data in public reports. Share these privately with support if needed.
{{< /warning >}}

## See also

- [RudderStack Assistant]({{< ref "sources/event-streams/sdks/rudderstack-javascript-sdk/events-tracking-assistant/" >}}): Learn about RudderStack Assistant and its features
- [Interface Reference]({{< ref "sources/event-streams/sdks/rudderstack-javascript-sdk/events-tracking-assistant/interface-reference.md" >}}): Learn about the different tabs available in RudderStack Assistant
- [Quickstart]({{< ref "sources/event-streams/sdks/rudderstack-javascript-sdk/events-tracking-assistant/quickstart.md" >}}): Installation and basic usage of RudderStack Assistant