what is the best place for a property that shows the number of assets in my customer system, when the number only needs to be accurate on a daily basis and should be commonly available at user level?
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
You’ll get the most value by storing this as a user profile property, and updating it daily.**Why user profile (not event property):**- Mixpanel recommends using User Properties for demographic / state-like attributes about the user “as they exist in this moment,” such as plan, subscription level, counts like “number of songs a user has played,” etc.[Data model]
- Event properties are best for contextual details at event time and are immutable once tracked; your “number of assets” is a current state value that only needs daily accuracy, so it fits the profile model.[Profiles FAQ]Storing it on the user profile: - Makes it commonly available at user level in filters, breakdowns, cohorts, etc.
- Will be joined to all events for that user at query time, using the latest value.[Profiles FAQ]Implementation tips: - Track it as a numeric user property (e.g. asset_count) so you can do aggregations (sum, average, percentiles) in Insights.[Property data types]
- Update it once per day via your backend or a pipeline using the Profiles API.
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! 📚
Store this as a numeric user profile property and update it daily from your backend.What to implement- Define a user profile property, e.g. asset_count.
- Once per day, your backend:
1. Reads the current asset count from the customer system.
2. Sends a profile update for each user with the latest value using the Profiles/Engage API ($set operator) or relevant SDK “set” method (e.g. people.set, people_set, MessageBuilder.set, etc.). [User profiles]
- Use the same distinct_id you use for that user’s events so the profile joins correctly in reports. [User profiles]Why this way- Profiles are designed for user-level, slowly changing data (about one change per day per user is supported). [Update frequency]
- The latest profile value is automatically joined onto all events for that user at query time, so asset_count will be available as a filter/breakdown in reports. [Profiles FAQ]
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! 📚
Speichert diese Information als numerische User-Profile-Property und aktualisiert sie täglich im Backend.Was umzusetzen ist- Legt eine User-Property an, z. B. asset_count.
- Ein täglicher Backend-Job:
1. Liest die aktuelle Asset-Anzahl aus dem Kundensystem.
2. Schickt für jeden Nutzer ein Profile-Update mit $set über die Engage API oder die jeweilige SDK-Methode zum Setzen von Profil-Properties (z. B. people.set, people_set, PeopleSet, MessageBuilder.set). [User profiles]
- Verwendet dabei immer dieselbe distinct_id, die ihr auch für Events nutzt, damit Events und Profile korrekt gejoint werden. [User profiles]Warum so- Profile sind für Nutzerzustände und langsam ändernde Daten gedacht; Updates erfolgen über $set & Co. und überschreiben den letzten Wert. [User profiles]
- Der jeweils aktuelle Profilwert wird bei Abfragen mit allen Events des Nutzers verknüpft und steht in Filtern, Breakdowns und Cohorts zur Verfügung. [User profiles FAQ]
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! 📚
Für ein Angular-Frontend nutzt ihr das JavaScript SDK von Mixpanel.Die passenden Methoden für User-Profile sind dort unter mixpanel.people verfügbar, z. B.: - mixpanel.people.set() – Profil-Properties setzen/überschreiben [JS people.set]
- mixpanel.people.set_once() – nur setzen, wenn Property noch nicht existiert [JS other updates]
- mixpanel.people.increment() – numerische Properties hoch-/runterzählen [JS other updates]
- mixpanel.people.append() / mixpanel.people.union() – Listen-Properties erweitern [JS other updates]Für euren Anwendungsfall (täglicher Stand asset_count pro Nutzer) ist im Angular-Frontend relevant: js mixpanel.identify(userId); // einmalig pro Session/Seite mixpanel.people.set({ asset_count: 123 // aktueller Tageswert });LBKSWichtig: mixpanel.identify(userId) muss vorher aufgerufen werden, damit das Profil dem richtigen Nutzer zugeordnet wird. [JS identify & set]
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.
