FAQ about Attributes and Events

Prev Next

Can I edit the default attributes?

Editing default attributes is not allowed because some products rely on them as default logic.

Can I edit the events and event parameters?

Yes, you can edit default and custom events and parameters. You can edit events by adding additional parameters to them.

Can I delete an attribute, event, or event parameters?

No, you cannot delete any attributes, events, or event parameters. If you require such an option, reach out to the Insider One team.

Is the event graph affected by event Time to Live?

No. The event graph isn’t tied to Time to Live (TTL). It simply displays daily logs of collected events. Even if a custom event hasn’t been collected for several months, the graph won’t automatically show “0” due to TTL; it only reflects actual collection activity for each day.

Does the attribute graph depend on the user's TTL or on the user's existence?

No. The attribute graph also isn’t connected to TTL or user retention. It visualizes daily collection logs. If an attribute existed for a user who was later deleted or expired due to TTL, that doesn’t retroactively change the historical data shown in the graph—it still represents what was collected on that day.

Can I toggle “Show on Segment” for default attributes, such as “last purchase date”?

No. Default attributes are system-defined and cannot be toggled on or off. You can only modify their display name if necessary. If you need changes beyond that, contact the Insider One team.

For example, the last purchase date attribute is controlled via the purchase behavior tab and is intentionally disabled for manual editing or toggling.

How long does it take for new values to appear on the Attributes or Events page?

Once the value appears in the user profile, it’s already counted in the attributes or events metrics. In other words, as soon as ingestion completes and the profile reflects the update, the metrics page will also show it; no extra delay beyond standard processing time.

How can I update an attribute for the user?

You can update an attribute for a user via: 

The Static Segment requires an identifier. The Upsert API can be used with both profile ID and identifier.

If the attribute you want to update is an identifier, you should update the identifier.

What happens if I change the data type of an attribute or an event parameter?

When an attribute’s or event parameter’s data type is changed, Insider One automatically converts the existing values in the database to match the new type.

For example, consider an attribute defined as a String that contains values such as True and False. While the attribute is of type String, segmentation will display operators relevant to string-based fields, such as:

  • contains

  • does not contain

  • is exactly

  • is not exactly

If the same attribute is later converted to the Boolean type, its values are converted accordingly. The next time you access segmentation, the available operators will change to those applicable to Boolean fields, such as:

  • is

  • is not

  • is empty

  • is not empty

This behavior ensures that segmentation logic always aligns with the attribute’s current data type and maintains consistency across the system.

Is there a limit on the number of events I can add to an event parameter?

There is no limitation on the number of events you can connect to a single event parameter.