--- title: "FAQ about Attributes and Events" slug: "faq-about-attributes-and-events" description: "Answers common questions about editing, deleting, TTL behavior, and changing data types across Insider One's attributes, events, and event parameters." tags: ["events and attributes", "attributes and events", "faq about events", "faq about attributes"] updated: 2026-10-22T06:33:43Z published: 2026-10-22T06:33:43Z canonical: "academy.insiderone.com/faq-about-attributes-and-events" --- > ## Documentation Index > Fetch the complete documentation index at: https://academy.insiderone.com/llms.txt > Use this file to discover all available pages before exploring further. # FAQ about Attributes and Events ### 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? You can delete custom attributes. Default attributes, identifier attributes, events, and event parameters cannot be deleted. To delete a custom attribute, contact the Insider One team. Deletion removes the attribute's values from every user profile and cannot be undone. For details, see [Delete a custom attribute](/v1/docs/create-a-custom-attribute). For events and event parameters, you can pause their ingestion on the Attributes and Events page, and you can hide event parameters from segmentation. ### Is the event graph affected by event Time to Live? No. The event graph isn’t tied to [Time to Live (TTL)](/v1/docs/data-retention). 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: - [Static segment](/v1/docs/create-a-static-segment) - [Upsert API](/v1/docs/upsert-user-data-api) The Static Segment requires an identifier. The Upsert API can use either a profile ID or an identifier. > [!NOTE] > If the attribute you want to update is an identifier, you should [update the identifier](/v1/docs/update-identifiers-api). ### What happens if I change the data type of an attribute or an event parameter? [UCD](/v1/docs/unified-customer-database-ucd) doesn't automatically convert existing values when you change the data type. As a result, an existing value is displayed only if it already fits the new data type as it is. If it doesn't, the user appears not to have this attribute. For example, you change the **birth_month** attribute from **String** to **Number**: | Stored value | After the change to Number | | --- | --- | | 9 | Displayed, because 9 is a valid number. | | September | Not displayed. The user appears to have no value for **birth_month**. | After the change, segmentation shows the operators for the new data type. For example, a String attribute offers operators such as *contains* and *is exactly*. After you change it to Boolean, it offers operators such as *is*, *is not*, *is empty*, and *is not empty*. Before you change the data type of an attribute that's already collecting data, check that your existing values are compatible with the new type. Segments, journeys, and campaigns that use the attribute only include users whose values can be displayed in the new type. ### 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. ## Related - [Attributes and Events Page](/attributes-events-page.md) - [Create a Custom Attribute](/create-a-custom-attribute.md) - [Attributes and Events: Use Cases](/attributes-events-use-cases.md)