3 Tips for Event Monitoring Analytics Tableau CRM App
Tableau CRM & Event Monitoring
It’s been a couple of years since Tableau has been sold to Salesforce ☁️ Salesforce rebranded Einstein Analytics (previously known as Wave) as Tableau CRM couple releases back.
Tableau CRM is a paid service (as many other Salesforce tools appeal to stakeholders do) but you can play around with the tool by creating a Tableau CRM-enabled Developer Edition org.
Event Monitoring also is a paid service (part of a Salesforce Shield or Event Monitoring Add-on) but is available for free in Developer org— 3 event types (Login, Logout, Insecure External Asset) are available in all orgs at no cost, but any other event type will require a purchase. Tableau CRM access and an app template for Event Monitoring will be included when you purchase Event Monitoring access, so no need to pay extra on enabling Tableau CRM.
If you are lucky enough to be part of the Event Monitoring project but have never used Einstein Analytics/Tableau CRM previously, this article is for you 🍀 Here are 3 tips for creating Event Monitoring Tableau CRM Dashboards.
1. Turn on Time Zone Support
I spent at least several hours trying to find a way to convert the timestamp that was associated with the event logs into the local time zone. There seemed to be no way I could transform the GMT timezone into something actually useful.
Then at the end of my Google journey, I found out that Salesforce has a Beta feature that will convert Datetime/Date values into the selected time zone. Since this is Beta, it might not work properly, might encounter an unexpected error (I did encounter an error Week without Timezone function is not supported when my dashboard was using a week as a chart group. Error was resolved by creating a brand new dashboard.) or the feature might get removed in the future.
But so far (after resolving the function error) I didn’t have any issue filtering or displaying data properly based on selected timezone, not in GMT.
2. Dashboard will show 1 sample URI event… until the next data upload
This freaked me out for a while when I was trying to test the dashboard in the sandbox.
Raw Log Data shows one sample event log. This is expected behavior until the next Event Log Files are uploaded to Tableau CRM.
Within the next 24 hours of creating the Event Monitoring App, you’ll be able to see URI Upload flow — Overwrite data upload job. (If you do not see this upload data job, double-check you enabled the Event Monitoring from the setup and then contact Salesforce Support)
3. When analyzing URI events, REFERER_URI will not show custom sObject API name
If you were to filter the URI event log by each object, the easiest way would be to find out if the URI contains the sObject API name. Any standard sObject name will be found in the URI file without problem.
But if you try to search for any custom sObject’s API name, it won’t return any result. That is because the following URI pattern will be logged for the custom sObject URI event:
…/lightning/r/-CustomObjectApiName/a0V...One of the easiest ways to filter a specific custom sObject URI event (in Dataflow or Recipe) is to filter by URI contains CustomObjectApiName/xxx where xxx would be the custom sObject’s ID prefix.
Hope this can help any new Event Monitoring analytics personnel!
