Skip to main content
The Tracking Pixel is currently in alpha. The data collected may change between releases.
A reference of all data the Tracking Pixel collects, organized by category. Useful for privacy reviews, legal assessments, and technical audits.

Cookies

The pixel sets first-party cookies only. No third-party cookies are created.
CookieNameLifetimeScopePurpose
Anonymous Device IDimtbl_anon_id2 yearsFirst-party, current hostnamePersistent anonymous device identifier (UUID v4). Shared between the pixel and web SDK. SameSite=Lax, Secure on HTTPS.
Session ID_imtbl_sid30 minutes (rolling)First-party, current hostnameSession continuity across page loads. Expires after 30 minutes of inactivity.
The pixel reads (but does not write) existing third-party cookies if present, for cross-platform identity stitching:
CookieSourcePurpose
_gaGoogle AnalyticsGoogle Analytics client ID
_fbcMeta (Facebook)Facebook click ID
_fbpMeta (Facebook)Facebook browser ID

Device Fingerprint Signals

These signals are collected automatically when consent is anonymous or full.
SignalSourceExample
User agentnavigator.userAgentMozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7)...
Screen resolutionscreen.width × screen.height1920×1080
TimezoneIntl.DateTimeFormat().resolvedOptions().timeZoneAmerica/New_York
Browser languagenavigator.languageen-US
IP addressServer-side from request headersUsed for geo lookup then hashed. Raw IP is never stored.

Attribution Signals

Captured automatically from the URL and browser on every page load.
SignalSourceExample
UTM parametersURL query stringutm_source, utm_medium, utm_campaign, utm_term, utm_content
Google click IDURL query stringgclid
Meta click IDURL query stringfbclid
TikTok click IDURL query stringttclid
Microsoft click IDURL query stringmsclkid
Display & Video 360 click IDURL query stringdclid
LinkedIn click IDURL query stringli_fat_id
Referrerdocument.referrerThe referring page URL
Landing pagewindow.location.href (first page in session)Entry point URL
Referral codeURL query stringreferral_code parameter if present

Auto-Tracked Events

page

Fires on every page load. Properties: All attribution signals above, sessionId, third-party IDs (gaClientId, fbClickId, fbBrowserId), touchpoint_type: 'click'.

session_start

Fires when a new session begins (no active _imtbl_sid cookie). Properties: sessionId.

session_end

Fires on page unload (visibilitychange to hidden / pagehide). Properties: sessionId, duration (seconds since session start).

form_submitted

Fires on HTML form submission. Properties: formAction, formId, formName, fieldNames. At full consent only: emailHash (SHA-256, hashed client-side before transmission). Fires on outbound link clicks (external domains only). Properties: linkUrl, linkText, elementId, outbound: true. What is collected at each consent level:
Data categorynoneanonymousfull
Script loadedYesYesYes
Cookies setNoneimtbl_anon_id, _imtbl_sidimtbl_anon_id, _imtbl_sid
Page view eventsNoYesYes
Session eventsNoYesYes
Device fingerprintNoYesYes
Attribution signalsNoYesYes
Form submissionsNoYes (no email)Yes (with hashed email)
Outbound link clicksNoYesYes
Third-party ID stitchingNoYesYes

What the Pixel Does NOT Collect

  • No cross-domain tracking (first-party cookies only)
  • No session replay or screen recording
  • No heatmaps or mouse movement tracking
  • No scroll depth tracking
  • No custom event tracking (use the Web SDK for that)
  • No A/B testing or feature flags
  • No server-side rendering support
  • No impression or view-through tracking (click-through only)
  • No raw email addresses (only SHA-256 hashed, only at full consent)
  • No raw IP addresses stored (hashed server-side after geo lookup)

Next Steps

Quickstart

Install the pixel on your site

Configuration Reference

All init options and command queue methods