Creating and Accessing New Customer Profile Properties
how do i create new customer profile properties? and how do i access these properties in the reports?
how do i create new customer profile properties? and how do i access these properties in the reports?
Hi Tobias, 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 create new customer (user) profile properties in Mixpanel, you need to set these properties using your chosen SDK. Here’s how you can do it:
1. Creating New Customer Profile Properties
You create or update user profile properties by calling the appropriate method in your SDK. For example, in JavaScript: LBKS// Identify the user first mixpanel.identify('12345');LBKS// Set new or update existing profile properties mixpanel.people.set({ plan: 'Premium', // New or updated property company: 'Mixpanel', // New or updated property age: 30 // New or updated property });LBKSIf a property does not exist, it will be added. If it already exists, it will be overwritten with the new value. This pattern is consistent across all Mixpanel SDKs, including iOS, Android, Python, Ruby, PHP, and others. You must call .identify() before setting properties to associate them with the correct user profile. For more SDK-specific examples, see the documentation for your platform (e.g., JavaScript, iOS, Android).
2. Accessing These Properties in Reports
Once you have set user profile properties, you can access and use them in Mixpanel reports: - Filtering and Segmentation: User properties can be used to filter or segment your data in reports. For example, you can segment events by user properties like "plan," "company," or "age."
- Cohorts: You can create cohorts (groups of users) based on user profile properties, such as all users with plan = 'Premium'.
- Custom Properties in Reports: You can also create custom properties in reports by combining existing user properties using the custom property builder. This allows you to define new properties on the fly for analysis, and, if you have the appropriate plan, save them for reuse across reports. To do this, click the plus button next to the search bar in a report, select "User Property," and define your formula. You can then apply or save this custom property for use in your analysis or share it with your team Creating a Custom Property.Note: Custom properties created in reports are different from profile properties set via SDKs—they are calculated properties for analysis, not stored on the user profile itself.---In summary:
- Set new user profile properties via your SDK using .people.set() (or equivalent).
- Access and use these properties in reports for filtering, segmentation, and cohort creation.
- Optionally, create custom properties in reports for advanced analysis.If you need SDK-specific code, let me know your platform!
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.
Let me check the knowledge base for you again. One moment! 📚
To calculate the sum of all assets across all your customers (i.e., the sum of the $number_of_assets property across all user profiles) in Mixpanel, you can use the Aggregate Property measurement in an Insights report.Here’s how you can do it: 1. Go to Insights: Open the Insights report in Mixpanel.
2. Select Users as the Data Source: Make sure you are analyzing user profiles, not events.
3. Choose the Measurement: Click on the measurement dropdown (it may say "Total" or "Unique Users" by default).
4. Select "Aggregate Property": Choose "Aggregate Property" as the measurement type.
5. Pick the Property: Select $number_of_assets as the property to aggregate.
6. Choose "Sum": For the aggregation, select "Sum". This will give you the total number of assets across all user profiles.This approach will sum the value of the $number_of_assets property for every user profile, giving you the total assets across your customer base. This is supported in Mixpanel’s Insights reports for profile properties: > | Function Name | Events Calculation | Profiles Calculation |
| --- | --- | --- |
| Sum | The total of a numeric property value across all instances of [event]. | The total of a numeric property value across all user profiles. Example: What’s the total revenue across all users? |
Aggregate PropertyIf you do not see the option to analyze user profiles in Insights, ensure you are in the correct mode (Users, not Events).Note: This method assumes that $number_of_assets is a numeric property on your user profiles.Let me know if you need step-by-step screenshots or further clarification!
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.
Let me check the knowledge base for you again. One moment! 📚
To recast (typecast) a customer profile property from a string to a number in Mixpanel reports, you can use the Data Type option in the report UI. Here’s how you can do it: 1. In your report (such as Insights), find the property you want to typecast.
2. Click the overflow menu (three dots) next to the property filter or breakdown.
3. Select the Data Type option.
4. Choose Number as the data type.This will force Mixpanel to treat the property as a number for the purposes of that report, allowing you to perform numeric operations like sum, median, or percentiles. This is especially useful if your property was ingested as a string but represents numeric data.> Mixpanel allows you to force Properties into another data type by using the “Data Type” option in the overflow menu for property filters and breakdowns. Typecasting is helpful when one of your properties is a number but is sent to Mixpanel as a string and you want to see histogram data for that property.
Typecasting in ReportsNote:
- This typecasting only affects how the property is treated in the report; it does not change the underlying data type stored in Mixpanel.
- For permanent changes, you should update your implementation to send the property as a number.If you need to typecast within a custom property formula, you can use the number() function, e.g., number(A), where A is your property name Custom Property Functions.
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.
Let me check the knowledge base for you again. One moment! 📚
I'm sorry, but the knowledge sources do not contain explicit information about setting the data type of a property when importing from a CSV into Mixpanel. The documentation describes how to import profiles and map columns to properties, but it does not mention an option to specify or enforce property data types during the CSV import process. Properties may be interpreted based on their values, but there is no documented way to set the data type directly during import via the UI or CSV mapping workflow Importing Profiles via the UI.If you need to ensure a specific data type, you may need to adjust your data formatting in the CSV (e.g., ensure numeric columns contain only numbers), but the documentation does not guarantee how Mixpanel will interpret these types on import.
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.
Let me check the knowledge base for you again. One moment! 📚
I'm sorry, but the knowledge sources do not contain information about converting or saving a custom property created with the number() function (or any custom property) as a persistent profile property on the user profile in Mixpanel. Custom properties created in reports are used for analysis within those reports and are not stored as actual profile properties on user profiles.If you need a property to exist as a true profile property, you must set it via your SDK or API when tracking or updating user profiles, not through the custom property builder in reports Creating a Custom Property.If you need further assistance, please let me know your use case or platform!
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.