Our recent redesign simplifies the data transfer experience by combining raw and modelled data sources into a single object - data feeds. We’re gradually releasing this new feature to our customers.
If you see Data Feeds in the left navigation sidebar, you're in the right place. If not, go here.
Are you seeing this error message when creating a metric?
This article explains why this message displays and what you can do about it.
Why am I seeing this error message?
You'll see this message if your data feed includes a LOT of rows. To respect fair use limits and enable optimum performance for all customers, we limit the number of rows of data that can be ingested per hour, per account. This limit is applied during metric creation and when you choose to delete and re-import data for a metric. If you see this error message, it means you have exceeded your hourly data ingestion limit.
What can I do to fit within the limit?
When creating data feeds for custom metrics, we strongly recommend adding a date column. This is especially true for larger data feeds. Learn more about creating custom metrics.
If the data feed doesn’t include a date column, we need to ingest the entire feed when a metric is created (and on every refresh) which may cause you to hit the maximum ingestion limit.
If the data feed includes a date column, we group the rows in the data feed into daily buckets using the selected time dimension and count the number of rows in each daily bucket. The daily ingestion value for the custom metric is calculated using the single, highest row count of all the daily buckets, instead of a total of ALL the rows. This significantly reduces the data being ingested and makes it less likely you'll exceed the maximum limit.
To fit within the data ingestion limit, try:
- Reducing the number of rows in your data feed, for example, by applying filters when querying your data for custom metrics.
- Adding a date column to your data feed if it doesn't have one.