All Collections
Integrations
Google Analytics 4
Google Analytics 4: Set Up Best Practices
Google Analytics 4: Set Up Best Practices

How to best set up your GA4 property for optimized performance with the MNTN integration.

Tori Cipollone avatar
Written by Tori Cipollone
Updated over a week ago

MNTN’s direct integration with Google Analytics allows you to view your MNTN campaign performance alongside your other marketing channels. The guide below outlines the optimal setup to ensure your MNTN data is properly reflected within Google Analytics.


Map your Google Analytics Measurement ID to MNTN

Our Google Analytics integration is powered by the Google Analytics Measurement Protocol API. To pass your campaign data to GA, you will need to provide your account’s Measurement ID to the MNTN team.

Our Pixel automatically maps your Measurement ID based on what is on your site. Still, it's always important to confirm that data is going to the correct location if you have multiple data streams within your GA4 account or need to define a specific stream to send data to.

Instructions for locating your Measurement ID can be found here: https://intercom.help/mntn/en/articles/6633933-where-can-i-find-my-ga4-measurement-id

Set Channels that can receive attribution credit in Google Analytics

Google Analytics 4 has a setting that allows only Google paid channels to receive session and conversion credit in attribution. This setting will not allow channels like MNTN to get credit within the platform. Ensure Channels that can receive credit are set to Paid and organic channels.

Instructions for selecting your attribution settings can be found here: https://support.google.com/analytics/answer/10597962

Set Conversion Windows in Google Analytics

Conversion windows determine how far back in time a touchpoint is eligible for attribution credit. We recommend setting the Acquisition key events to 30 days and All other key events to 90 days. The Engaged-view key events setting does not impact MNTN data.

Instructions for setting your conversion can be found here: https://support.google.com/analytics/answer/10597962

Set your Reporting Identity in Google Analytics

If you are leveraging a 3rd Party implementation for funneling data into Google Analytics from your website (such as Segment, Elevar, or Shopify), we recommend updating your Reporting Identity to Device-based. This will ensure consistent identity resolution between your MNTN-driven events and Google Analytics events to get the most accurate representation of MNTN performance.

💡Note: Google Signals and Modeling data can create hashed identifiers that do not match the GA Client IDs passed from our integration, and therefore the Integration will not work as expected.

If you are experiencing low engagement metrics associated with MNTN and have activated Google Signals or Google Modeled Data methods, we recommend working directly with the Platform Experience team.

Instructions for setting our reporting identity can be found here: https://support.google.com/analytics/answer/10976610

Set your Visit Tracking tags in MNTN

By default, MNTN will auto-populate UTM tracking tags on your creatives in the campaign setup process. We recommend reviewing your UTMs each time you upload new creative to ensure they follow your preferred setup. This will make it easy for you to filter for your MNTN campaign performance within Google Analytics when viewing the Traffic Acquisition report.

Instructions for customizing your Visit Tracking Tags can be found here: https://intercom.help/mntn/en/articles/6633832-implementing-site-served-visit-tracking-tags

Align your Conversion Events in Google Analytics and MNTN

To ensure you are able to compare MNTN performance with your Google Analytics performance appropriately, we recommend ensuring you are tracking the same conversion events both in Google Analytics and in the MNTN account.

⏸️ GA4 Server-Side Tagging

If you are leveraging a server side implementation, we recommend working directly with the Platform Experience team to assist in setup and monitoring performance.

Did this answer your question?