Show Menu
TOPICS×

Administration

Configure users and learn about data sampling.
For Admin Console help, see the Analytics Reference.

User Licenses

Before a user can log in, the user must be granted a user license. User licenses are concurrent-use licenses. Users can share user licenses, but the number of users at any given time is limited to the number of user licenses purchased.
When the number of logged-in users exceeds the number of available licenses, a dialog box notifies the user that all available licenses are in use. The user's position in the queue is shown along with a link to recheck the queue position. When a license becomes available, the user is notified with an email and a pop-up dialog box indicating that ad hoc analysis is available for access. The user then has 15 minutes to respond before losing the position in the queue.

Grant User Licenses

Steps that describe how local Reports and Analytics administrators can grant user licenses via the permissions system.
  1. Log in to the Experience Cloud.
  2. Click Admin > User Management.
  3. Click Edit Groups.
    If your company has purchased user licenses, the Ad Hoc Analysis License Users group appears in the Group Name column. The number of available licenses for user logins is also shown.
  4. Click Edit.
  5. Under Assign User Logins, select the users you want to add to the group, then click Add.
  6. Click Save Group.
    The licensing system does not limit the number of users that are added to a group. There is limited concurrent usage to the number of user licenses purchased.

Manage User Sessions

Steps that describe how an administrator can terminate a user's session. This feature does not prevent a terminated user from logging in again.
  1. Click Adobe Analytics > Admin > User Management, then click Manage Users.
  2. Locate the user, then click Terminate.
    On the Active Ad Hoc Analysis Sessions page, the user who has been idle the longest displays at the top of list.

Permissions

You set up access to report suites in the Administration Console. You can configure permission at the report suite level. For example, if you have multiple report suites enabled, but you do not want to grant all users access to all report suites, you can create groups with specific report suites, and then assign those users to the applicable group.

Add a User to the All Report Access Group

Steps that describe how to grant non-admin users access to all report suites.
  1. Log in to the Experience Cloud.
  2. Click Adobe Analytics > Admin > User Management > Edit Groups.
  3. Click All Report Access.
  4. In Available Users, select the user, then click Add.
  5. Click Save Group.

Create Permission Groups

Create permission groups for non-admin users for specific report suites.
  1. Log in to the Experience Cloud.
  2. Click Adobe Analytics > Admin > User Management > Edit Groups.
  3. Create a permissions group for non-admin users that includes the ad hoc analysis-activated report suites that you want accessible to users.
    The report suites available to the user are displayed in the Report Cloud menu when you create a new project.

Set Up Proxy Policies in Java

Steps that describe how to set up proxy policies if you receive a server connection error.
Ad Hoc Analysis uses HTTP to communicate with the server. It is subject to the same proxy policies as other HTTP traffic.
  1. In the Windows Control Panel, launch the Java Control Panel.
  2. On the General tab, click Network Settings.
  3. Select Use browser settings, or manually configure the proxy settings.
  4. Click OK, then click OK on the Java Control Panel.

How Data is Sampled

Samples of visitor data is taken to produce meaningful, accurate reporting. The date range is used as the data slice for a loaded project. A slice typically represents the current month, plus the previous two months.
For optimal processing, ad hoc analysis uses roughly 750 million as the maximum hits per slice. (Hits = page views + events.)
To arrive at the projected sample rate, the projected hits are calculated per data set, then divided by 750 million, as shown here:
  • (Avg. daily hits x number of days in the slice) / 750 million
For example, if you have 10 million hits a day, with a data slice of 90 days:
  • (10,000,000 x 90) / 750,000,000 = 1.2
So to keep the number of hits for this 90 day slice below 750,000,000, the data could be sampled at 1.2:1, but because samples on whole numbers are used, the sample rate is 2:1.
As another example, if you have 10 million hits a day, with a data slice for 365 days:
  • (10,000,000 x 365) / 750,000,000 = 4.8
So to keep the number of hits for this 365 day slice below 750,000,000, the data could be sampled at 4.8:1. Using whole numbers, the sample rate is 5:1.