If there are two profiles on the same device, how many pushes will be delivered to the profiles?
Only one push will be delivered to the most recent profile.
While one push is delivered to the most recent profile, will the “push-delivered” event be recorded on both profiles?
The “Push delivered” event will be recorded only for the profile that received the push.
Is a push notification sent to the last active user of the device? If one user is logged in, should the other user be logged out?
Only Mobile App campaigns use the latest active profile for a shared device; Architect does not. In Architect, the profile that enters the journey supplies the targeting and personalization data, even if another profile is now the device’s latest active user.
And logging in User B does not automatically guarantee that User A becomes logged out:
The app must call logout() while User A is still the current user. This sets User A’s Mobile App Login Status to false.
The app then calls login() for User B. This sets User B’s status to true.
If the app switches directly to User B without correctly logging out User A, both profiles can remain true.
Both profiles can then qualify for an Architect journey, while the push still reaches the same physical device.
So, this expectation is correct only if the app implements the sequence logout(A) → login(B) correctly. After the login status is set to false, the login() method must be called to set it to true again.
For Architect, use Mobile App Login Status = true, but treat it as dependent on correct SDK calls. It is not an automatic “last active user of this device” filter.