---
sourceDocument: Australia Platform Analytics
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/now-intelligence

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Platform Analytics

ft:clusterId :

    - par

bundleId :

    - par

workflow :

    - Platform


---

# Types of tracking consent policies

# Types of tracking consent policies in Usage Insights {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

There are five types of tracking consent policies that you can define for individual countries. This option provides you with the flexibility to define tracking policies according to the country and even according to users or
roles.
The default consent policies are set to No Consent Required for all countries/groups of users. However, admins can update a group or individual country's consent policy to any of the following:  

Basic tracking
:   Users with the admin role can obtain usage metrics only. This consent policy tracks and processes user activity but only stores basic user data, including hashed user IDs, and stores only partial session details including
    the session time.

Disabled
:   No tracking of users occurs in any of the Usage Insights tracked applications. Usage metrics aren't obtained from these users.

Explicit opt-in
:   Users are presented with a message to select whether to opt in or decline to be tracked. This is a more advanced policy.

Notice
:   Users are presented with a message explaining that their activity in the application will be tracked. This is a more advanced
    policy.

No consent required
: Users are automatically tracked and aren't presented with an opt-in/decline message. This is a more advanced policy. This is the default consent policy for all users.  
Hinweis:  
* Every country's consent policy is set to No Consent Required by default. However, users can opt in or out of ServiceNow applications individually in application Settings. If you want to provide opt-in messages or notices to users when they log in, you must configure tracking consent policies.
* If a country's consent policy is set to Explicit Opt-In or Notice, individual users are asked for consent yearly. Their existing tracking preference expires every 365 days.
* If a country's tracking consent policy is set to Disabled, user metrics aren't tracked.
* Counters in the Usage Insights application contain aggregated user numbers.
* Analytics administrators can choose to store additional user properties. See [Add user properties as filters to Usage Insights](https://servicenow-prod.fluidtopics.net/Qj3LtqHiWcAF6Xy0UnzD~A "In addition to the default filters on the pages of the Usage Insights application, you can add filters based on user properties. This allows you to effectively segment your Usage Insights data to develop a deeper understanding of your users and their usage patterns. User properties-based filters are supported as global filters for all pages and objects in the Usage Insights application.") for more information.
* When Consent policies are updated to display a notice or require opt-ins, capturing detailed user and session data may be impacted due to individual opt-outs. Aggregated metrics will continue to reflect the total user base, including those who have opted out of individual session tracking.
{#uxa-tracking-types__ul_rvn_wkk_12c}
* **[Define consent policies according to country](https://servicenow-prod.fluidtopics.net/niKMHSdkDTPmvvxCltlkUw)**   
  Define the tracking consent policies for users within different countries. You can either select the same tracking consent policy for all countries, use the allocated default values, or define different consent policies for individual countries.
* **[View and update an individual country's consent policy](https://servicenow-prod.fluidtopics.net/f8P7eDtHA80GhhA3uREcaw)**   
  View a list of all countries with their assigned consent policies and select a country to update its existing policy.
* **[Define how to detect your user's location](https://servicenow-prod.fluidtopics.net/uHJtiP5MmUVuIEKBbe3yaw)**   
  Detect your users' location by selecting and prioritizing a detection policy. You can also define the order in which these policies apply. There are predefined detection policies, but you can create custom scripts to give more flexibility to your definitions.

