---
schema_version: "1"
id: 93fd9f7a9ecb7730579a2fef5ad4a5b5799e8676e5fa1dd2c94d74f030e0655f
title: Search Event Type
collection: legacydeveloper
version: current
locale: en-us
portal_url: https://docs.salesforce.com/legacydeveloper/current/en-us/object_reference/sforce_api_objects_eventlogfile_search.md
canonical_url: https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_objects_eventlogfile_search.htm
source_site: developer.salesforce.com
content_type: documentation
content_hash: a404703703226b0cc23b94560e9e75ac71cafc310869a56b2aa76a5ef8254e70
description: Search events contain details about the user’s search query. All searches within the app, including Experience Cloud sites, are included. However, unauthenticated users won’t have a unique Salesforce user ID.
---
# Search Event Type

Search events contain details about the user’s search query. All searches within the app, including Experience Cloud sites, are included. However, unauthenticated users won’t have a unique Salesforce user ID.

For details about event monitoring, see the [Trailhead Event Monitoring module](https://trailhead.salesforce.com/en/modules/event_monitoring/units/event_monitoring_intro "HTML (New Window)") or [REST API Developer’s Guide](https://developer.salesforce.com/docs/atlas.en-us.264.0.api_rest.meta/api_rest/using_resources_event_log_files.htm "HTML (New Window)").

## Fields

<table class="featureTable sort_table" summary=""><tbody class="tbody"><tr><td class="entry"><strong class="ph b">Field</strong></td><td class="entry"><strong class="ph b">Details</strong></td></tr><tr><td class="entry"><span class="keyword parmname">EVENT_TYPE</span></td><td class="entry"><dl class="dl detailList"><dt class="dt dlterm">Type</dt><dd class="dd">String</dd><dt class="dt dlterm">Description</dt><dd class="dd"><span class="ph" id="event-type-desc"><a name="event-type-desc"></a>The type of event.</span> The value is always <samp class="codeph nolang">Search</samp>.</dd></dl></td></tr><tr><td class="entry"><span class="keyword parmname">NUM_RESULTS</span></td><td class="entry"><dl class="dl detailList"><dt class="dt dlterm">Type</dt><dd class="dd">Number</dd><dt class="dt dlterm">Description</dt><dd class="dd">Number of results returned by the search query.</dd><dt class="dt dlterm">Possible Values</dt><dd class="dd"><ul class="ul bulletList"><li class="li">0</li><li class="li">25</li><li class="li">1000</li></ul></dd></dl></td></tr><tr><td class="entry"><span class="keyword parmname">ORGANIZATION_ID</span></td><td class="entry"><dl class="dl detailList"><dt class="dt dlterm">Type</dt><dd class="dd">Id</dd><dt class="dt dlterm">Description</dt><dd class="dd">The 15-character ID of the organization.</dd><dd class="dd">For example: <samp class="codeph nolang">00D000000000123</samp>.</dd></dl></td></tr><tr><td class="entry"><span class="keyword parmname">PREFIXES_SEARCHED</span></td><td class="entry"><dl class="dl detailList"><dt class="dt dlterm">Type</dt><dd class="dd">String</dd><dt class="dt dlterm">Description</dt><dd class="dd">Space-separated list of key prefixes that were searched.</dd><dt class="dt dlterm">Example</dt><dd class="dd">001 006 ka0</dd></dl></td></tr><tr><td class="entry"><span class="keyword parmname">QUERY_ID</span></td><td class="entry"><dl class="dl detailList"><dt class="dt dlterm">Type</dt><dd class="dd">String</dd><dt class="dt dlterm">Description</dt><dd class="dd">Unique ID of the search query.</dd><dt class="dt dlterm">Example</dt><dd class="dd">-2vx8relit08r</dd></dl></td></tr><tr><td class="entry"><span class="keyword parmname">REQUEST_ID</span></td><td class="entry"><dl class="dl detailList"><dt class="dt dlterm">Type</dt><dd class="dd">String</dd><dt class="dt dlterm">Description</dt><dd class="dd">The unique ID of a single transaction. A transaction can contain one or more events. Each event in a given transaction has the same <span class="keyword parmname">REQUEST_ID</span>.</dd><dd class="dd">For example: <samp class="codeph nolang">3nWgxWbDKWWDIk0FKfF5DV</samp>.</dd></dl></td></tr><tr><td class="entry"><span class="keyword parmname">SEARCH_QUERY</span></td><td class="entry"><dl class="dl detailList"><dt class="dt dlterm">Type</dt><dd class="dd">String</dd><dt class="dt dlterm">Description</dt><dd class="dd">The first 100 characters of the search query.</dd><dt class="dt dlterm">Example</dt><dd class="dd">Salesforce</dd></dl></td></tr><tr><td class="entry"><span class="keyword parmname">TIMESTAMP</span></td><td class="entry"><dl class="dl detailList"><dt class="dt dlterm">Type</dt><dd class="dd">String</dd><dt class="dt dlterm">Description</dt><dd class="dd">The access time of Salesforce services in GMT.</dd><dd class="dd">For example: <samp class="codeph nolang">20130715233322.670</samp>.</dd></dl></td></tr><tr><td class="entry"><span class="keyword parmname">TIMESTAMP_DERIVED</span></td><td class="entry"><dl class="dl detailList"><dt class="dt dlterm">Type</dt><dd class="dd">DateTime</dd><dt class="dt dlterm">Description</dt><dd class="dd">The access time of Salesforce services in ISO8601-compatible format (<samp class="codeph nolang">YYYY-MM-DDTHH:MM:SS.sssZ</samp>).</dd><dd class="dd">For example: <samp class="codeph nolang">2015-07-27T11:32:59.555Z</samp>. Timezone is GMT.</dd></dl></td></tr><tr><td class="entry"><span class="keyword parmname">USER_ID</span></td><td class="entry"><dl class="dl detailList"><dt class="dt dlterm">Type</dt><dd class="dd">Id</dd><dt class="dt dlterm">Description</dt><dd class="dd">The 15-character case insensitive ID of the user who’s using Salesforce services through the UI or the API.</dd><dd class="dd">For example: <samp class="codeph nolang">00590000000I1SNIA0</samp>.</dd></dl></td></tr></tbody></table>

#### See Also

- [EventLogFile Supported Event Types](https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_objects_eventlogfile_supportedeventtypes.htm "The EventType field in the EventLogFile object supports these events. Some common fields, such as CPU_TIME and RUN_TIME, can have null or zero values depending on how the events are generated for a given feature. Sometimes, three quotation marks appear around event data containing special characters in the CSV file. The third quotation mark is necessary for tools and applications to parse the field data at the correct field value boundary.")
- [EventLogFile](https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_objects_eventlogfile.htm "Represents event log files generated by Event Monitoring. Use event log file data to analyze usage trends and user behavior in your Salesforce org. This object is available in API version 32.0 and later. The Interval and Sequence fields are available only in API version 37.0 and later.")