Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Important
This feature is in Beta. Workspace admins can control access to this feature from the Previews page. See Manage Azure Databricks previews.
This page answers frequently asked questions about the managed Amplitude ingestion connector in Lakeflow Connect. For FAQs that apply to all managed connectors, see Managed connector FAQs.
Which Amplitude plans does the connector require?
The cohorts table uses the Behavioral Cohorts Download API, which is limited to 500 requests per month on Growth and Enterprise plans. Amplitude documents no plan requirement for the Export API, events list, or annotations. See Behavioral Cohorts API.
Which tables does the connector support?
The connector supports four source tables: events, events_list, cohorts, and annotations. For their destination schemas, see Destination table schemas.
How far back can the connector ingest data?
The events table is incremental. The first sync ingests events from the start_datetime option, which defaults to 1970-01-01T00:00:00Z (all available history). Later syncs ingest events by server_upload_time. Amplitude makes export data available within 2 hours of receiving an event, and a single export query covers at most 365 days. The events_list, cohorts, and annotations tables reingest all available records on every run.
Which authentication methods does the connector support?
The connector supports basic authentication with an Amplitude project API Key and Secret Key. OAuth U2M, OAuth M2M, and basic username and password authentication are not supported.