Skip to main content

Change Management

Event versioning​

Each event in your data includes a VERSION number that tracks how the data structure has evolved over time. As we improve and update our analytics system, the information we capture may change, and version numbers help ensure your data remains consistent and reliable.

How it works: When we make changes to what information an event captures, we assign it a new version number. This means newer events of the same type might have slightly different version numbers than older ones in your historical data.

Understanding Version Numbers​

We use a three-part numbering system (like 2.3.1) that tells you what kind of changes were made:

  • Major version (the first number - "2") - Changes when we make significant updates that might affect how you use the data
  • Minor version (the middle number - "3") - Changes when we add new information without affecting existing data
  • Patch version (the last number - "1") - Changes for small updates that don't meaningfully change the data structure

Types of Changes We Track​

Major changes that might affect your analysis (breaking changes):​

  • Removing information that was previously included
  • Changing how existing information is formatted or categorized
  • Making required information optional

Minor changes that enhance your data (non-breaking changes):​

  • Adding new information to events
  • Making optional information required (providing more complete data)

What This Means for You​

  • Complete documentation: We maintain detailed documentation for every version of every event type, so you always know exactly what information is available.
  • Data consistency: Version tracking ensures you can reliably analyze both historical and current data, understanding any differences between time periods.

Table Schema Versioning​

The main session_events_view table you work with always contains the most current version of your analytics data. We automatically maintain and update this table to ensure you have access to the latest features and improvements.

Preserving Historical Data​

While we keep your main data table current, we also preserve historical versions so your past analysis remains accurate and accessible.

How this works: We create separate, dated versions of your data table with names like:

  • session_events_view (always the current version)
  • session_events_view_2_3_1 (historical version from an earlier time period)
  • session_events_view_2_4_0 (another historical version)

Important: These historical tables aren't just frozen snapshots. They continue to receive new, current data - but only the information that matches their original structure. This means you get fresh data in the format you're familiar with.

Automatic Updates​

When we release improvements to our analytics system:

  • What we do: We automatically update your main session_events_view table to include the latest enhancements and features.
  • What stays the same: Historical versions remain unchanged, ensuring your past reports and analysis continue to work exactly as they did before.

Example Timeline​

If we released a new version (2.4.1) today:

  • Your session_events_view table would automatically use the new 2.4.1 features
  • The session_events_view_2_4_0 table would remain available with the previous version's structure
  • You could continue accessing both current and historical data as needed

What This Means for You​

  • Always current: Your primary data table automatically includes the latest analytics capabilities without any action required from you.
  • Reliable history: Your historical analysis and reports remain accurate and accessible, even as we enhance the system.
  • Seamless transitions: Updates happen automatically in the background without disrupting your ongoing analysis work.
Table nameSchema version
session_events_view2.4.0 (ie. 'latest')
session_events_view_2_4_02.4.0
session_events_view_2_3_12.3.1