Amplitude: Import Events
Importing events from Amplitude enables you to refine audience definitions within Lytics. Beyond just basic event triggers, Lytics can apply its ML-powered behavioral scoring and content affinity to enhance user profiles.
Integration Details
- Implementation Type: Server-side.
- Implementation Technique: REST API.
- Frequency: One-time batch, or hourly continuous updates.
- Resulting Data: User fields and raw event data (see additional fields).
This integration utilizes the Amplitude Export API to retrieve event data. On each run of the job, it will:
- Request an export of zipped event data in a JSON format.
NOTE: If the user opted to backfill events, on the first run of the job it will request all events from the time frame selected by the user. Otherwise the import requests a file of all events between the current and previous run. - Ingest the data from the JSON files into the Lytics data stream
amplitude_events
.
Fields
The following fields are included in the default mapping from the amplitude_events
stream:
Source Field | Lytics User Field | Description | Type |
---|---|---|---|
event_type | amplitude_events | Amplitude Event Count | map[string]int |
schema | amplitude_schema | Amplitude Schema | int |
event_time | amplitude_event_time | Amplitude Event Time | date |
server_upload_time | amplitude_server_upload_time | Amplitude Server Upload Time | date |
city | amplitude_city | Amplitude City | string |
app | amplitude_app | Amplitude App | int |
device_carrier | amplitude_device_carrier | Amplitude Device Carrier | string |
platform | amplitude_platform | Amplitude Platform | string |
os_version | amplitude_os_version | Amplitude OS Version | string |
user_creation_time | amplitude_user_creation_time | Amplitude User Creation Time | date |
paying | amplitude_paying | Amplitude Paying | boolean |
dma | amplitude_dma | Amplitude DMA | string |
group_properties.* | amplitude_group_properties | Amplitude Group Properties | map[string]string |
user_properties.* | amplitude_user_properties | Amplitude User Properties | map[string]string |
event_properties.* | amplitude_event_properties | Amplitude Event Properties | map[string]string |
client_upload_time | amplitude_client_upload_time | Amplitude Client Upload Time | date |
insert_id | amplitude_insert_id | Amplitude Insert ID | string |
event_type | amplitude_event_type | Amplitude Event Type | string |
library | amplitude_library | Amplitude Library | string |
amplitude_attribution_ids | amplitude_attribution_ids | Amplitude Attribution IDs | string |
device_type | amplitude_device_type | Amplitude Device Type | string |
device_manufacturer | amplitude_device_manufacturer | Amplitude Device Manufacturer | string |
location_lng | amplitude_location_lng | Amplitude Location lng | float |
event_id | amplitude_event_id | Amplitude Event ID | int |
location_lat | amplitude_location_lat | Amplitude Location lat | float |
os_name | amplitude_os_name | Amplitude OS Name | string |
amplitude_event_type | amplitude_event_type | Amplitude Event Type | string |
device_brand | amplitude_device_brand | Amplitude Device Brand | string |
data | amplitude_data | Amplitude Data | string |
device_id | amplitude_device_id | Amplitude Device ID | string |
language | amplitude_language | Amplitude Language | string |
device_model | amplitude_device_model | Amplitude Device Model | string |
country | country | Amplitude Country | string |
region | region, state | Amplitude Region/State | string |
is_attribution_event | amplitude_is_attribution_event | Amplitude Is Attrivbution Event | boolean |
session_id | amplitude_session_id | Amplitude Session ID | string |
device_family | amplitude_device_family | Ampitude Device ID | string |
sample_rate | amplitude_sample_rate | Amplitude Sample Rate | string |
client_event_time | amplitude_client_event_time | Amplitude Client Event Time | date |
idfa | amplitude_idfa | Amplitdue Idfa | string |
adid | amplitude_adid | Amplitude Adid | string |
user_id | amplitude_user_id unique id | Amplitude User ID | string |
amplitude_id | amplitude_id unique id | Amplitude Amplitude ID | string |
Additional fields
The following fields are not included in the default mapping, reach out to the customer support team to add them to the mappings for your account.
Source Field | Lytics User Field | Description | Type |
---|---|---|---|
server_received_time | amplitude_server_received_time | Amplitude Server Received Time | date |
processed_time | amplitude_processed_time | Amplitude Processed Time | date |
version_name | amplitude_version_name | Amplitude Version Name | string |
start_version | amplitude_start_version | Amplitude Start Version | string |
uuid | amplitude_uuid | Amplitude UUID | string |
ip_address | amplitude_ip_address | Amplitude IP Address | string |
Configuration
Follow these steps to set up and configure an import job for Amplitude in the Lytics platform. If you are new to creating jobs in Lytics, see the Jobs Dashboard documentation for more information.
- Select Amplitude from the list of providers.
- Select the Import Activity Data job type from the list.
- Select the Authorization you would like to use or create a new one.
- Enter a Label to identify this job you are creating in Lytics.
- (Optional) Enter a Description for further context on your job.
- Complete the configuration steps for your job.
- In the Backfill Days numeric field, enter how many days in the past do you want to import events (default is 90 days). Select 0 if you want to start from now on.
- (Optional) Toggle Show Advanced Options. Select the Keep Updated checkbox to import events hourly.
- Click Start Import.