Understanding how the Mixpanel Connector affects MAR
Mixpanel Connector Overview
- Mixpanel utilizes Fivetran’s Priority First sync strategy which syncs the most recent 30 days of Event data during the initial sync.
- Once the most recent 30 days of data has been synced, Fivetran will pull the historical data at regular intervals defined by the connector’s sync frequency
- For the Event and Transaction table Fivetran uses a timestamp as a primary key meaning all events and transactions result in a new row in their respective tables
- The Event table timestamp only supports date level granularity. This means we must re-import the table for each sync that occurs within a given day. Therefore, MAR for the Event table is the high water mark for that day and is not equal to the total number of records inserted for that day.
- For all other tables when Fivetran detects a change in the data, we update or insert (upsert) into the destination, overwriting old data
- Mixpanel does not support deletes
- Custom fields configured in Mixpanel will be captured and synced by Fivetran
What Contributes Towards MAR?
There are 4 primary actions that will contribute toward MAR:
- A new record is inserted.
- For the Event and Transaction table Fivetran uses a timestamp as a primary key meaning all transactions result in a new row
- An existing table is updated (CAMPAIGN or PEOPLE)
- A new custom field is added for a table
- The historical sync after the initial 30 days counts toward MAR
Managing MAR for this Connector
- Table level exclusion is possible but the data is likely valuable to the client
- Limit the events tracked in Mixpanel