The queries you build when searching for sessions are reflected in the URL parameters. You can share these URLs with others to deep link to search results, or even create them programatically.

/sessions?query={key}={value}

• The logical combinations, and and or, are built into the query, separated by spaces (%20):

  • /sessions?query={key1}={value1}%20AND%20{key2}={value2}
  • /sessions?query={key1}={value1}%20OR%20{key2}={value2}

• Implicitly, and is used, so the following two queries are equivalent:

  • /sessions?query={key1}={value1}%20AND%20{key2}={value2}
  • /sessions?query={key1}={value1}%20{key2}={value2}

• For the list of session properties, see our Session search docs

• For more information on operators and general search, see our Search docs

Viewing sessions for a particular user:

/sessions?query=identifier=alice@example.com

Excluding sessions from your organization:

/sessions?query=identifier!=*@yourdomain.com*

Viewing sessions for a particular page in your app:

/sessions?query=visited-url=*/your/path/name*

Multiple properties

/sessions?query=identifier=Bob%20email!=alice@example.com