# Amplitude: Event Enhanced ## Description * Each record represents event data, enhanced with event type data and unnested event, group, and user properties. ## Supported Data Sources * Amplitude ## Columns | Type | Name | Description | | -------- | ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | STRING | unique\_event\_id | A unique key for each event, concatenating event\_id, device\_id, and client\_event\_time | | STRING | unique\_session\_id | Unique key of each session, concatenating user\_id and session\_id | | STRING | amplitude\_user\_id | Unique key for each user, which is user\_id by default. If user\_id does not exist, use amplitude\_id | | INTEGER | event\_id | A counter that distinguishes events | | STRING | event\_type | The assigned type of event. Example 'Add Friend' | | DATETIME | event\_time | Amplitude timestamp (UTC) which is the client\_event\_time adjusted by the difference between server\_received\_time and client\_upload\_time, specifically: event\_time = client\_event\_time + (server\_received\_time - client\_upload\_time) 2015-08-10T12:00:00.000000 We use this timestamp to organize events on Amplitude charts. Note: If the difference between server\_received\_time and client\_upload\_time is less than 60 seconds, the event\_time will not be adjusted and will equal the client\_event\_time | | DATE | event\_day | Day of event time | | INTEGER | event\_type\_id | Event type ID | | STRING | event\_type\_name | Event type name | | INTEGER | session\_id | The session start time in milliseconds since epoch. All events within the same session share the same session ID. By default, the setting in Amplitude for the session property is session ID. All events with the same session ID and the same user ID will be grouped into the same session. The session ID does not have to be unique across multiple users. Session IDs for events sent via the Amplitude SDKs are automatically generated and managed. However, for events sent via the HTTP API, Amplitude defaults to a session ID of -1. This means the event is excluded from all session metrics. | | INTEGER | session\_event\_number | The number of the event within the session, ordered by time of event. | | INTEGER | user\_event\_number | | | STRING | group\_types | Group types. "Groups" in the source table, renamed here. See the Accounts documentation for more information. | | STRING | user\_id | A readable ID specified by you. Amplitude uses a combination of three different methods to identify your users: device IDs, Amplitude ID, and user IDs. The first comes directly from your users' devices, while the second is an ID that Amplitude automatically creates once it has enough information to conclusively identify a unique user. The user ID, however, is something you'd set up. In Amplitude, a user ID is a unique identifier applied to individual users. Using them is optional, but recommended: your product should set a user ID once a user has created an account, logged in, or is otherwise identified in your product. Amplitude can use a user ID to reconcile events across multiple devices under the same user ID. Additionally, a user's event data will be merged on the backend so that all anonymous events prior to the assignment of a user ID will be connected to the correct user. For this reason, you can wait to assign user IDs if that makes sense for your product. Conversely, this is also why you should not set user IDs for anonymous users. Once set, user IDs in Amplitude cannot be changed.Once set, user IDs in Amplitude cannot be changed. | | DATETIME | user\_creation\_time | Event\_time (UTC) of the user's first event | | STRING | amplitude\_id | An internal ID used to count unique users. | | INTEGER | app | Project ID found in your project's Settings page | | INTEGER | project\_name | Project ID | | INTEGER | version\_name | The app version | | DATETIME | client\_event\_time | Local timestamp (UTC) of when the device logged the event. | | DATETIME | client\_upload\_time | The local timestamp (UTC) of when the device uploaded the event. | | DATETIME | server\_received\_time | Amplitude timestamp (UTC) of when servers received the event | | DATETIME | server\_upload\_time | Amplitude timestamp (UTC) of when the event data was uploaded to Amplitude servers | | INTEGER | city | City | | STRING | country | Country | | INTEGER | region | Region | | STRING | data | Dictionary where certain fields such as first\_event and merged\_amplitude\_id are stored. | | INTEGER | location\_lat | Latitude | | INTEGER | location\_lng | Longitude | | INTEGER | device\_brand | Device brand | | INTEGER | device\_carrier | Device carrier. | | INTEGER | device\_family | Device family. Apple iPhone | | STRING | device\_id | The device specific identifier | | INTEGER | device\_manufacturer | Device manufacturer | | INTEGER | device\_model | The device model | | INTEGER | device\_type | Device type | | STRING | ip\_address | IP address | | INTEGER | os\_name | OS name | | INTEGER | os\_version | OS version | | INTEGER | platform | Platform of the device. | | INTEGER | language | The language set by the user | | INTEGER | dma | Designated marketing area (DMA) | | INTEGER | schema | Schema ID | | INTEGER | start\_version | App version the user was first tracked on | | INTEGER | totals | The total number of times the event has happened this week | | STRING | value | Name of the event in the raw data. | | INTEGER | events\_per\_session | The count of events in a session | | DATETIME | session\_started\_at | The time of the first event in a session | | DATETIME | session\_ended\_at | The time of the last event in a session | | INTEGER | user\_session\_number | | | DATETIME | session\_started\_at\_day | | | DATETIME | session\_ended\_at\_day | | | DECIMAL | session\_length\_in\_minutes | | | INTEGER | is\_first\_user\_session | Boolean of whether or not a session is the user's first session | | DECIMAL | minutes\_in\_between\_sessions | | | STRING | unique\_key | | --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://endash-guidance-docs.gitbook.io/cigro-data-templates/data-model-templates/amplitude-event-enhanced.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.