After setting up the Event Monitoring Analytics app in CRM Analytics, users report that the app returns no data, dashboards appear empty, or specific event types (such as API calls or LightningInteraction events) are missing from datasets. This article covers the most common causes and resolutions for post-setup data visibility issues in the Event Monitoring Analytics app.
Each user of the Event Monitoring Analytics app requires the Event Monitoring Analytics Apps permission set license (PSL). Without this PSL, users cannot access the app or its dashboards even if they have standard CRM Analytics access. The PSL is a separately provisioned license that is not included with CRM Analytics Growth or Plus.
The Event Monitoring Analytics app requires the org-level Enable Event Monitoring setting to be active. If this setting is disabled or was never enabled, event log file objects are not generated and the app has no source data to display.
Event log files for the previous day are generated approximately 24 hours after the events occur. If you are looking for today’s data or data from the last few hours, it does not yet exist in the event log file objects. This is expected behavior, not an error.
The Event Monitoring Analytics app uses a dataflow or recipe to pull event log files into CRM Analytics datasets. If the dataflow was not configured to include a specific event type (for example, API or LightningInteraction), that event type does not appear in the datasets even if the events were logged.
Contact your Salesforce Account Executive to verify that the Event Monitoring Analytics Apps PSL is included in your contract. Once provisioned, assign the PSL in Setup:
Go to Setup > Event Monitoring and verify that Enable Event Monitoring is toggled on. If it is not enabled, contact Salesforce Support to discuss enabling it for your org based on your contract.
If the app shows data from previous days but not today, this is expected. Event log files are generated once per 24 hours for the prior day’s events. Check whether the data you expect is more than 24 hours old. If hourly event logs are enabled for your org, data may be available sooner — check your contract to confirm.
In Data Manager, open the Event Monitoring Analytics dataflow or recipe. Verify that the event type you expect (for example, ApiTotalUsage or LightningInteraction) is included as a source object. If it is not present, add it to the data sync configuration under SFDC_LOCAL, run a data sync, then rerun the dataflow or recipe.
The app was showing data last month but now shows nothing. What changed?
Common causes include: the Event Monitoring Analytics Apps PSL was not renewed; the dataflow was not scheduled and missed runs; or the Integration User lost access to the EventLogFile object due to a permission change. Check the Jobs Monitor for recent dataflow status and verify the PSL assignment is still active.
I have the PSL but the Event Monitoring Analytics app does not appear in my app list.
The PSL must be paired with the correct permission set. Ensure the user has been assigned the Event Monitoring Analytics Apps Admin or Event Monitoring Analytics Apps User permission set, not just the PSL. See the setup guide for step-by-step permission set assignment instructions.
Can I get real-time event data in the app?
No. Event log files are generated on a 24-hour cycle. Real-time event streaming is a separate product (Salesforce Event Log Streaming). The Event Monitoring Analytics app is designed for historical analysis of the prior day’s events.
Event Monitoring Analytics App Permission Set License and User Permissions — Salesforce Help
Set Up Salesforce Permissions for the Event Monitoring Analytics App — Salesforce Help
Identify Event Monitoring Analytics App User Types — Salesforce Help
005385256

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.