Hello Fivetran Support,

We use the Bitly Lite connector to sync Bitly data into Databricks for reporting. We need to know whether we can reconstruct what a Bitlink's destination URL and related UTM/association data looked like on a past date.

Your Bitly connector documentation says BITLINK and its child tables are re-imported weekly to capture updates and deletes, and that History Mode is not supported. Could you confirm how this works for our connection and the BITLINK/association tables?

• When a Bitlink or association is updated, does the destination table overwrite the prior values, or is any previous version retained?

• Are _fivetran_deleted and _fivetran_synced available on BITLINK and its child tables? Which tables support delete capture, and how are updates represented?

• Does _fivetran_synced indicate when Bitly changed a row or when Fivetran synced it? Is a source-side modified timestamp available?

• What is the expected detection delay for updates and deletes given the weekly re-import? Are there cases where a change or deletion is not captured?

• Is there a native Fivetran setting or supported approach for retaining historical Bitlink and association versions in Databricks, even though the connector's docs show History Mode as unsupported?

• If history must be maintained downstream, what sync-completion signal should we use before taking a daily snapshot, and are there connector-specific caveats?

Our goal is to preserve dated redirect and association history so analysts can reproduce older direct-mail reporting. Please clarify the behavior for our current connection and the relevant tables. We can provide the connection ID and schema details through your secure support portal if needed.