Why are MTUs divided into Web, App, and 1st Party categories?
To ensure fair billing, MTUs are categorized as Web, App, and 1st Party. This separation means the 1st Party users shared via integrations do not consume the MTU limits of other products and are calculated at a more favorable cost. Similarly, users on the website are not counted as App MTUs unless they also engage on the app, helping avoid sudden cost spikes from a single source.
Does every event impact data point consumption?
Some events do not affect data point usage. You can check the list in the Data Points to see which events are counted in the data point allocation.
If a user profile is updated multiple times within the same month, does it count as multiple MTUs?
No, multiple updates to a user profile within the same calendar month count as a single Monthly Tracked 1st Party User (MTU). Even if the profile is updated on different days within the month, it is still counted as one MTU.
What integration methods contribute to the 1st Party User MTU count?
Data imports through upserting, user data ingestion, and segment uploads contribute to updating 1st Party User profiles and are included in the monthly MTU count.
How are MTUs calculated for customers using multiple domains?
Insider calculates the total MTU usage across all domains for customers with multiple domains under one limit. A breakdown of usage by each domain is provided, but the total is compared to a single limit.
What happens if a customer has multiple products with different contract periods?
If a customer has multiple products with different contract periods, meaning one product has a monthly limit and another has a yearly limit, they can see them separately as defined in their contract.