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