Fair Usage
Simon has usage policies and best practices that come standard with the Core CDP Platform. The two primary reasons for these rules and best practices are to:
- Enable you to see what value you're getting from your data
- Ensure your account has the data and the live flows you need to support your marketing strategy
What are these usage rules and best practices?
- Custom Configuration: Simon can customize the Core CDP Platform based on your unique needs. For example:
- Daily Pipe Run: 2x per day
- Data Retention Increase: changing the lookback periods to your event-based datasets may increase the volume of data Simon is making available to you
- Fair Usage: Limits on our Core CDP Platform that can't be adjusted. If you require an increase to these limits, a customized Enterprise CDP Platform is required.
To customize your account, contact your account manager.
Standard usage rules
Category | Type | Volume included in the Core CDP Platform | Notes |
---|---|---|---|
Custom Configuration | Daily Pipe Run | 1x per day | |
Custom Configuration | Data retention | 3.0 bn reference data rows | |
Fair usage | Total Segments | 2,000 | |
Fair usage | Live Flows & Journeys | 400 | Aggregated across Flow Types |
Fair usage | Live Datasets | 250 | Aggregated across Dataset Types |
Fair usage | Total Attributes | 1,600 | Ingested from your Data Sources or created in Simon |
Per-dataset total cell limitations
Used in Content? | Incremental | Overwrite |
---|---|---|
No | 2.0 billion | 200.0 million |
Yes | 200.0 million | Not Permitted |
These limits are on the number of total cells (i.e. number of rows multiplied by number of columns) in any individual contact event or contact object dataset. The 2 billion limit for incremental datasets not used in content, for example, means you can have a 4 column table of 500m rows or a 20 column table of 100m rows.
Updated 3 months ago