A data point is the fundamental unit of behavioral and profile data in Insider One. Every event recorded and every attribute stored against a user profile contribute to your monthly data point allocation. This reference defines what affects your data point consumption, what doesn't, and how to optimize your tracking strategy.
What is a data point?
Any piece of information that Insider One stores against a user profile or session is a data point. This includes user actions (events) and user properties (attributes). Data points are the engine behind segmentation, personalization, and reporting, and they count toward your monthly contracted allocation.
Not every collected signal affects your monthly data point consumption. Insider One distinguishes between data points that do impact your allocation and data points that are collected by default and do not. Campaign interaction signals, such as email opens, push clicks, and in-app interactions, do not affect your data point usage.
Data Point Consumption
You can select which events and attributes to collect based on your data point allocations. Some events and attributes are collected by default and do not impact your data point usage.
See below for a detailed breakdown of the events and attributes that affect your monthly data point consumption.
Category | Definition | Does it affect your data point consumption? |
|---|---|---|
INTERACTION LEVEL | ||
InApp Notification Interactions | Interactions (*e.g., open, close, click*) on InApp campaigns created via Insider One's InOne panel | No |
App Push Interactions | Interactions (*e.g., open, close, click*) on App Push Notifications created via Insider One's InOne panel | No |
Email Interactions | Interactions (*e.g., open, close, click, bounce, spam*) on Email campaigns created via Insider One's InOne panel | No |
Session Start | Start time of the session | Yes |
Session End | End time of the session | Yes |
Architect User Journey History | Users' interactions on an Architect Journey | No |
Sign Up Confirmation Events | A completed sign-up flow | Yes |
Lead Collection Events | A completed registration/subscription form | Yes |
ACTIVITY LEVEL | ||
Product View History | History of all products visited by user | Yes |
Category Visit History | History of all categories visited by user | Yes |
Pageview History | History of all pages tracked by partner and visited by user | Yes |
Purchase History | History of all purchases made by user | Yes |
Shopping Cart History | History of all shopping cart actions of user | Yes |
Last Purchased Product Attributes | Details of the last purchased product of user | No |
Last Abandoned Cart Attributes | Details of the last abandoned product by user | No |
Last Visited Product Attributes | Details of the last visited product by user | No |
Last Email Open Date | Last email interaction date of the user | No |
USER LEVEL | ||
Age | Age information of the user | Yes |
Birthday | Birthday information of the user | Yes |
City | City information of the user | Yes |
Country | Country information of the user | Yes |
Email Address | Email address of the user | Yes |
GDPR Opt-in | User's allowance for their personal data to be stored in a database | Yes |
Email Opt-in | User's allowance to receive marketing emails | Yes |
Phone Number | Phone number of the user | Yes |
SMS Opt-in | User's allowance to receive SMS | Yes |
Gender | Gender information of the user | Yes |
Language | Language information of the user | Yes |
Username | Account username of the user | Yes |
DEVICE LEVEL | ||
Model | Device model | No |
Carrier | Active carrier on the device | No |
App Version | Current app version on the device | No |
Os Version | Operating system of the device | No |
Screen Width | Screen width of the device | No |
Screen Height | Screen height of the device | No |
Time zone | Time zone of the device | No |
Device Language | Language of the device | No |
SDK Version | Current SDK version on the device | No |
Browser Version | Browser Version of the device | No |
CUSTOM | ||
All Custom Events | Custom events that are integrated by and are specific to the partner | Yes |
All Custom Attributes |
| Yes |
Optimization strategies
Data point consumption accumulates with every write to a user profile or event log. The following patterns help reduce unnecessary consumption without sacrificing the data quality needed for segmentation and personalization.
Send only changed data
Every attribute update against a user profile affects your data point consumption, even if the value is unchanged. Before writing to a profile, diff the incoming payload against the current state and send only fields that have genuinely changed.
Audit your custom event schema
Custom events fully affect your data point consumption. Review your event taxonomy periodically to identify events that are being tracked but not used in any segment, journey, or report. Decommissioning unused event types directly reduces your monthly usage.
Batch writes where possible
For server-side integrations, batch profile and event updates into a single API call rather than issuing one call per attribute or event. This does not reduce the number of data points recorded but ensures writes are consistent and avoids duplicate submissions from retry logic.
Device-level data (model, OS version, carrier, SDK version, browser version, screen dimensions, timezone, and device language) is collected automatically by Insider One. Avoid replicating this data into custom attributes. Doing so creates unnecessary data load and duplicates information that is already available natively.
Monitor your allocation
Your contracted monthly data point allocation and current consumption are visible in the InOne panel. Contact your Insider One account team to:
Review your current monthly allocation and data point usage to date.
Identify the top event types and attributes driving consumption in your account.
Get tailored guidance on tracking strategy and schema optimization.
Explore allocation upgrades if your usage consistently approaches your contracted limit.