Skip to content
Kubit Guide home
Kubit Guide home

Cross Platform User Tracking

Kubit unifies user behavior across platforms and devices into a single profile, so you get one view of the customer journey no matter where the interaction happens. A user who chats with your agent, opens your mobile app, and converts on the web is one user in Kubit, not three.

How Kubit models a user

Every report in Kubit analyzes a Subject, a unique identifier used to count and group. User is the subject that ties activity together. Each platform may carry its own identifier (a web user ID, a mobile device ID, an authenticated account ID, an agent session user), and cross platform tracking is the work of resolving all of them to one canonical User.

Unify identities in the Modeler

The Modeler is where you map each source to the shared User subject.

  • Map identifiers to one subject. Point each platform's user column at the canonical User subject so events from web, mobile, and agents resolve to the same person.

  • Resolve anonymous and device IDs. Use a custom column to map device or anonymous IDs to a known user once they authenticate, joining pre login and post login activity into one profile.

  • Union sources into one model. Agent behavior and product behavior arrive as separate source views. The Modeler unions them and joins your shared dimensions, so a single report spans every surface.

If you already resolve identity upstream in a CDP, Kubit uses it directly. Segment, Snowplow, mParticle, and RudderStack feed their unified identifiers straight into your warehouse, and Kubit reads them in place.

The warehouse native foundation

Cross platform tracking works because all of your platform data lives in one place. With a warehouse native deployment, web, mobile, and agent data sit in the same cloud data warehouse, so Kubit joins them where they are with no copying and no separate identity store to reconcile.

What it unlocks

  • End to end journeys. Follow one user from a web visit, through an agent conversation, to a mobile conversion in a single Flow or Funnel.

  • Accurate counts. Deduplicate the same person across devices so user counts, retention, and cohorts reflect people, not sessions or devices.

  • Cross surface cohorts. Build a cohort on behavior from any platform and use it across every report.

Make it accurate

  • Confirm each source exposes a usable user identifier and map it to the User subject in the Modeler.

  • Define the identity resolution rule (custom column or upstream CDP) for anonymous to known stitching.

  • Keep identifier fields documented so the mapping stays clear as you add platforms.

Next steps

Powered by Plain