User tracking

In mobile and web app analytics, it's essential not to miss the user for the device IDs, which would then make you miss out on your audience size and its behavior. More often than ever before people are switching or upgrading their devices, many use several platforms at once, and some take turns on a single device. MyTracker will help you keep tabs on the exact number of your customers and seamlessly accumulate relevant data.

How it works

It works only for apps with registration and authorization mechanisms. Upon registration, each user is assigned a unique identifier, that is not tied to a device or platform. With these user IDs, MyTracker can recognize all of the user's activity even if they switch devices.

Where to start

  1. Choose a user identification method. You can use the same ID as in the app backend or your CRM system.
    Remember the following limitations:
    • User ID should remain unchanged throughout the project. For example, if an ID is an email, you should not write it as a string on one platform and as an email hash on the other. In this case, some of the benefits will be lost and MyTracker will be unable to link user activities on different platforms.
    • An identifier is unique for each individual project. MyTracker builds a separate client base for each project, so it will recognize the same IDs in different projects as different users, even if the ID is the user's personal email or phone.
  2. Send the identifier to MyTracker. The sooner MyTracker receives the ID, the more complete the picture of the user's activity will be. Transfer the identifier right after the user launches the app. For more details, please see the Track users section for iOS, Android, Unity, Flutter, Web.

Do not forget to track registration and authorization events (for more details, please see the Track events section for iOS, Android, Unity, Flutter, Web). That way, you will be able to easily tell new users from the existing audience:

  • registration with an unknown ID — new user;
  • authorization with an unknown ID — user, who had registered before you installed the SDK and started tracking (new for MyTracker, but old for your app);
  • authorization with a known ID — existing user.

Done! Now, MyTracker will be collecting user stats for your project. You will gain insights into your real user base, including its size, traits, purchases, and how these people actually interact with the app. To analyze data, select the Users metrics in the Report constructor.