Google Analytics Connector Sync Overviewlink
File connector data sources like Google Analytics do not provide change-tracking data to help us determine if the file has been updated in the source. As a result, Fivetran re-syncs the entire file every time a sync is scheduled. That means each row in the source counts to monthly active rows (MAR). However, if the file is updated multiple times in a month, its rows only count toward monthly active rows once.
In our Google Analytics connector, we use a trailing window instead of a rollback sync. During every sync cycle we sync data from the last 2 days. Once a day, we also sync data from 7 days ago and 30 days ago to get conversion-related data. This helps us fetch all of your important data using fewer API calls.
What contributes to MAR?link
The following main factors contribute to MAR:
- The number of accounts synced (the ‘Sync All Accounts’ vs. ‘Sync Specific Accounts’ setting)
- The number of profiles under each account selected
- Optional segments selected
- Optional filters used
- Historical Sync
- Aggregation (hour vs. day vs. month)
Managing MAR for Google Analytics connectorlink
The Historical Sync Timeframe (for example, 12 months or 3 months) will impact MAR during connector re-syncs. You cannot modify this setting once the connector is created. Before setting up your Google Analytics connectors, we highly recommend that you test out your desired combinations of metrics and dimensions for compatibility as a best practice for report QA, testing, and preventative troubleshooting. You can use the Google Analytics Dimensions & Metrics explorer tool and the GA Query Explorer tool. These tools let you run sample queries that call the same Google Analytics reporting API that Fivetran connectors use. You cannot change the aggregation (hour, day, or month) once the connector has been created. The more granular aggregation windows will increase MAR.
NOTE: You can create multiple reports within a single Google Analytics connector, but the account (all or specific selected) is configured at the connector level, not at the individual report (table) level.