Tracking

Ring DAS provides comprehensive tracking capabilities to measure ad performance and attribute conversions to ad interactions.

Overview

The tracking system captures two types of events:

• Click Events: Recorded when users click on ads via the Adclick API
• Activity Events: Recorded when users perform actions on your website via the Activity Pixel API

Conversion Attribution Flow

sequenceDiagram
    participant User
    participant Ad
    participant Adclick API
    participant Website
    participant Activity Pixel

    User->>Ad: Views ad
    User->>Ad: Clicks ad
    Ad->>Adclick API: /trk/adclick/...?lu=XXX
    Adclick API->>Adclick API: Records click
    Adclick API->>Website: 302 Redirect with lu parameter
    User->>Website: Browses products
    User->>Website: Makes purchase
    Website->>Activity Pixel: /activity?event=purchased&lu=XXX
    Activity Pixel->>Activity Pixel: Matches lu to click
    Note over Activity Pixel: Conversion attributed!

Key Concepts

User Identifiers

Ring DAS uses the following identifiers to track users and attribute conversions:

• LU - Anonymous local user ID
• AID - Hashed email set by Ring DAS
• EID - Hashed email provided by client

These identifiers flow through the conversion funnel:

1. Generated or captured when user interacts with the ad system
2. Passed in the adclick URL when user clicks an ad
3. Captured on the landing page
4. Sent with activity events (purchases, etc.)
5. Used to attribute conversions back to clicks

Attribution Window

Conversions are attributed to clicks within a configurable lookback window. If a user clicks an ad and makes a purchase within the attribution window, the conversion is credited to that click.

Guide Pages

• Conversion Attribution - How click-to-conversion attribution works

API Reference

• Click tracking spec - Adclick API endpoint
• Purchased event spec - Activity Pixel purchase event