Skip to main content

​
The Challenge

Businesses need to track how their key metrics evolve over time to understand trends, make informed decisions, and comply with reporting requirements. However, maintaining accurate historical records presents several challenges:
  • Capturing point-in-time snapshots of metrics
  • Tracking changes in dimension attributes over time
  • Managing slowly changing dimensions (SCD)
  • Ensuring data consistency across time periods
  • Creating reliable trend analysis
With Nekt, companies can implement proper historical tracking using SCD Type 2 methodology, maintaining a complete history of changes while enabling powerful trend analysis and historical reporting. This approach ensures data integrity and provides valuable insights into business performance over time.
Teams can now build comprehensive historical records of their KPIs, tracking changes in both metrics and dimension attributes. This enables accurate trend analysis, year-over-year comparisons, and reliable historical reporting that supports better business decisions.

Data Source Integration

Connect to any data source, from CRMs to custom systems.

SCD Implementation

Implement SCD Type 2 to track historical changes in dimensions and metrics.

Trend Analysis

Create powerful visualizations to analyze trends and patterns over time.

​
Implementation Example

Here’s how teams use Nekt to implement SCD Type 2 with the History module:
1

Connect your data source

Make sure the source table you want to track is available in your Catalog.
2

Create a History

Go to the History module and click Add History. Select the input table, define the primary keys that uniquely identify each record, configure the output layer and table name, and set up a trigger (we recommend an event-based trigger tied to your source extraction).
3

Watch your history grow

Each time the History runs, it compares the current state of your source table with the previous version and appends new versioned records. Check your output table over time to see the full change history.
Set the History trigger as event-based, tied to the pipeline of your input source extraction. This ensures your history is updated automatically every time fresh data arrives.
Here’s a video tutorial to guide you through the process!
Check our LinkedIn post about it!