Hi,
We have a user journey that starts in two completely separate applications with two different identification systems, and later connect so that we have continuous access to the user’s IDs from both apps.
As a team, we are really focused on Activation and tracking the events early in a customer journey. For this app, the typical journey starts like this:
- A user (usually an admin) installs the app in App A and makes some configuration/setup choices. We would usually use App A related values here for both user_id as well as to identify a group for the app license.
- A user (either the same admin as before or a different one) installs the app in App B and does some more setup. At this point, we have access to their App B identifiers for the user and group.
At this point - we do not have any practical ways to link the two actions / journey steps, since there is no shared interface or user/license credentials. It is also unlikely that we will have a reliable/consistent device_id during these first steps.
- A user decides to connect their App B to App A, so now the two are integrated. At this point, we have access to a user’s App A user_id and license information even when they are in App B, so things get less complicated.
I am asking for some guidance or best practices on how to deal with tracking our customer’s journey (at both the user and group level) during the beginning steps, when our information is disjointed. The desired end result is being able to make a funnel chart that has the first step = InstalledInAppA and the second step = InstalledInAppB.
Has anyone successfully dealt with this type of situation before?
