✨
Docs
Case StudiesGet Help
  • ✨Getting Started
    • What is Because?
    • Navigating The Because Dashboard
    • Klaviyo: Technical Integration Guide
  • ⚡Personalize
    • Because Content Types
      • Badges
      • Replace Image
      • UTM's
    • Because Page Types
      • Home Page Personalization
      • Collection Page Personalization
      • Product Detail Page Personalization
      • Cart Page Personalization
    • Campaign Setup
      • How Positions Work
      • Find Your Position Tool
      • Campaign Rules
      • How to Preview a Campaign
      • Using the Groups Tab
      • How to Use Dynamic Text Tokens
    • Klaviyo Personalization
      • Understanding Klaviyo Targeting Logic in Because
      • Klaviyo Use Cases
      • How to Link Klaviyo Popups to Because Campaigns
      • Klaviyo Profile Data & Dynamic Text Tokens
    • Shopify Customer Data Integration
    • Troubleshooting Campaigns
      • How Do Cart Campaigns Get Reloaded
      • Understanding Script Types: Asynchronous vs. Synchronous
  • 🌈Test
    • A/B Testing 101
    • Understanding Data Updates After Pausing an A/B Test
    • How Split Ratios Affect Your A/B Test Results
  • 📈CASE STUDIES
    • Southern Scholar Boosts CVR by +34%
    • Ethique Leverages Zero-Party Data to Boost CVR by 26%
  • 🤖Support
    • Frequently Asked Questions
    • Get Help
    • Give Feedback
    • Because Youtube Channel
  • 🚀The Ecom Edge
    • Ep 01
    • Ep 02
    • Ep 03
    • Ep 04
    • Ep 05
    • Ep 06
  • 🦄Partners
    • Because Partner Program
  • ⚠️Incident Reports
    • Double Counting in Analytics
Powered by GitBook
On this page
  • Incident Summary
  • What Happened
  • What We've Done
  • Moving Forward
  1. Incident Reports

Double Counting in Analytics

Dear Valued Customer,

We wanted to inform you about an issue we recently identified and resolved to ensure transparency and maintain your trust in our platform.

Incident Summary

During the week of November 12, 2024, we discovered an issue in our analytics where some metrics were double-counted. This occurred after transitioning our database from PostgreSQL to ClickHouse to support faster data processing.

What Happened

The switch to ClickHouse was made to enhance data processing speed for our large datasets, some of which contain close to half a billion rows. This transition significantly improved data ingestion and reduced processing time. However, during this update, an error was introduced into the way we calculated analytics metrics.

The issue stemmed from our transformation processes, where both pre-processed and post-processed data were included in the calculations, resulting in double-counted metrics in the analytics dashboards.

Importantly, this issue did not impact the accuracy or integrity of your raw data. Only the pre-calculated tables used for analytics were affected.

What We've Done

Once we identified the issue, we worked closely with ClickHouse support to resolve it. The problem has now been fixed, and the pre-calculated tables have been corrected. Your analytics dashboards are accurate once again.

Moving Forward

To prevent issues like this in the future, we’ve:

  • Conducted a thorough review of our data transformation processes.

  • Implemented additional safeguards to ensure data integrity during future updates.

  • Strengthened our collaboration with ClickHouse to promptly address any unforeseen challenges.

We take the reliability of your analytics very seriously and are committed to continuous improvement to provide you with the best possible experience.

Thank you for your understanding and trust. If you have any questions or need further clarification, please don’t hesitate to reach out to our support team.

Sincerely,

The Because Team

PreviousBecause Partner Program

Last updated 4 months ago

⚠️