Amplitude#
Connect Amplitude with an API key, secret, and backfill start date. The source writes 1 fixed table under titan.amplitude.
select
uuid,
event_id,
event_type
from titan.amplitude.events
limit 10Connect Amplitude#
Open Apps, choose Connect app, and select Amplitude.
Enter an API key, secret, and backfill start date.
Review the tables, then save the source.
Watch Sync history until the first run completes.
Credentials are stored as secrets. They never become lake columns or appear in query results.
Sync behavior#
The first run starts at your configured backfill date. Later runs continue from the last completed interval.
A new source syncs when you connect it and then follows its schedule. The default recurring interval is 4 hours. An interrupted run keeps its completed progress and retries safely.
Every lake table also has the system columns _synced_at and _deleted; the column reference below lists source columns only.
Table reference#
events#
titan.amplitude.events has 40 source columns.
Source field uuid.
Source field event_id.
Source field event_type.
Source field event_time.
Source field user_id.
Source field session_id.
Source field amplitude_id.
Source field amplitude_attribution_ids.
Source field server_received_time.
Source field server_upload_time.
Source field client_upload_time.
Source field client_event_time.
Source field sample_rate.
Source field start_version.
Source field app.
Source field library.
Source field device_carrier.
Source field processed_time.
Source field version_name.
Source field paying.
Source field platform.
Source field os_name.
Source field os_version.
Source field device_id.
Source field device_type.
Source field device_family.
Source field language.
Source field country.
Source field region.
Source field city.
Source field dma.
Source field ip_address.
Source field data.
Source field event_properties.
Source field user_properties.
Source field group_properties.
Source field groups.
Source field location_lat.
Source field location_lng.
Source field insert_id.
Deletes and history#
Rows are merged by their source key. When the source can prove that a row was deleted, Supernova keeps the row and sets _deleted so queries can choose whether to include history. Filter current-state queries with where not _deleted.