Release Noteslink
December 2020link
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.
April 2020link
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.
December 2019link
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:
data
event_properties
groups
group_properties
user_properties
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.
November 2019link
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.
May 2019link
We have added a new field user_id
to the EVENT
table.
April 2019link
-
We have deleted the
USER
table and all its dependent tables:USER_ALIAS_ID
USER_AMPLITUDE_ID
USER_ALIASING_PROFILE
USER_PROPERTY
USER_MERGE_TIME
-
All the information in those tables exist in
EVENT
table itself.
March 2019link
We have changed the value of initial_sync_start_time
to 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 client_event_time
parameter.
-
Added 3 new tables
USER_ALIASING_PROFILE
USER_PROPERTY
USER_MERGE_TIME
-
Changed the primary key from event_id, projectName to event_id, device_id, client_event_time in
EVENT
table. DeletedDEVICE
table.
February 2019link
Added a new table EVENT_AMPLITUDE_ATTRIBUTION_ID
. Changed the primary key from user_id
to amplitude_id
and project_name
in USER
table.
January 2019link
Amplitude is a comprehensive product analytics software for web and mobile.
Link to Amplitude Documentation
We have added a new table, EVENT_AMPLITUDE_ATTRIBUTION_ID
.