Lytics leverages a credit-based pricing, where a credit represents an update to a user profile. Most events in Lytics consume 1 credit, so the number of credits you need depends on how much data you send to Lytics.

Inbound events refer to data received by Lytics from the web, API, or any managed integrations. They are consumed at a rate of 1 credit per event. For example, if you have 100 page views, it would consume 100 credits, assuming no additional data collection has been configured. All inbound events would consume 1 credit, regardless of how big the event is or how many profile attributes it updates.

Cloud Connect sync events are a special class of inbound event and refer to rows synchronized between your data warehouses and Lytics. They are consumed at a rate of 1/2 credit per updated row. For example, if your query returns 1,000 rows, it would consume 500 credits. Subsequent syncs will only consume credits for the difference in records from the previous sync.

Overages are handled differently depending on what account tier you are on:

Enterprise: For our enterprise plans we generally do not charge per month style overages. We work with you to understand your usage and ensure you are on the right plan. If you are consistently over your credit limit, we will work with you to move to the appropriate plan at renewal.

Growth: Growth plans which continually exceeded their monthly allocation will be automatically enrolled in a higher credit model at the rates outlined above.

Developer: Developer plans which exceeded their monthly allocation will be automatically throttled upon reaching event caps. This throttle will prevent further credit consumption until the next billing cycle.