---
title: Triple Whale
slug: triple-whale
createdAt: 2025-12-10T14:34:31.994Z
---

## Introduction

Triple Whale is a unified e-commerce attribution and analytics platform that offers advanced tracking, attribution modeling, and real-time insights across channels and customer touchpoints.

Connecting Triple Whale as a destination allows you to send user-level events and interactions collected via Chord directly to Triple Whale — enabling centralized attribution, funnel analysis, and behavioral insights while preserving your brand’s data context.

## Getting started

As a **device-mode** destination, Triple Whale receives data from client-side tracking implemented via Chord. Before connecting, ensure:

- You already have a Triple Whale account and the appropriate site or store configured;
- Your site’s frontend includes necessary tracking setup (tracking code or pixel) compatible with Triple Whale; and
- You have authorization to add or change tracking destinations.

## Connecting to the Triple Whale CDP destination

:::hint{type="danger"}
Before connecting destinations in the Chord CDP, please verify with all Destination owners that all **non-Chord CDP** configured destinations are *disabled.*
**
Running external destinations alongside configured Chord CDP destinations ***can result in duplicate events downstream. ***
:::

1. Log into the **Chord Data Platform.**
2. Go to the **CDP → Destinations** section.
3. Click **“Add”** to browse available destinations.
4. Select **Triple Whale** from the catalog.
5. Enter a **Destination Name** (e.g., “Triple Whale — Production”).
6. Provide the **Store Identifier **and **Platform **your store is running on.
7. Click **Create** to activate the destination.

Once connected, Chord will automatically route relevant user events and interactions (page views, conversions, identity data, etc.) to Triple Whale.

## Best practices & conflict avoidance

Before enabling Triple Whale via Chord, we recommend:

- Disabling any legacy or manually added Triple Whale tracking scripts/pixels to avoid **duplicate event firing and inflated data** 
- Coordinating with your engineering or analytics team to ensure single source-of-truth for tracking and user identity (avoid multiple overlapping tracking solutions) 
- Confirming tracking consent and privacy compliance if you manage user data under GDPR/CCPA or similar regulations 

Running parallel tracking outside of Chord’s configuration may lead to inconsistent analytics, inaccurate attribution, or data duplication.

## Troubleshooting & FAQs

**Q: I’m seeing duplicate pageviews or conversions in Triple Whale — what should I check?**

- Verify that you haven’t also installed Triple Whale tracking manually (outside of Chord). Duplicate scripts/pixels can cause double-counting.

**Q. What if some user attributes or events aren’t appearing in Triple Whale?**

- Ensure that the Chord tracking configuration includes the necessary signals, and that your user identity mapping (e.g., user ID, email) is properly populated in Chord before events fire.

**Q. Does Triple Whale overwrite my existing data warehouse or analytics stack?**

- No — Triple Whale operates as a destination for analytic and attribution data. If you rely on a separate warehouse or BI stack, treat Triple Whale as a complementary analytics solution rather than a full replacement.