Skip to main content
Ask your AI

User stitching

User stitching combines data from multiple sources or sessions into a unified view of a user. You need it to combine website and mobile app data, to unify customer interaction data across platforms, or to follow a user's journey through various touchpoints. It is especially useful when a user interacts with a system on multiple devices or platforms and these interactions should end up in a single user profile.

User behavior data is often incomplete, especially on the web, where users can easily delete cookies, change devices or use a different browser. Stitching correctly starts with understanding user identification.

Working with persistent identifiers requires the user's consent. Consent is always bound to specific purposes, which have to be documented and communicated properly.

tip

Learn more about consent management with walkerOS.

Relying on third-party tools and cookies might have been common practice, with benefits, in the past. Data that isn't owned and collected first-party always depends on others.

First-party data collection is the basis for attribution modeling, a complete view of your users and data ownership.

User identification levels​

User identification means recognizing a user, typically by associating them with a unique identifier. walkerOS has three levels of user identification:

  • id: a unique identifier for a user, typically from internal systems like a CRM.
  • device: a device-specific identifier, saved in the storage.
  • session: a session-specific identifier for user activities within a single session.

A single user can have different devices with multiple sessions. The id identifies an individual user across sessions and devices. The device recognizes a user across multiple sessions on the same device, while session covers user behavior and interactions within one limited time frame.

The diagram represents one user with two devices across three sessions.

warning

These techniques may require a user's consent and documentation to respect privacy and stay compliant. Ask your data protection officer for legal advice.

Example​

Events are individually measured user interactions. Stitching them together creates user journeys, and all event-related data helps to identify a user.

The following table is a minified event log over several days. It shows user activities over time and across sessions, with varying levels of user identification and consent categories.

All events of a run, representing a page load, share one source.trace id. A hash is a temporary fingerprint. session, device, and user are all simplified unique identifiers.

StepDayEventConsentTraceHashSessionDeviceUser
1Monday,
1st
session startanalyticsafoo
2Monday,
1st
page viewanalyticsafoo
3Monday,
1st
consent denyanalyticsafoo
4Monday,
1st
page viewanalyticsbfoo
5Tuesday,
2nd
session startmarketingcbar1phone
6Tuesday,
2nd
page viewmarketingcbar1phone
7Tuesday,
2nd
consent acceptmarketingcbar1phone
8Tuesday,
2nd
session startmarketingdbar2phone
9Tuesday,
2nd
page viewmarketingdbar2phone
10Wednesday,
3rd
session startmarketingebaz3phoneolli
11Wednesday,
3rd
page viewmarketingebaz3phoneolli
12Wednesday,
3rd
user loginmarketingebaz3phoneolli
13Friday,
5th
session startanalyticsfqux
14Friday,
5th
page viewanalyticsfqux
15Friday,
5th
page viewanalyticsgquxolli
16Friday,
5th
consent denyanalyticsgquxolli
17Friday,
5th
user loginanalyticsgquxolli
18Thursday,
11th
session startmarketinghlol4ph0n3

Based on the data, we can at least summarize the following:

  • 18 tracked events in total
  • 8 different trace ids ('a', 'b', 'c', 'd', 'e', 'f', 'g', 'h')
  • 6 individual session start events
  • 5 temporary hashes ('foo', 'bar', 'baz', 'qux', 'lol')
  • 4 reliable sessions (1, 2, 3, 4)
  • 2 known devices ('phone' and 'ph0n3')
  • 1 unique user ('olli')
💡 Need implementation support?
elbwalker offers hands-on support: setup review, measurement planning, destination mapping, and live troubleshooting. Book a 2-hour session (€399)