what are common event properties to collect?

what are common event properties to collect? | Mixpanel Community

2 comments

· Sorted by Oldest

kapa.ai
APP
·
·
Hi Susan, 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
kapa.ai
APP
·
·
Mixpanel collects a variety of event properties automatically. Here are some examples: 1. Ingestion APIs Event Properties: - $city: The city of the event sender parsed from the IP property or the Latitude and Longitude properties. - $region: The region (state or province) of the event sender parsed from the IP property or the Latitude and Longitude properties. - mp_country_code: The country of the event sender parsed from the IP property or the Latitude and Longitude properties. - $mp_api_endpoint: Mixpanel property to record the API endpoint the data was sent to. - $import: Internal Mixpanel property set to true to indicate that events were sent through /import API. - $mp_api_timestamp_ms: UTC timestamp in milliseconds when the event was received by our API. - mp_processing_time_ms: UTC timestamp in milliseconds when the event was processed by Mixpanel servers. source2. Client-side SDKs Event Properties: - $device_id: Autogenerated ID that is local to the device. - $user_id: The identified ID of the user. - $insert_id: A unique identifier for the event, used to deduplicate events that are accidentally sent multiple times. - mp_lib: The Mixpanel library that sent the event. - $lib_version: Mixpanel library version. - mp_sent_by_lib_version: Mixpanel library version used to send data. - $os: OS of the event sender. - $os_version: The current version of the operating system on the device. - $browser: Name of the browser. - $browser_version: Version of the browser. - $app_build_number: General build of the app. source3. Legacy Automatically Tracked Events: - $ae_first_open: Tracks the first time the user has opened the app. - $ae_updated: Executes when a user updates the app from the previous version. - $ae_session: Executes when a user spends more than 10 seconds in the app. - $ae_iap: Executes when a user conducts an in-app purchase through your app. sourceIn addition to these, you can also define your own custom properties to capture more specific information about the events. For example, a Page Viewed event might have a property called Page URL, which is set to the URL of the page that was viewed. source
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.

kapa.ai
APP
·
·
Hi Susan, 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
kapa.ai
APP
·
·
Mixpanel collects a variety of event properties automatically. Here are some examples: 1. Ingestion APIs Event Properties: - $city: The city of the event sender parsed from the IP property or the Latitude and Longitude properties. - $region: The region (state or province) of the event sender parsed from the IP property or the Latitude and Longitude properties. - mp_country_code: The country of the event sender parsed from the IP property or the Latitude and Longitude properties. - $mp_api_endpoint: Mixpanel property to record the API endpoint the data was sent to. - $import: Internal Mixpanel property set to true to indicate that events were sent through /import API. - $mp_api_timestamp_ms: UTC timestamp in milliseconds when the event was received by our API. - mp_processing_time_ms: UTC timestamp in milliseconds when the event was processed by Mixpanel servers. source2. Client-side SDKs Event Properties: - $device_id: Autogenerated ID that is local to the device. - $user_id: The identified ID of the user. - $insert_id: A unique identifier for the event, used to deduplicate events that are accidentally sent multiple times. - mp_lib: The Mixpanel library that sent the event. - $lib_version: Mixpanel library version. - mp_sent_by_lib_version: Mixpanel library version used to send data. - $os: OS of the event sender. - $os_version: The current version of the operating system on the device. - $browser: Name of the browser. - $browser_version: Version of the browser. - $app_build_number: General build of the app. source3. Legacy Automatically Tracked Events: - $ae_first_open: Tracks the first time the user has opened the app. - $ae_updated: Executes when a user updates the app from the previous version. - $ae_session: Executes when a user spends more than 10 seconds in the app. - $ae_iap: Executes when a user conducts an in-app purchase through your app. sourceIn addition to these, you can also define your own custom properties to capture more specific information about the events. For example, a Page Viewed event might have a property called Page URL, which is set to the URL of the page that was viewed. source
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.