Managing Data Output the Smart Way

Data Output is one of the most common topics we see in conversations with TagoIO users. While it's a simple concept, misunderstanding how it works can quickly impact your application performance and even your business operations.

What is Data Output?

Think of Data Output as "data leaving" the TagoIO platform. Every time a variable record is read from storage, it counts as one transaction. This includes running an Analysis, exporting documents, and retrieving historical data using external integrations via the API.

Here's where confusion often starts: many users associate consumption only with incoming data from devices. In practice, Data Output is driven by how frequently data is accessed and visualized, even when no new data is arriving.

Data Output vs. Data Output for Dashboards

It's important to understand that TagoIO tracks these as two separate limits. Data Output is counted for each register read from a device's data storage. This applies to Analyses, API calls, and data exports. Data Output for Dashboards is a separate counter that tracks data displayed when users load dashboards in TagoIO Admin or TagoRUN. Data consumed by dashboards will not be counted against the Data Output Service, and you are not billed for Data Output for Dashboards. Each limit resets monthly, and you can monitor both in your Admin panel under 'Hard Limits'.

Why Data Output issues are so common

Our Support team sees a consistent pattern: we typically hear from more users toward the end of the month, as accounts get closer to their limits. In most cases, they come from unoptimized access patterns like Analyses running without device filters and exports pulling more data than needed.

TagoIO sends multiple alerts when consumption approaches limits, giving teams time to act before applications are affected.

Smarter ways to use Data Output

Be specific in Analyses. If possible, always add as many filters as possible to reduce the amount of unnecessary data you pull from your devices. Without this filter, your Analysis may pull more variables than necessary, dramatically increasing consumption. This small configuration makes a huge difference in accounts that manipulate lots of devices with long data histories.

Filter exports carefully. Before exporting, consider which variables are truly required. Do you need the last year of data, or would the last month suffice? Filtering variables and time windows keeps exports lighter and avoids waste.

Use metadata smartly. Instead of storing many separate variables, group related values inside a single metadata object. One read returns multiple pieces of information, improving efficiency.

TagoDeploy: If your application requires more flexibility than standard plans offer, TagoDeploy provides a dedicated instance with no shared resource limitations. You define your own RPM, bucket sizes, and more.

Small changes, big impact

Data Output limits encourage efficient usage and predictable application behavior. Avoiding issues usually comes down to simple adjustments in how data is read, filtered, and displayed. These optimizations also improve the experience for your end users, making dashboards load faster and applications more responsive.

Have you found other ways to optimize Data Output? Share your tips in the TagoIO Community.