Activity Usage Reporting activity-usage-reporting
Overview overview
The Activity Usage Report helps you view and track the activity usage of your Audience Manager instance, giving you a clear idea of how your activity usage compares to your contractual commitment.
Additionally, you can download the Activity Usage Report whenever you need, for record keeping and custom analysis.
Considerations considerations
The Activity Usage Report is available to all Audience Manager users with administrator privileges.
Use Cases use-cases
There are two main use cases of the Activity Usage Report:
- Tracking actual instance activity usage against your activity usage commitment: Most customers have a monthly estimated activity commitment per Audience Manager instance, which is then cumulated into a yearly activity commitment across all instances. While this report is not a billing report, it can provide helpful guidance as to whether you are exceeding the committed activity usage.
- Validation for implementation changes: If you recently updated your implementation, such as setting up ÃÛ¶¹ÊÓƵ Analytics server-side forwarding, or changing your ÃÛ¶¹ÊÓƵ Target server call settings, this report can help you check whether the new activity volume is in line with your expected activity volume.
Using the Activity Usage Report using
To see the Activity Usage Report, log in to your Audience Manager account, and go to Administration > Usage.
Next, use the Reporting Interval filter to select the time interval to generate the report for. You can choose between 30, 60, 90 days, or a custom date range.
Once your report loads, you can see a breakdown of your Activities for the selected period.
Activities define the aggregate total of all onsite and offsite interactions with Audience Manager, split into the following categories:
- Server Calls: Any data collection or retrieval event sent to Audience Manager from websites, servers, email, mobile application(s), or other systems.
- Pixel Calls (formerly known as Impression Server Calls): Data collected from ads (such as impression volume from a targeting platform) or email impression calls made to Audience Manager. These require the presence of the
d_eventparameter in the query string. - On-Boarded Records: Unique records ingested from your own customer relationship management system (CRM) or other offline data files, such as call center records, device IDs, and custom data feeds from external data providers.
- Log File Records: Unique records from log files ingested into Audience Manager from a targeting platform.
Additionally, you can use the Activity Usage Trends graph types to switch between two type of graphs.
You can also hover your cursor over a specific date in the timeline to see the detailed usage for that date.
Exporting Activity Usage Reports export
For a better overview of your Audience Manager activity usage level, you can export the Activity Usage Report based on the type of records that you want to include.
The Onboarded Records Breakdown and Onsite Server Calls Breakdown reports provide the most granular insight of source data available for these activities. The volume attributed to these breakdowns is based on your implementation.
Onboarded Records Breakdown onboarded-breakdown
This report contains onboarded records broken down by data source.
Onsite Server Calls Breakdown onsite-breakdown
This report contains a breakdown of server calls from three sources: Analytics, Target, and Other.
- Analytics: These are billable server calls passed from all ÃÛ¶¹ÊÓƵ Analytics instances to Audience Manager, including server-side forwarding. Secondary server calls or duplicate server calls (as in the case of server side forwarding from multiple report suites) are not billable activities, so they are not included in this breakdown.
- Target: These are server-side calls from ÃÛ¶¹ÊÓƵ Target to Audience Manager, to retrieve Audience Manager segment data as part of a server-to-server integration.
- Other: Includes calls from any other website or system (partner sites, direct server calls, etc.), mobile browser/app calls via the SDK, DIL, event calls, and DCS calls. Also includes calls from Target if set up as a cookie integration (rather than server-to-server).