Events and Report
Following are debugging instructions in case your events are not showing on the Copilot.cx console.
Instructions on how to see and understand data in the Copilot.cx console can be found in our Knowledgebase.
Troubleshooting events not arriving in the system
- Make sure the Firebase is configured correctly, you can follow the 5 min Firebase Configuration steps.
- For testing, you can use Firebase DebugView, meaning:
- Data will not arrive in the Copilot.cx system, since the events get trashed.
- You will be able to see the events in 10 seconds in the Firebase system.
- Validate you call sessionStarted() in each app activation, so you have the User ID connected to the events.
- Wait up to 24 hours for the events to get to the system, go to "Users & Devices" -> "Support", and find the user to view the events. user_created, thing_created, and user_thing_associated will appear directly, no 24 hours required.
- If you know your system is GDPR complient and are not sure, the following will help:
- Users who do not have GDPR consent in a system will not have data connected to them.
- Under "Users & Devices" -> "Operate" you can see the percentage of your users who are "Allowed to process" according to GDPR.
- When you go into a user under “Users & Devices” -> "Support", they have a tag at the top with "Analysis approved" or "Analysis decliend".
- On GDPR complient systems, you should send the consent API for every user who agrees to Analytics.
- If all else fails, please send your Maverick the user ID, time, and what you did, so our team can look in the back flow of the data to find the issue.
- Before doing so, validate that the export of your own Firebase into the BigQuery linked to it is working correctly.
Any questions?
Contact your Techincal Onboarding Manager with any questions