Skip to main content

Understanding LiveRamp Billing

Learn about LiveRamp's token-based billing model and its metrics to understand how your usage is calculated on the Usage Reports page.

To view the Usage Reports page, select AdministrationUsage Report from the navigation pane.

Note

This billing model is available in an early limited release.

Access and Usage

Your LiveRamp usage is calculated based on two main units of measurement: Access and Usage.

  • Access: The amount of data (records) your organization accessed, ingested, or resolved using LiveRamp. For example, if you connect your data source to LiveRamp Clean Room and 500,000 rows are resolved to RampIDs, 500,000 records are considered to have been accessed.

    Note

    For more information on the definitions of records accessed, ingested, and resolved, see the "Metrics Definition" section below.

  • Usage: The additional actions performed against the data. For example, if you query against 100,000,000 rows in Clean Room, your data usage increases by 100,000,000 records.

The table below shows the services that can be included in your usage report and the corresponding unit of measurement.

Product Area

Service Type

Unit of Measurement

Activation

Records Ingested

Access

Records / Segment / Destination

Usage

Analytics Environment

Records Ingested

Access

Clean Room

Records Resolved

Access

Records Queried

Usage

Customer Profiles

Records Ingested

Access

Records / Segment / Destination

Usage

Identity Engine

Records Ingested

Access

Enterprise IDs per Graph

Usage

Identity Resolution and Translation

Records Accessed

Access

Measurement Enablement

Records Ingested

Access

Metrics Definition

The terms used in the table above are defined as follows:

  • Record: A single unit of access, such as a row of data in a file, a single call to an API, or a transaction through a cloud native application, before deduplication

  • Records Ingested: Records that a company has ingested into LiveRamp in order to use a LiveRamp service. Records ingested exclude the following:

    • Records that were previously ingested and resubmitted, but flagged for exclusion (for example, as a result of opt-out or deletion requests)

    • Records that were previously ingested into a LiveRamp platform and resubmitted to another LiveRamp platform (for example, a records transfer from one platform to another

  • Records Accessed: Records that LiveRamp accessed and resolved to RampID in order to use a LiveRamp service

  • Records Resolved for Clean Rooms: Records that have been resolved to RampIDs within LiveRamp Clean Room

  • 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

  • Records / Segment / Destination: The amount determined by multiplying the number of records per segment by the number of destinations, where:

    • Records per segment = the maximum number of records configured for distribution within each segment over a month

    • Number of destinations = the number of destinations that the company has distributed the segment(s) to as of the end of a month

      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.

  • Records Queried: Records subject to a LiveRamp Clean Room query or question

Tokens

Tokens are LiveRamp's unified secondary currency used to track your consumption across products. You can purchase a lump sum of tokens, which can lower overall costs, or opt for a pay-as-you-go model suitable for fluctuating usage. As your LiveRamp usage increases, your token balance will decrease.

The conversion rate per token (the volume of usage a single token covers) is contractually agreed upon based on your tier level. You can always request more tokens through contract amendments if needed before the end date of the contract.

If an overage occurs and you continue to use LiveRamp, LiveRamp would calculate the number of tokens that would have been used and apply an overage fee per token. Any unused tokens remaining after your contract end date will not be carried over or refunded.

Tier Levels

Tiers are predefined, contractual commitments that define your token conversion rate and usage volume. LiveRamp offers 12 tier levels, each with a different token conversion rate. In general, the greater the volume of rows, the higher the tier level, and the better the conversion rate.

Refer to the table below to view the token conversion rate per level.

Tier

Metric

All Platforms (Access)

Identity Engine (Usage)

Activation (Usage)

Clean Room (Usage)

12

1 token =

1,550,000

75,000

1,400,000

330,000,000

11

1 token =

1,150,000

50,000

1,000,000

285,000,000

10

1 token =

845,000

40,000

710,000

250,000,000

9

1 token =

635,000

30,000

535,000

215,000,000

8

1 token =

480,000

25,000

400,000

190,000,000

7

1 token =

360,000

19,000

300,000

165,000,000

6

1 token =

270,000

15,000

225,000

140,000,000

5

1 token =

205,000

12,200

170,000

125,000,000

4

1 token =

145,000

9,800

120,000

110,000,000

3

1 token =

100,000

7,800

85,000

95,000,000

2

1 token =

71,000

6,250

60,000

80,000,000

1

1 token =

50,000

5,000

42,000

71,000,000

Example Scenarios

Note

  • Token calculations are rounded down to two decimal points. For example, if your company is on tier 11 and has performed ingestion on 2,000,000 rows, the token usage is calculated as: 2,000,000 / 1,150,000 = 1.73 tokens.

  • The minimum billable token amount is 0.01. This means you will not be charged for token usage below 0.01.

Tier Level

Scenario

Access Token Calculation

Usage Token Calculation

Total Tokens Spent (for the month)

3

You connect your data in LiveRamp Clean Room where 100,000,100 records are resolved to RampIDs. You then run a query against 1,000,000 of those records in Clean Room.

100,000,100 / 100,000 = 1,000 (rounded down from 1,000.001)

1,000,000 / 95,000,000 = 0.01

1,000.01

8

You have a workflow in Identity Engine with a maximum number of enterprise graphs of 50,000. In that same month, you distributed 2,800,000 to two destinations.

50,000 / 25,000 = 2

(2,800,000 x 2) / 400,000 = 14

16

12

You ingested 3,000,000 records to be used for the Analytics Environment. In that same month, you send 1,250,000 records to LiveRamp for Measurement Enablement.

(3,000,000 / 1,550,000) + (1,250,000 / 1,550,000) = 2.73

0

2.73