This is a Jitsu.Classic documentation. For the lastest version, please visit docs.jitsu.com. Read about differences here.
Amplitude API
Jitsu supports Amplitude as a destination. All event fields after Mapping Step will be formatted as JSON body and will be sent via Amplitude API with HTTP POST request.
Amplitude destination supports only stream
mode and
should have mapping rules compatible with
Amplitude API parameters. See mapping below
Filtering events#
For filtering events stream to prevent sending all events to Amplitude table_name_template
is used.
For more information see Table Names and Filters.
Configuration#
Amplitude destination config consists of the following schema:
destinations:
my_amplitude:
type: amplitude
mode: stream
amplitude:
api_key: <YOUR_API_KEY> #see below how to get it from Amplitude
data_layout:
table_name_template: "$.event_type" #Optional. It is used for filtering events.
mappings:
keep_unmapped: false
fields:
- src: /user/email
dst: /user_id
action: move
- src: /user/anonymous_id
dst: /device_id
action: move
- src: /event_type
dst: /event_type
action: move
- src: /parsed_ua/os_family
dst: /os_name
action: move
- src: /parsed_ua/os_version
dst: /os_version
action: move
- src: /parsed_ua/os_version
dst: /os_version
action: move
- src: /parsed_ua/device_brand
dst: /device_brand
action: move
- src: /parsed_ua/device_family
dst: /device_manufacturer
action: move
- src: /parsed_ua/device_model
dst: /device_model
action: move
- src: /location/country
dst: /country
action: move
- src: /location/region
dst: /region
action: move
- src: /location/city
dst: /city
action: move
- src: /user_language
dst: /language
action: move
- src: /location/latitude
dst: /location_lat
action: move
- src: /location/longitude
dst: /location_lng
action: move
- src: /source_ip
dst: /ip
action: move
- src: /eventn_ctx_event_id
dst: /insert_id
action: move
Amplitude credentials#
Field | Type | Description |
---|---|---|
api_key (required) | string | Amplitude project API Key from the Project Settings page. |