① Capture · Behavior Tracking
Capture behavior everywhere your members are.
Email, the loyalty portal, your native app, and your own site — four collection surfaces, one identity-resolved member timeline. Anonymous behavior stitches to a member the moment they're known, and every signal is parsed server-side, bot-filtered, and proxy-aware.
One member timeline
anonymous → resolved to member
The problem
Your member's behavior is scattered across four tools that never talk.
Email opens you can't trust
Apple and Gmail pre-fetch images, so half your “opens” are machines. Decisions built on inflated engagement are decisions built on noise.
On-site behavior, invisible
What a member browses on the portal, taps in the app, or reads on your site lives in three different analytics tools — none of them keyed to the member.
Anonymous stays anonymous
A visitor browses for weeks before signing up, and all that intent is lost the moment you can't connect their earlier behavior to the new member.
Four collection surfaces
Capture once, everywhere they engage.
Every surface writes into the same member timeline — so the whole picture is one query, not four exports.
Opens & clicks, proxy-filtered
Every open and click is recorded with the real device, OS and browser behind it. Apple Mail Privacy and Gmail image-proxy prefetches are detected and filtered out — so an “open” means a human actually looked, not a machine pre-fetch inflating your numbers.
Member portal
Page visits + block-level events
Every visit on the loyalty portal — path, category, referrer, UTM, server-parsed device and geography — plus block-level interactions: which portal block a member saw (impression) and tapped (click), and the target. Attributed to the member from their session; anonymous when logged out.
Native app
Same tracking, inside your app
The member center runs inside your app as a WebView with first-party single sign-on, so in-app page visits and block taps flow into the very same timeline. No separate mobile-analytics SDK to wire up or reconcile — it is the portal tracking, in-app.
Your own site
First-party beacon
Drop a lightweight first-party tracking snippet onto your marketing or e-commerce site and page views post to a public tracking endpoint, joining the same member timeline (keyed anonymously on your domain). You see behavior on your site, not only what happens inside Flash.
One timeline
Four sources, one member story.
Behavior is keyed by an anonymous id and a session id, then resolved to a member id from the session — so a visitor's earlier anonymous activity stitches onto their record the instant they're known. The result is a single chronological timeline: enrollment, points, receipts, coupons, email opens and clicks, portal visits, in-app taps, and site browsing — all in one place, per member.
A member timeline
Opened “Weekend perks”
Email · iPhone · real open
Visited the portal
Portal · rewards page
Tapped “Redeem 200 pts”
App · offer block
Browsed pricing
Your site · via SDK
Earned 120 points
Receipt · in-store
illustrative · server-side device & geo · bot-filtered
Built for trust
Honest signal — not inflated, not client-trusted.
Server-side, not client-trusted
Device, OS and browser are parsed from the user agent server-side; geography is resolved server-side; bots are detected and flagged — the client never gets to lie about who it is.
Proxy-aware email
The hard part of email analytics done right: real human opens are separated from Apple/Gmail proxy prefetches, so engagement metrics reflect people, not privacy proxies.
Anonymous → known resolution
Behavior is keyed by an anonymous id + session id and resolves to a member id from the session. The moment a visitor is known, their earlier anonymous behavior stitches onto their member record.
Privacy by construction
Collection honors consent and the Global Privacy Control signal and falls back to anonymous when a visitor is not logged in — instrumentation that respects the member, fail-closed.
It doesn't stop at capture
The behavior timeline is the raw material the rest of the loop runs on — the member record, segments, the dashboard, and the agent that decides the next best action.