Frequently asked questions about mobile app profiles and push tokens
You will learn
Learn the answers to common questions surrounding mobile app profiles and push tokens.
In the sections below, we cover the following:
- Push profiles
- Push tokens/consent
FAQs for push profile
How does Klaviyo identify mobile app profiles?
Installing the Klaviyo SDK in your mobile app lets you identify profiles and track events in Klaviyo, the same way Klaviyo’s Active on Site tracking snippet does on a website.
When someone opens your app for the first time, Klaviyo creates an Anonymous ID for that user. When your app sends the first profile property, event, or token for that user to Klaviyo, Klaviyo will create an anonymous profile using that ID. If your app later identifies the user with an email address, phone number, or external ID, Klaviyo looks for an existing profile with that same information.
If Klaviyo finds a match, it updates that existing profile and merges it with the anonymous profile.
If there’s no matching profile, Klaviyo creates a new one using whatever identifiers your app provides.
Your app developer must have set up your app to create profiles in Klaviyo. If no profiles are being created (either identified or anonymous), you should reach out to your app developer.
Why do I have anonymous profiles (i.e., profiles without an email or phone number)?
An anonymous mobile profile has an anonymous ID, but no email address, phone number, or external ID.
Klaviyo automatically generates an anonymous ID in the SDK for all mobile app users. An anonymous profile is created when both of the following are true:
- Your app sends a profile property, event, or token through the Klaviyo SDK
- Your app doesn’t provide any other unique identifier for that person, like an email address, phone number, or external ID.
Anonymous profiles allow you to track a user’s in-app activity and message them even before they are identified.
Why do I see a lot of “Merged Profile” events for the profile?
A Merged Profile event appears whenever Klaviyo combines 2 separate profiles. For mobile app users, this happens when Klaviyo connects an anonymous profile to an existing one using an email address, phone number, or external ID.
You might see several Merged Profile events if someone uses your app on multiple devices. Klaviyo creates a separate anonymous profile for each device, then merges them as it identifies the same person on each one by email address, phone number, or external ID.
Can I stop tracking anonymous profiles?
Yes, you can disable tracking anonymous profiles in your Account Settings.
- Go to Settings > Data
- Under Mobile App Identification, uncheck the box next to Anonymous Profile Tracking.
- In the modal that appear, select Turn off to confirm that you would like to stop tracking anonymous profiles.

When you turn off this feature, Klaviyo will block any API requests that contain only an anonymous ID as an identifier.
FAQs for push tokens/consent
A push token identifies your app on a particular device. To send marketing push notifications to that device, the user must have allowed notifications for your app on that device. Learn more about push notification consent.
Where can I find push tokens in Klaviyo?
Because app users can have your app on multiple devices, a profile can have one or many push tokens associated with it. You can find push tokens listed on an individual profile under Channel consent > Mobile push notifications. All mobile app users generally will have a push token associated with the profile even if they have not subscribed to push notifications.
When are new push tokens generated?
Firebase Cloud Messaging (FCM) on Android and Apple Push Notification service (APNs) on iOS issue push tokens, which your app forwards to Klaviyo through the SDK. A new token can be issued when:
- Someone uses your app on a device for the first time
- Someone deletes and reinstalls your app
- An app or device is restored from a backup
Why was a push token removed from a profile?
Klaviyo removes push tokens from profiles when iOS or Android notifies Klaviyo that the tokens are not valid.
Here’s how that happens:
- You try to send a push notification (via a flow or campaign) to a token.
- Android or iOS sends a response saying the token is invalid.
- Klaviyo removes the push token.
A profile can have multiple push tokens if someone has enabled push notifications on more than one device, like a phone and a tablet. When that’s the case, only the invalid token is removed, and you can keep sending push notifications to their other devices.
If the token is the only one on the profile, Klaviyo unsubscribes the profile from push notifications until your app adds a valid push token again.
Additional resources
- Understanding push notification consent
Learn about push notification consent and best practices for compliance. These guidelines can help you be compliant in your consent collection practices and maintain a positive relationship with your customers.
- Frequently asked questions about push notification delivery
Learn the answers to common questions surrounding push notification delivery.