Event Versions
When you create and activate an Activity, it is saved together with its corresponding Event as a version. Any changes later made to this Activity are also saved, and a new version of the Event is created.
This is what allows you to keep using historical Events on a Profile even after the source Activity has changed, and to choose which version of an Event a Segment should look at.
In this Article
What is an Event Version?
An Event Version is a snapshot of the fields an Event carries at a specific moment. When you create a Form, a Survey, a Product Views Activity or a Custom Event, Apsis One stores the initial structure as version 1 of that Event. When you edit the source — for example by adding a new field to your Form — Apsis One stores the updated structure as a new version.
Both versions remain available:
Historical Events stay attached to Profiles with the version they were collected on.
New Events are collected with the latest version.
In the Segment Builder, you choose which version to evaluate against.
When a new version is created
Not every Event is versioned. New versions are created when the underlying Activity or Event template can have its fields changed by you:
Forms Event Versions
If at some point you edit your Form to start collecting a new Attribute, or to remove a field from the Form, a new version of the Form – Submit Event is created to match your changes.
Custom Event Versions
If you add, edit or remove Event data fields on a Custom Event you previously created in the Data Model, a new version of your Custom Event is created. See Custom Events for editing details, including the 1-hour edit lockout that applies after each save.
Product View Event Versions
If you remove or map a new visual element in your Product Views Activity, a new version of the Product View – Collect Event is created.
Other versioned Events
The same versioning behaviour applies to:
Survey – Submit Events (one version per Survey Activity)
Event Tool register – Collect Events (one version per Event Tool registration page)
Website form – Collect Events (one version per Website Tool form Activity)
💡 Good to know: Each of these Events carries a unique identifier per Activity. That is why you may see, for example, several entries for "Product View – Collect" in pickers — one for each Product Views Activity you have set up.
Selecting a version in the Segment Builder
In the Segment Builder you can choose to use the previous or present version of an Activity's Event for your Segment.
When you build a Segment with one of these versioned Events, you will see a Version drop-down menu where you select which version of the Event to evaluate.
Picking the right version matters when your fields have changed: a Segment built on version 2 of an Event will only match Events collected on version 2 (and on later compatible versions). Older Events collected on version 1 will still exist on the Profile timeline but will not be matched by that Segment condition.
Rules for changing Events safely
To keep Segments and Marketing Automation Flows working when you edit an Activity or Custom Event, follow these rules:
Change you want to make | Safe? | What happens |
Add a new field | ✅ Safe | A new Event version is created with the extra field. Existing Segments and Flows continue to work and ignore the new field unless you start referencing it. |
Rename the Event display name | ✅ Safe | The name change is cosmetic. The underlying Event identifier does not change. |
Remove an existing field | ⚠️ Risky | A new version is created without the field. Any Segment or Flow that references the removed field can no longer evaluate it. Existing Events stay on the Profile, but new Segments and Flow conditions on that field will fail to match. |
Change a field's type (for example Text → Number) | ⚠️ Risky | Treated like removing the old field and adding a new one. Existing references break. |
⚠️ Important: Adding fields is always backwards-compatible. Removing fields is not. Before removing a field, search your Segments and Marketing Automation Flows for any condition that uses it, and update or remove those conditions first.
Use Cases
Re-targeting Profiles who submitted an older Form version
You changed your newsletter sign-up Form to capture a new "industry" field. Profiles who signed up earlier do not have that field. In the Segment Builder, pick the previous version of the Form – Submit Event to target the historical sign-ups.
Switching a Flow over to a new Form version
You released a redesigned Form with new fields, and want your welcome Flow to use the new version's data. Update the Listen Node to reference the latest version, and update any Segment conditions in the Flow to match.
Cleaning up a Custom Event
You added a field to a Custom Event during testing and want to remove it. Before removing it, check that no Segment or Flow uses the field. Make the change, wait for the 1-hour edit lockout to clear, and verify your Segments still return Profiles as expected.
Troubleshooting
❓ My Segment used to work, but it stopped returning Profiles after I edited the Form / Custom Event.
Editing the source created a new Event version. If the Segment was built on the previous version, it may no longer match new Events, or it may have lost a field reference. Open the Segment and check the Version drop-down for the affected Event. Re-point the Segment to the current version, or restore the removed field.
❓ My event-triggered Marketing Automation Flow runs, but Profiles fail when they hit a Segment-match step.
This is the same root cause. The Listen Node is firing on the latest Event version, but a Segment condition inside the Flow still references an older version (or a field that no longer exists). Update the Segment to use the current version.
❓ I edited my Custom Event but cannot edit it again.
After each save, Custom Events are locked for one hour. The Event also cannot be used in new Activities during that hour. Wait it out, then refresh.
❓ I see multiple versions of "Product View – Collect" in the Segment Builder.
Each Product Views Activity creates its own version of the Event. If you have several Product Views Activities running on different parts of your site, you will see one entry per Activity. The same is true for Forms, Surveys and Event Tool registrations.
❓ How long are older versions kept?
Older versions remain available as long as you have Events collected against them on Profiles. The Events themselves follow the default Time to Live (TTL) for that Event type.
What's Next?