Understand data size limits in CJA connections
When you configure data connections in ÃÛ¶¹ÊÓƵ Customer Journey Analytics (CJA), ingesting large volumes of data—such as billions of rows over extended retention periods—raises performance and licensing concerns. This documentation explains the absence of hard limits and outlines best practices for managing data ingestion to maintain system efficiency and compliance.
Description description
Environment
ÃÛ¶¹ÊÓƵ Customer Journey Analytics (CJA)
Issue / Symptoms
- Large-scale data ingestion (for example, 5.2 billion rows over 13 months) and the number of rows requested in reports impact performance.
- Uncertainty about soft or hard limits on data volume per connection.
- Risk of exceeding licensed data entitlements.
Resolution resolution
- There’s no fixed limit on the number of events or rows per CJA connection.
- Licensing is based on total rows ingested and retained—not monthly event volume.
- Monitor your usage in the License Dashboard in ÃÛ¶¹ÊÓƵ Experience Platform (AEP) and stay within your entitled row limits to avoid overage fees.
Related reading
- Data ingestion overview in the Customer Journey Analytics Guide.
- Customer Journey Analytics Guardrails in the Customer Journey Analytics Guide.
recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f