Skip to content
Module
Module 3 of 6Lesson 2 of 3~14 min

Identity, accounts and event sources

When user identity is handled badly, journeys split in two and B2B accounts become impossible to count. This lesson prepares a PM to specify, with engineers, how anonymous visitors, signed-in people and customer companies are linked together. It also helps decide which events should be sent from the server rather than from the interface.

Take this lesson: your first course is freeSee the full syllabus

Lesson objective

By the end of this lesson, you will be able to specify when to identify a user, how to link their anonymous and logged-in events, how to attach events to a client account in B2B, and which events to send from the server rather than from the browser or the app.

Questions this lesson answers

  • When should you call identify on a user in a product analytics tool?
  • How do you attach analytics events to a customer account in B2B?
  • Which analytics events should be sent from the server instead of the client?

Topics covered

  • identify call
  • anonymous ID
  • group analytics
  • server-side tracking
  • B2B analytics

Where it fits

Design the tracking plan

Which events should I collect, how should I name them and who should they be attached to, so that the data answers my questions?

Lessons in this module

  1. Events, properties and naming convention
  2. Identity, accounts and event sources (this lesson)
  3. Write the tracking plan and the acceptance criteria

What you will learn in this module

This lesson is part of the course Instrument a product and use data to make decisions

  • Design an implementable tracking plan (events, properties, naming convention, identity and accounts, emitting source, owners).

Related courses