Viewing Usage
The Usage Report page displays information about your LiveRamp usage for the current month and past months, as well as information about your token spending and contract details.
To learn more about billing terms and concepts, see Understanding LiveRamp Billing.
From the navigation pane, select Administration → Usage Report.
The usage overview for the current month is displayed.
To see a past month’s usage, click the Month dropdown and select the appropriate month.
To view your contract details, click on the Contract Details tile.
To view all Access spending, select the Access tab.
To view all Usage spending, select the Usage tab.
To download a full usage report, click Download Report on the Overview, Access, or Usage tab. Select the month of the usage you want the report to capture and click .
Metrics Displayed on the Overview Tab
The Overview tab displays the following metrics:
Remaining Tokens: The total number of tokens remaining. This number is calculated by subtracting the total number of tokens spent from the total number of pre-committed tokens.
Note
Unused tokens left after the end of your contract end date will not be carried over and will not be refunded.
Pre-committed Token Allotment: The number of tokens allotted to your company at the start of the contract. This number may change if there are any contract amendments or adjustments.
Tokens Spent This Month: The total number of tokens spent on access and usage in the selected month.
Contract Details: Contains details about your contract, such as your tier level, contract start and end date, pre-committed tokens, and number of tokens spent since the start of your contract.
Top Access Items by Tokens Spent: Shows the five access items from the selected month that consumed the most tokens.
Top Usage Items by Tokens Spent: Shows the five usage items from the selected month that consumed the most tokens.
In addition to the metrics above, the following metric displays only when your company's token usage has exceeded the number of pre-committed tokens:
Tokens Overage: Calculates the difference between the amount of tokens spent so far and the number of tokens allotted at the start of the contract. If an overage occurs, LiveRamp would calculate the number of tokens that would have been used and apply an overage fee per token.
Column Headings on the Access Tab
The Access tab has the following columns:
Column | Description |
|---|---|
Service Type | The type of service performed on the data rows |
Product Area | The LiveRamp product area through which the data was accessed |
Number of Rows | The total rows included |
Billable | Indicates whether the action is billable. If the value is "No", no charge will incur even if the respective Tokens column is populated. |
Rows per Token | The number of rows covered per token, based on your company's tier level |
Tokens | The cost in tokens |
To view more information on all applicable services under Access and their respective product area, see "Access and Usage".
Column Headings on the Usage Tab
The Usage tab has the following columns:
Column | Description |
|---|---|
Service Type | The type of service performed on the data units |
Product Area | The LiveRamp product area where the action/service occurred |
Number of Units | The total units included |
Billable | Indicates whether the action is billable. If the value is "No", no charge will incur even if the respective Tokens column is populated. |
Units per Token | The number of units covered per token, based on your company’s tier level |
Tokens | The cost in tokens |
To view more information on all applicable services under Usage and their respective product area, see "Access and Usage".
The definition of "units" varies depending on the service type:
Records Queried (Clean Room): Records subject to a LiveRamp Clean Room query or question
Records / Segment / Destination: The amount determined by summing the maximum number of records for every unique destination account a segment is distributed to over the month. See "Understanding the Records / Segments / Distribution Metric" to learn more.
Note
If the same record appears in multiple segments that are combined within LiveRamp to create a single audience file for distribution to a destination, it will only be counted once for that destination.
If the same record is sent to the destination multiple times using separate files, or appears multiple times in an audience file combined outside of LiveRamp, then the record will be counted once for each time it is distributed to the destination.
Enterprise IDs per Graph: The maximum number of Enterprise IDs present in a company’s Identity Engine graph(s) at the end of each month