All Categories
SuperPixel
V3 SuperPixel Documentation

V3 SuperPixel Documentation

Another article description

SuperPixel v3 Documentation

SuperPixel v3 is our latest identity and event tracking pixel built for performance marketers, data platforms, and analytics teams who need reliable, deterministic user data. It emphasizes authenticated resolution, spam-resilient event tracking, and seamless support for session and profile stitching—all with minimal configuration and maximum control.

🚀 What’s New in v3

  • Authenticated-only HEM resolution
  • Deterministic identity resolution chain (Cookie → HEM → Universal ID → Profile)
  • Real-time validation with no backend post-processing
  • Full event customization via API
  • Improved bot and spam filtering
  • Support for GA4 & Clarity integrations

🧠 Identity Resolution Methodology

SuperPixel v3 resolves users into persistent, portable profiles using a multi-layered deterministic system. Here’s how we do it:

🔐 Step 1: Cookie / MAID to HEM

Resolution starts with a cookie_id or maid_id. The user must authenticate for us to hash their email (HEM = Hashed Email).

Requirements:

  • Event type: authentication
  • Captured email must match session IP & user agent
  • Email is normalized and hashed using SHA256

Sample Payload:

json
CopyEdit
{
  "cookie_id": "a1f2c3d4e5",
  "event": "authentication",
  "email_raw": "user@example.com",
  "hem": "4d186321c1a7f0f354b297e8914ab240",
  "ip": "192.168.0.1",
  "user_agent": "Mozilla/5.0"
}
We never use IP-to-HEM guessing. IPs are used only for validation.

🧬 Step 2: HEM to Universal ID (UID)

Each HEM is deterministically linked to a uid. If a user logs in across multiple browsers or devices, we group them under one uid when 2 or more identifiers match:

  • Same IP subnet (/24 range)
  • Same fingerprint (user agent + screen res)
  • Authenticated HEM overlap
  • Event proximity < 24 hours

Example:

json
CopyEdit
{
  "uid": "u_01HEABCX789TZY",
  "hem": "4d186321c1a7f0f354b297e8914ab240",
  "cookie_ids": ["a1f2c3d4e5", "b9g7k2m3t1"],
  "maids": ["aabbccddeeffgghh"]
}

🧠 Step 3: Universal ID to Profile

uid is mapped to a profile_id where all behavioral and identity signals are consolidated:

json
CopyEdit
{
  "profile_id": "p_01HJXYZ12345",
  "uid": "u_01HEABCX789TZY",
  "hems": [
    "4d186321c1a7f0f354b297e8914ab240",
    "9b74c9897bac770ffc029102a200c5de"
  ],
  "traits": {
    "last_seen_ip": "192.168.0.1",
    "device_type": "desktop",
    "geohash": "9q9hwgk7"
  },
  "event_count": 244
}
Profiles are deduplicated automatically and never built from anonymous or inferred data.

📊 Supported Events

SuperPixel v3 tracks the following user events:

Event Type
Description
copy
Fired when user copies text or content.
page_view
Triggered on full page load.
exit_intent
Fires when mouse moves toward top edge (likely tab close).
deep_scroll
Activated when user scrolls 75%+ of the page.
idle_user
Fires after a set period of inactivity (default: 60s).
video_engagement
Tracks video events like play, pause, complete.
all_clicks
Tracks all clicks across the page.
file_downloads
Tracks downloads of PDF, DOC, ZIP files, etc.
all_form_submissions
Tracks all form submission events.

🧾 Enriched Event Payload

A fully enriched SuperPixel event may include multiple layers of information:

📌 Identity & Timing Fields

json
CopyEdit
{
  "pixel_id": "003daacb-d261-421c-9781-311df9c381d8",
  "hem_sha256": "1458ee23320e30d920f099f57b11000b89ab82a7456bf39dd663d9d0858fd88d",
  "event_timestamp": "2025-05-29T23:52:53Z",
  "ip_address": "35.191.85.117",
  "activity_start_date": "2025-05-29T23:52:53Z",
  "activity_end_date": "2025-05-29T23:53:53Z"
}

📄 Event Metadata (Nested in event_data)

  • URL visited
  • Page title
  • Referrer
  • Scroll percentage
  • Clicked element (text, tag, classes)

Note: event_data is nested and includes interactive element metadata.

🧬 Resolution Metadata (Nested in resolution)

Includes:

  • Personal details: FIRST_NAME, LAST_NAME, GENDER, AGE, INCOME_RANGE
  • Contact: PERSONAL_EMAILS, PERSONAL_PHONE, MOBILE_PHONE_DNC
  • Address: PERSONAL_ADDRESS, PERSONAL_CITY, STATE, ZIP
  • Enrichment: NET_WORTH, HOMEOWNER, MARRIED, CHILDREN, SKIPTRACE_MATCH_SCORE
These fields are only populated when deterministic resolution is successful.

🧩 Event Configuration

Control which events are captured directly in your SuperPixel init script:

js
CopyEdit
SuperPixel.init({
  trackEvents: {
    copy: true,
    page_view: true,
    exit_intent: true,
    deep_scroll: false,
    idle_user: true,
    video_engagement: true,
    all_clicks: false,
    file_downloads: true,
    all_form_submissions: true
  }
});
⚠️ Disable high-volume events like all_clicks if you're optimizing for efficiency.

🧼 Attribution & Bot Filtering

  • SuperPixel does not use IP-to-HEM resolution.
  • When HEM is unavailable, fallback uses IP → Company enrichment with a cleaned IP table:
    • Filters out TOR nodes, proxies, datacenters
    • Known bot clouds are dropped by default

🔒 Privacy & Post-Processing

  • No post-processing or retroactive enrichment is performed.
  • All associations are made in-session using observed, authenticated events only.
  • Shared device activity is tagged, and multiple HEMs can exist per browser session with clear timestamp tracking.
Did this answer your question?
😞
😐
🤩

Last updated on August 6, 2021

Set-up the web-hook Dealing with Duplicates