Which connector?: Braze

Additional details: Over the course of https://support.fivetran.com/hc/en-us/requests/367638, we discovered that the Braze Currents incremental sync does not collaborate with the functionality of the Braze Currents export to the cloud storage location. Braze Currents segregates event data into folders separated by hour, likely the hour matching the event timestamp. It is reasonable to assume that events aren't mutated after they're captured since Braze currents is an event stream.

Instead of taking advantage of this, the Braze connector currently incrementally fetches files based on the lastmodified timestamp. This works well for entities like campaigns and canvasses, but it doesn't make much sense for Braze Currents data.

I'd like to propose that the Fivetran Braze connector is updated such that, specifically for Braze currents, incremental syncs use the event timestamp organization rather than the lastmodified timestamp of the files themselves, and therefore minimize the amount of data required to be scanned and reduce the amount of duplicate data moving per-sync.