Google Analytics Connector MAR Overview

File connector data sources like the Google reporting connectors 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 towards monthly active rows. 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 3 days. Once a day, we also sync data from the last 7th, 15th and 30th day to get conversion-related data. This helps us to fetch all of your important data using fewer API calls.

What Contributes Towards MAR?

There are 5 primary actions that will contribute toward MAR:

The Historical Sync Timeframe (ex. 12 months vs 3 months) will impact MAR on a full re-sync and you cannot modify this once the connector is created.
Before setting up your Google Analytics connector(s), as a best practice for report qa, testing, and preventative troubleshooting, it is highly recommended that you test out your desired combinations of metrics and dimensions for compatibility using the Google Analytics Dimensions & Metrics explorer tool as well as the GA Query Explorer tool which will allow you to run sample queries that will hit the same GA reporting api that Fivetran’s connectors also use.
Aggregation (Hour, Day, Month) cannot be changed once a connection has been created. The more granular the aggregation window will increase MAR.
NOTE: Multiple reports can be created 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.

Related to