Field descriptions for a report suite’s General Account Settings in Admin.
These settings contain editing options for basic report suite functionality, such as name and time zone.
Site Title
Identifies your site. Give each report suite a unique site title.
Base URL
Specifies the report suite’s main website. The Base URL does not affect referrer filtering. Use
internal URL filters instead.
Time Zone
Determines the date and time associated with your report data. Changing the time zone for a live report suite creates either a spike or gap in report data. To minimize the impact, Adobe recommends changing time zones during non-peak hours to avoid skewing data. For example, if you change the report suite time zone from Central to Pacific at 3:00pm, the report suite’s current time becomes 1:00pm. Because reporting has already collected data for the 1:00 hour, reports show a traffic spike between 1:00pm and 3:00pm. Alternatively, if you change the report suite time zone from Central to Eastern at 3:00pm, the report suite’s current time becomes 4:00pm. Reports display no data between 3:00pm and 4:00pm on the day of the time change.
Default Page
If your Most Popular Pages report contains URLs rather than page names, this setting prevents multiple URLs from representing the same page. For example, the URLs https://example.com
and https://example.com/index.html
are typically the same page. You can remove default filenames so that these two URLs would both show up as https://example.com
. If left blank, the following filenames are removed from the URLs: index.htm, index.html, index.cgi, index.asp, default.htm, default.html, default.cgi, default.asp, home.htm, home.html, home.cgi, and home.asp. To disable stripping of filenames altogether, enter a value that is never present in your URLs.
Replace the last octet of IP addresses with 0
When enabled, replaces the last octet of IP addresses with a zero. This occurs before geo-related reports are populated and therefore may impact the accuracy of these reports.
IP Obfuscation
Turns IP addresses into non-recognizable strings, essentially removing them from Adobe data stores. When IP Obfuscation is enabled, the original IP addresses are permanently lost.
Note: The IP addresses are obfuscated everywhere in Analytics, including Data Warehouse. However, the IP setting in Target is controlled separately, so this setting has no impact on Target.
If IP obfuscation is enabled, all needed processing including IP filtering/exclusion, bot rules and Geosegmentation lookups are done before the IP address is obfuscated. You don’t need to change anything when you enable IP obfuscation.
- Checking Disabled leaves the IP address in the data.
- Checking Obfuscate IP address changes the IP to two colons followed by a hashed value (e.g.,
::1932023538
).
- Checking Remove IP address replaces the IP address with
::X.X.X.X
in the data, after geo-lookup.
Note: This setting might require changes to custom bot rules or IP exclusions.
Note: Data collected via Experience Edge can have IP obfuscation applied at Experience Edge via data stream configuration. If the IP obfuscation is applied at the edge it will already be obfuscated with it reaches Analytics impacting bot rules and geo lookups.
Enable Data Warehouse
Enables the Data Warehouse UI under Analytics > Tools > Data Warehouse.
Zip Option
Lets you specify the zip code instead of using whatever our geo IP lookup produces.
Multi-byte character support
Multibyte character support stores characters in the report suite using UTF-8. Upon receipt, the system converts data from your web page’s character set to the UTF-8 character set, so you can use any language in your marketing reports. Contact your Adobe Account Team or Customer Care to change the multibyte character support for an existing report suite.
Activated
Specifies whether this report suite is activated or not.
Base currency
Lets you specify the base
currency for this report suite.
Organization ID
The ID associated with your provisioned Experience Cloud company. This ID is a 24-character alphanumeric string, followed by (and must include) @AdobeOrg.