I have added event for download app in my website and that event also sent to the same project id which is present for my mobile application, now i want to map the users who clicked on download and then started using the app. basically i want to map or combine user of website and my app as both of them redirecting to the same project id
Hi Abhijeet S., Please stand by as I search the Mixpanel knowledge base for an AI-powered answer. I normally take about 15 seconds or so. In case AI cannot answer your question, feel free to reach out to Mixpanel support at mixpanel.com/get-support. If you have follow-up questions for this thread, please tag me again with your question: @kapa.ai <follow-up question> 👋
Feel free to ask a follow-up question once I've answered by mentioning me with @kapa.ai
To map users who clicked "Download App" on your website and then started using your mobile app—when both platforms send data to the same Mixpanel project—you need to leverage Mixpanel’s identity management and ID Merge features.
How Mixpanel Maps Users Across Web and App
1. Anonymous Tracking on Web:
When a user clicks "Download App" on your website, Mixpanel assigns them a $device_id
via the JavaScript SDK. This event (e.g., "Download App Clicked") is sent with this $device_id
and no $user_id
(unless the user is logged in).2. App Install and Usage:
When the same user opens your mobile app, the Mixpanel SDK on the app generates a new $device_id
for that device. Unless you have a way to pass a unique identifier from the web to the app (e.g., via a deep link with a token), Mixpanel will initially treat this as a new, anonymous user.3. User Identification and ID Merge:
If the user logs in (or signs up) on both the website and the app using the same account, you should call identify(<user_id> )
in both places. Mixpanel will then merge the $device_id
from the web and the $device_id
from the app into a single identity cluster under the same $user_id
. This allows you to see the full user journey across both platforms, including the "Download App" event and subsequent app usage events, all attributed to the same user profile. - When both $device_id
and $user_id
are present in an event for the first time, Mixpanel creates a mapping to merge them, forming an identity cluster. Any data sent with a distinct_id
set to any value in this cluster will be attributed to the same user in Mixpanel.
Identifying Users (Simplified)
Best Practices
- Send Data to the Same Project:
You are already sending both web and app data to the same Mixpanel project, which is recommended for cross-platform analysis. This enables you to track the full user journey and avoid counting the same user twice if they use both platforms.
Tracking Best Practices: Developer Environments- Consistent User Identification:
Ensure that you call identify(<user_id> )
as soon as you know the user's identity (e.g., after login or signup) on both web and app. This is crucial for merging their anonymous and authenticated activity streams.- Querying the Journey:
Once identity is merged, you can build a funnel or cohort in Mixpanel to analyze users who performed "Download App" on the web and then performed key actions in the app.
Limitations
- If users do not log in or create an account, Mixpanel cannot automatically link their web and app activity, since the $device_id
will be different on each platform and there is no shared identifier.
Summary
By using Mixpanel’s ID Merge and ensuring you identify users on both web and app, you can map the journey from "Download App" click on your website to app usage, as long as users authenticate on both platforms. This approach gives you a unified view of user behavior across devices and platforms.For more details, see the documentation on Identifying Users (Simplified) and Identity Management in Action.
kapa.ai is still learning and improving, please let me know how I did by reacting below.
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
The event from the website is basically [Auto] Page View with utm medium = social
kapa.ai The event from the website is basically [Auto] Page View with utm medium = social
Let me check the knowledge base for you again. One moment! 📚
If your website is sending an [Auto] Page View event with utm_medium = social
, and you want to map users who viewed this page (i.e., came from a social campaign) and then started using your mobile app, here’s how Mixpanel enables this mapping:
How Mapping Works
1. UTM Tracking on Web:
Mixpanel’s JavaScript SDK automatically captures UTM parameters (like utm_medium
) from the page URL and attaches them to events such as [Auto] Page View. These UTM parameters are also stored as super properties and, for first-touch attribution, as user profile properties prefixed with initial_
(e.g., initial_utm_medium
) when the user is identified. No extra configuration is needed for this if you’re using the default SDK settings and identifying users normally Web Attribution Sending Data to Mixpanel.2. Identity Merge Across Platforms:
When the same user later uses your mobile app and logs in (or signs up) with the same account as on the website, you should call identify(<user_id> )
in both the web and mobile SDKs. Mixpanel will merge the anonymous web activity (including the [Auto] Page View with utm_medium = social
) and the app activity under the same user profile Identifying Users (Simplified) Identity Management in Action.3. Attribution and Analysis:
Once the identity is merged, you can analyze the user journey in Mixpanel. For example, you can create a funnel to see how many users who had a [Auto] Page View with utm_medium = social
later performed key actions in your mobile app. The UTM parameters will be available for segmentation and attribution analysis Computed Properties: Attribution.
Important Notes
- If the user does not log in or create an account on both platforms, Mixpanel cannot automatically link their web and app activity. - UTM parameters are tracked and persisted by default, but for advanced attribution models, it’s recommended to disable UTM persistence by initializing the SDK with stop_utm_persistence: true Track UTM Tags.
Summary
As long as you identify users on both web and app, Mixpanel will merge their activity—including [Auto] Page View events with UTM parameters—allowing you to map and analyze the journey from social campaign click to app usage.If you need more details on setting up attribution or identity merge, refer to the Web Attribution and Identifying Users (Simplified) documentation.
kapa.ai is still learning and improving, please let me know how I did by reacting below.
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.