Amplitude

Amplitude is a product analytics platform that enables you to build products by tracking and understanding user behavior.

Amplitude integration relies on the Amplitude Query product add-on, which utilizes a Snowflake database to store data.

Amplitude integrations can replicate event and merged user ID data.

See the Schema section for a list of objects available for replication.

A high-level look at this connector, including useful links, and supported features.

Feature/Capability	Support details
Supported Qlik Talend Data Integration projects	Replication projects only. Data pipeline projects are not supported.
Target update methods	Replication tasks: Apply changes Store changes Landing data in a data lake tasks: Change data capture (CDC)
Managing metadata	Manual metadata generation is not required.
Schema evolution	Only the Change column data type operation is supported.
Replication of LOB columns (NCLOB, CLOB, and BLOB)	Not supported.
Scheduled CDC	Required. This is how the target is kept up-to-date with changes to the source. For replication tasks, see Scheduling tasks For lake landing tasks, see Scheduling CDC for lake landing tasks
Notifications	Partially supported Setting notifications for changes in operation
Monitoring	CDC-only, as full load is not relevant for this connector. Monitoring an individual data task
Automatic denesting of JSON column payloads	Not supported. JSON column payloads in source datasets are not denested automatically on the target.

Preparing for authentication

To access your data, you need to authenticate the connection with your account credentials.

Make sure that the account you use has read access to the tables you want to fetch.

Creating the connection

For more information, see Connecting to SaaS applications.

Fill in the required connection properties.
Provide a name for the connection in Connection name.
Select Open connection metadata to define metadata for the connection when it has been created.
Click Create.

Connection settings
Setting	Description
Data gateway	Select a Data Movement gateway if required by your use case. Information note This field is not available with the Qlik Talend Cloud Starter subscription, as it does not support Data Movement gateway. If you have another subscription tier and do not want to use Data Movement gateway, select None. For information on the benefits of Data Movement gateway and use cases that require it, see Qlik Data Gateway - Data Movement.
Start Date	Enter the date, in the format `MM/DD/YYYY`, from which the data must be replicated from your source to your target.
Amplitude Snowflake Username	Enter your Snowflake username.
Amplitude Snowflake Password	Enter the Snowflake user's password.
Amplitude Snowflake Account	Enter the Snowflake account.
Amplitude Snowflake Warehouse	Enter the name of the Snowflake warehouse.
Amplitude Snowflake Database	Enter the name of the Snowflake database.

Schema

Schemas and naming conventions can change from version to version. It is recommended to verify your version before continuing.

The schema and info displayed below is for version 1.

Amplitude replicates two types of tables: Events and merged user IDs.

For each project in your Amplitude account, a set of these tables will be available for replication. Stitch will append a project’s ID to each table name to make them easily identifiable. For example: If a project has an ID of 168342, the events table for the project will be named events_168432.

You can identify which tables are for a specific project by comparing the ID in the table name to the projects in your Amplitude account. You can access this page in your Amplitude account by clicking the User menu (top right corner) > Settings > Projects.

Highlighted project ID field in the Amplitude UI

Depending on your destination, table and column names may not appear as they are outlined below.

events

events_[project_id] tables contain info about the events logged in your Amplitude projects.

Note: Each event table will have the project ID appended. For example: If a project has an ID of 168342, the events table for the project will be named events_168432.

Replication Method	CDC
Primary Key	uuid
Replication Key	event_time
Useful links	Amplitude documentation

adid

STRING

amplitude_event_type

STRING

amplitude_id

NUMBER

app

NUMBER

city

STRING

client_event_time

DATE-TIME

client_upload_time

DATE-TIME

country

STRING

data

STRING

device_brand

STRING

device_carrier

STRING

device_family

STRING

device_id

STRING

device_manufacturer

STRING

device_model

STRING

device_type

STRING

dma

STRING

event_id

NUMBER

event_properties

STRING

event_time

DATE-TIME

event_type

STRING

followed_an_identity

BOOLEAN

groups

STRING

idfa

STRING

ip_address

STRING

location_lat

NUMBER

location_lng

NUMBER

os_name

STRING

os_version

STRING

paying

STRING

region

STRING

server_upload_time

DATE-TIME

session_id

NUMBER

start_version

STRING

user_creation_time

DATE-TIME

user_id

STRING

user_properties

STRING

uuid

STRING

version_name

STRING

merge_ids

merge_ids_[project_id] tables contain info about merged users. These are users whose records have been merged with other user records to eliminate duplicates.

For example: If an anonymous user logs events anonymously before signing in, they will go from being anonymous to a recognized user. Without merging the user’s records, it’ll look like two users with two sets of events, rather than one user completing a series of events.

For more info on how Amplitude handles merging users, refer to their documentation.

Note: Each table will have the project ID appended. For example: If a project has an ID of 168342, the merged ID table for the project will be named merge_ids_168432.

Replication Method	CDC
Primary Keys	amplitude_id merge_server_time merged_amplitude_id merge_event_time
Replication Key	merge_event_time
Useful links	Amplitude documentation

amplitude_id

NUMBER

merge_event_time

DATE-TIME

merge_server_time

DATE-TIME

merged_amplitude_id

NUMBER

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!

Leave your feedback here