We now obfuscate the apiKey and secretKey values in the connector setup form.
You can now exclude the
EVENT_AMPLITUDE_ATTRIBUTION_ID table from the sync. On your connector details page, go to the Schema tab and deselect the table.
By default, we include the
EVENT_AMPLITUDE_ATTRIBUTION_ID table in the sync. If you exclude the table and later want to sync the table, perform a complete table re-sync to ensure data integrity.
You can now configure your Amplitude connector using the Fivetran REST API. This feature is in BETA and is available only for Standard and Enterprise accounts.
We no longer deliver a separate column for each custom field in the
EVENTS table. The
EVENTS table now syncs custom fields as JSON objects in the following columns:
Storing custom fields as JSON objects speeds up syncs and avoids hitting column limits in your destination.
We will deprecate the separate custom field columns after three months, so adjust your scripts accordingly. You must also re-sync your
EVENTS data during this time so that all your custom field data is in the new format before the separate columns are deprecated.
The Amplitude connector now supports priority-first sync. Priority-first syncs fetch your most recent data first so that it’s quickly ready for you to use. Amplitude’s priority-first syncs fetch the most recent 15 days of data from all tables.
To learn more, see our priority-first sync documentation.
We have added a new field
user_id to the
We have deleted the
USERtable and all its dependent tables:
All the information in those tables exist in
We have changed the value of
2014-07-16. This change means that for most Amplitude tables (except
EVENT_TYPE), we only sync data that was created after July 16, 2014. We have made this change to protect the integrity of your data.
Amplitude introduced the
client_event_time parameter, a part of the primary key for the
EVENT table, on July 16, 2014. Because earlier events don’t have the
client_event_time parameter, we can’t form the primary key for them. Without the primary key, we cannot deduplicate the data. Therefore, we cannot write that data to the destination if that data was created before Amplitude introduced the
Added 3 new tables
Changed the primary key from event_id, projectName to event_id, device_id, client_event_time in
Added a new table
EVENT_AMPLITUDE_ATTRIBUTION_ID. Changed the primary key from
Amplitude is a comprehensive product analytics software for web and mobile.
We have added a new table,