Server-side pixel

Architecture

The Traqly pixel is a server-side first-party tag. The browser SDK only collects deterministic signals (IP, User-Agent, screen, language, hashed cookie). All resolution happens server-side in your workspace, where we stitch identity using a deterministic + probabilistic two-stage join.

Because the cookie is first-party (set by your domain via a CNAME), it survives Safari ITP and major adblockers, and never expires before the conversion window closes.

CNAME setup

Point a subdomain like `t.your-brand.com` to `ingest.traqly.ai`. SSL is provisioned automatically via Let's Encrypt within ~2 minutes.

t.your-brand.com.   CNAME   ingest.traqly.ai.

Identity stitching

• •Deterministic join: hashed email, hashed phone, logged-in user ID (when available).
• •Probabilistic join: IP-class C + UA fingerprint + temporal proximity (within 30 minutes default).
• •Conflict resolution: most-recent-wins for personal data, all-events-preserved for analytics.