Oliver E.

Shorter refresh frequency for user/group tables Currently, we do a full sync of our user/group tables on a weekly basis, as this is the shortest frequency at which you can do a full sync. We are not interested in switching to incremental as we only care about current user/company state. It would be nice if we could reduce the frequency of this full sync, as we are not worried about underlying data scan volume, and would prefer to do a full sync daily instead of weekly.

Ability to Trigger a Full Refresh for an Event Data Source Currently, when we make changes to the underlying transformations in BigQuery which get the data into the Mixpanel schema (i.e with standardised event_name, event_time, user_id, company_id fields, and dynamic JSON properties field), we have to delete the warehouse connector for that table and re-create it. In addition to the “Manually Run Sync:” button shown below, it would be great if we could trigger a full refresh of the underlying table to Mixpanel, which would wipe away the data from the source table and reload it, so we don’t have to delete and recreate the warehouse sync for that table each time we do this.

Hi there - I've recently been working to set up warehouse syncs from Google BigQuery to Mixpanel within our organisation and have the following feature requests. Great product - really like it so far. I will put each feature request as a separate message to avoid confusion; Shorter Delay Time for Warehouse Connectors We currently use the following sync settings for our warehouse connectors from BigQuery Timestamp in our context is the time that the message was published (not the time it was inserted into the warehouse table), and this is used as the partition field for our event tables. We don’t have a separate column for the insert time (and even if we did, it would not be the partition), and messages take up to 10 minutes from being published to reach the warehouse tables. To work around this, we round the timestamp down to the nearest hour, and create our syncs at some time past the hour (15 - 20 minutes after) and rely on Event Deduplication using the MessageId to remove duplicate events. Ideally, we would instead like to be able to use the delay functionality in Mixpanel, which can only currently be set to 1 or 2 days, at a much lower interval (15 minutes), so that we still get the data in near-real time but without potentially missing events.