---
schema_version: "1"
id: 280d8cdd9b4046d4b2d0032398db4a68313a2c9cfe77a1ca0b9efd662c3aef0b
title: Best Practices and Considerations for Leveraging Event Log Object Data
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/elo_best_practices.md
canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.elo_best_practices.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 9b524a2838ee70c723fa2841463dbf157932f45dbdf222e1cf2e5de49ebfec9d
description: It’s important to understand the recommended practices and limitations for the Event Log Object framework to get the most out of your log data. Here are some tips to ensure your queries run smoothly.
products:
  - Salesforce Platform
  - Cross Cloud
release: "264"
---
# Best Practices and Considerations for Leveraging Event Log Object Data

It’s important to understand the recommended practices and limitations for the Event Log Object framework to get the most out of your log data. Here are some tips to ensure your queries run smoothly.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
      <colgroup>
        <col>
      </colgroup>
      <tbody>
        <tr class="">
          <td class="slds-cell-wrap" style="vertical-align:top;">Available in: Salesforce Classic (not available in all orgs), and Lightning
            Experience</td>

        </tr>
        <tr class="">
          <td class="slds-cell-wrap" style="vertical-align:top;">
            <p>Available in: <strong>Enterprise</strong>, <strong>Performance</strong>, and <strong>Unlimited</strong>
              Editions</p>
            <p style="margin-bottom:0;">Requires Salesforce Shield or Salesforce Event Monitoring add-on
              subscriptions.</p>
          </td>

        </tr>
      </tbody>
    </table> <table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
      <colgroup>
        <col style="width:49.504950495049506%">
        <col style="width:50.495049504950494%">
      </colgroup>
      <tbody>
        <tr class="">
          <td class="slds-cell-wrap" colspan="2" style="vertical-align:top;">User Permissions Needed </td>

        </tr>
        <tr class="">
          <td class="slds-cell-wrap" style="vertical-align:top;">
            <p style="margin-bottom:0;">To query and view event log object data: </p>
          </td>

          <td class="slds-cell-wrap" style="vertical-align:top;">
            <p style="margin-bottom:0;">View Event Log Object Data</p>
          </td>

        </tr>
      </tbody>
    </table>

## Querying Event Log Object Data Through SOQL

As of Spring 25’, the Event Log Object framework only supports SOQL queries, with the following exceptions:

- Relationship queries
- `HAVING`
- `OFFSET`

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-setup-264-0-0-production-enus/6f21df35-9ea0-4f53-ac94-45c3b5dfd5bc/images/icon_note.png)

Note Event Log Objects are designed for users with specific permissions to perform interactive analytics and diagnose security and performance incidents via SOQL. This feature is not meant to handle concurrent queries from a large number of users.

## Timestamp Field Considerations

The only supported date function for the Timestamp field in a `where` clause within the Event Log Object framework is DAY\_ONLY(). See [Date Functions](https://developer.salesforce.com/docs/atlas.en-us.soql_sosl.meta/soql_sosl/sforce_api_calls_soql_select_date_functions.htm) for more information on querying data by date periods.

You can query up to 15 days of data at a time using the Timestamp filter present on all event log objects. Consequentially, expect these behaviors when querying using the Timestamp field:

- When there are 3 or more Timestamp filters in the WHERE clause, we block the execution of the query with an error.
- `!=` isn’t supported
- When the Timestamp filter isn’t specified in the query, we append a filter in the backend to query only the last 15 days of data.
- If you are specifying Timestamp filters as part of an `AND` condition, the time range must fall within 15 days.
- No more than 2 Timestamp filters can be used for `OR` and `IN` operators.
- If a full range isn’t specified in the Timestamp filter (for example, if either the upper or lower bound is missing) the filter automatically retrieves 15 days of data in the direction of the missing bound.

![Example](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-setup-264-0-0-production-enus/6f21df35-9ea0-4f53-ac94-45c3b5dfd5bc/images/icon_example.png)

Example Valid Format:

- `Timestamp >= userSpecifiedTimeLower AND timestamp <= userSpecifiedTimeUpper`
- `Timestamp = userSpecifiedTime1 OR Timestamp = userSpecifiedTime2`
- `Timestamp IN (userSpecifiedTime1, userSpecifiedTime2)`

![Example](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-setup-264-0-0-production-enus/6f21df35-9ea0-4f53-ac94-45c3b5dfd5bc/images/icon_example.png)

Example Valid Timestamp Filter:

- `Timestamp >= 2024-09-27T17:18:15.553Z AND timestamp <= 2024-10-05T17:18:15.553Z`

![Example](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-setup-264-0-0-production-enus/6f21df35-9ea0-4f53-ac94-45c3b5dfd5bc/images/icon_example.png)

Example Invalid Timestamp Filter:

- `where Timestamp > 2024-09-27T17:18:15.553Z OR Timestamp = 2024-10-27T17:18:15.553Z`
- `where Timestamp = 2021-10-26T17:18:15.553Z AND Timestamp < 2024-10-27T17:18:15.553Z`