Credit Consumption Tables.

Use these tables to calculate how many entitlement credits are consumed for various types of usage (November 2023)

Standard Entitlement Credit Consumption Table

Step 1: For each type of usage in column (1), determine the quantity of usage using the units in column (3).  
Step 2: Divide the quantity from Step 1 by the number in column (2) and multiply by the number in column (4).  
Sept 3: The resulting credits consumed is the greater of the result of Step 2 or the number in column (5).
(1)
This type of usage,
(2)
With this usage quantity,
(3)
And this 
unit of usage,
(4)
Consumes this many credits.
(5)
Minimum Credits Consumed
aMDP Usage Credits.  Each base aMDP license includes 3 aMDP Usage Credits.
aMDP Record Processing (OLAP)
        
Records ingested
1
billion
1
1
Records discarded at initial ingestion
4
billion
1
1
Records distributed
10
billion
1
1
aIO API Requests (OLTP)        
aIO GET API Request 800 million 1 1
aIO PUT API Request 200 million 1 1
aGM API Requests (OLTP)        
aGM GraphDS API PUT for each root node neighbor 200 million 1 1
aMDP Storage Credits. Each base aMDP license includes 2 aMDP Storage Credits.
aMDP Storage (OLAP) 5 TB 1 1
aIO Storage (OLTP) 500 GB 1 1
aMDP Connection Credits. Each base aMDP license includes 5 aMDP Connection Credits.
Commercial Partner Integration License
1
configuration
4
1
Connection Instance
1
configuration
1
1
Note: A Connection Instance is a unique combination of a YAML job configuration and credentials for a Commercial Partner Integration or enterprise integration that necessitates a separate job execution for any given period.   For example, a Commercial Partner Integration for a single account or credential with that partner consumes 5 Connection Credits per month: 4 for the License and 1 for the Connection Instance.
aUT Usage Credits. Each base aUT license includes 1 aUT Usage Credit.
aUT Tag Request for Atomic Tags (e.g., image or simple JS)
1
billion
1
1
aUT Tag Request for Container Tags
1
billion
4
1

Special Entitlement Credit Consumption Table

(1)
This type of usage,
(2)
With this usage quantity,
(3)
And this
unit of usage,
(4)
Consumes this many credits.
(5)
Minimum Credits Consumed
aMDP Usage Credits.  Each base aMDP license includes 3 aMDP Usage Credits.
aMDP Record Processing (OLAP)
        
Records ingested with one data subject attribute per row
10
billion
1
2
Records ingested or distributed using a streaming endpoint
1
billion
2
1
Note:  Special pricing applies to Unsorted Collation Input Records (CIR) processed in excess of 3 Billion for every aMDP Usage Credit billed for ingestion records.  For the purposes of this calculation, every 10 Billion pre-sorted CIRs count as 1 Billion Unsorted CIRs.
Note: Special pricing applies to Data Mart records written (i.e., in Parquet format files) in excess of 3 Billion for every aMDP Usage Credit billed for ingestion records.
Note: Special pricing applies to ingestion records or data mart records with more than 250 columns, rows or fields.
aIO API Requests (OLTP)        
Sum of KB of data for each aIO API Request after 1 KB
800
million
1
1
aIO API Request Transaction Logging
2
billion
1
1
aMDP Bandwidth Credits.  
Data transfers within a CSP (eg between regions or AZ's)
10
TB
1
1
Data egress from a CSP (eg between CSPs or out to internet)
3
TB
1
1
aMDP Connection Credits. Each base aMDP license includes 15 aMDP Connection Credits.
Connection Job Execution
100
each
1
1
Note: Connection Job Execution metering may consume fewer credits than per Connection Instance metering. For example, three job configurations that each execute twice daily might execute a total of 180 times a month and consume 2 Connection Credits combined if applying Connection Job Execution metering, instead of 3 credits with Connection Instance metering.  Aqfer applies the method that consumes the fewest credits for each Connection Instance. For example, a job configuration that executes hourly in addition to a configuration executing daily for each of two partner access credentials would consume 2 Connection Credits (1 credit for the hourly job that ran 720 times per month and 1 credit for the two other jobs running 60 times a month combined), instead of 3 credits using only Connection Instances or 8 credits using only Connection Job Executions.
aMDP Serverless Query Credits. Each base aMDP license includes 1 aUT Serverless Query Credit.
Serverless Query Data Scanned (eg., AWS Athena, GCP BigQuery, Azure Synapse Serverless)
20
TB
1
1
aUT Usage Credits. Each base aUT license includes 1 aUT Usage Credit.
Tag Requests which add the Active Statistical ID option 
1
billion
2
1
Note: In addition to credits consumed for Tag Requests. E.g., a billion atomic JS tag requests consume 3 Tag Usage Credits.
aUT Bandwidth Credits.  
Client-supplied payloads (e.g., JS files) delivered with an Aqfer tag via the Akamai CDN
1
TB
1
1