Adobe Analytics Server Call Usage addresses your requests for transparency into both browser and mobile server call usage data. It lets you access:
The main benefits of Server Call Usage include:
Previously, while you could access monthly server call consumption data under Analytics > Admin > Billing , this data was only updated 6 days after billing had closed for that month. Further, the data did not include mobile consumption. This feature will also replace the current Billing Information report under Analytics > Reports .
Here is a short primer on essential terminology for Server Call Usage:
A server call, also known as a "hit" or an "image request", is an instance in which data is sent to Adobe servers to process. The most common type of server call is a page view. A page view occurs where a visitor views a page on your website and a server call is generated to Adobe, where information is collected, processed, and then included in your report metrics.
There are other types of server calls, including exit links and file downloads, where data is sent to Adobe to process, but they are not recorded as a new page view. Even "excluded" page views (excluded from your reports by an IP address range you configure, for example) are server calls because they are received and processed by Adobe but never show up in your reports.
Primary Server Call: Requests received directly from website visitor browsers or the Data Insertion API. Includes Primary Hits (Page Views), Primary Custom Events, Primary Download Events, and Primary Exit Events.
Secondary Server Call: Copies of primary server calls created by multi-suite tags or copied/moved by a VISTA rule. If a secondary server call has been moved (not copied) to a different report suite by a VISTA rule, the accumulated secondary calls are deducted from the primary server calls.
Mobile Primary Server Call
Requests received directly from one of the Mobile SDKs. Include trackAction, trackState, trackApp Crashes, trackActionFromBackground, trackLocation, trackBeacon, trackPushMessageClickThrough, trackTimedActionBacklog, trackLifetimeValueIncrease.
Mobile Secondary Server Call
Copies of primary server calls created by multi-suite tags or copied/moved by a VISTA rule. If a secondary server call has been moved (not copied) to a different report suite by a VISTA rule, the accumulated secondary calls are deducted from the primary server calls.
Note: If your company is contractually entitled to only Mobile Server Calls (Primary or Secondary), both your web and mobile-specific usage will count against your Mobile-specific commitment.
Billing Company (Billing ID)
The legal entity that gets billed for server calls. For example, adobe.com. Each billing company has a Billing ID that is used to uniquely identify the billing customer. A billing ID could be tied to multiple Experience Cloud Orgs; there is not always a 1:1 relationship between an org and a billing ID.
One billing company can have multiple login companies . A login company is a collection of report suites used by your organization. Some organizations have multiple login companies that apply to different parts of the organization. This is especially useful for large organizations that deal with different business units where many report suites are not applicable to others in the company.
Often, these are the regional subsidiaries of a company. This example shows login companies and their associated report suites:
Note: Server call usage data for all report suites within a billing company is visible to all users with the appropriate permission.
Experience Cloud organization
An organization is the entity that enables an administrator to configure groups and users, and to control single sign-on in the Experience Cloud. The organization functions like a login company that spans all the Experience Cloud products and solutions.
Most often, an organization is your company name. However, a company can have many organizations.
Server Call Commitment
When your company signs a contract with Adobe, the Adobe Sales team identifies with the you, the customer, the types (Primary, Secondary, Mobile Primary, Mobile Secondary) and the approximate number of server calls that you are expecting to incur over the course of the contract period. This is your total server call commitment.
For purposes of server call usage monitoring, this total server call commitment is broken down into smaller usage periods (such as 3 months) to facilitate year-over-year comparisons.
Contract periods can go over multiple years. Let's say your company has a server call commitment of 6 million calls for a 3-year contract time. For purposes of server call usage monitoring, this 3-year period can be broken down into smaller usage periods to facilitate year-over-year comparisons.
The Server Call Usage permission is automatically granted to Analytics Admins. It lets users view the dashboard and create server call alerts. Admins can choose to grant this permission to non-admins.
Your company can choose which login companies have access to Server Call Usage.
|Grant permission if you are logged in to Adobe Analytics (Legacy Login)
|Grant permission if you are logged in to Adobe Experience Cloud
Server Call Usage