Google FAQs

1. Go to Platform Home from the GMP Product hamburger menu
2. Navigate to Administration, and select the client Organization
3. Select Analytics
4. Select the correct standard GA4 Analytics Account
5. Expand the Properties tab
6. Click on the word Standard on the properties list (it doesn’t look clickable)
7. Click on the word Standard in the property screen (it doesn’t look clickable)
8. Select the 360 radio button and hit Save
   

• Go to Platform Home from the GMP Product hamburger menu
• Navigate to Administration, and select the client Organization
• Select Analytics
• Select the correct standard GA4 Analytics Account
• Expand the Properties tab
• Click on the word Standard on the properties list (it doesn’t look clickable)
• Click on the word Standard in the property screen (it doesn’t look clickable)
• Select the 360 radio button and hit Save

Thresholding is applied as a privacy measure to prevent reporting of sensitive information 

You may observe reports with a yellow exclamation mark with the following note:  “Google Analytics has applied thresholding to one or more cards in this report and will only display the data when the data meets the minimum aggregation thresholds.”  Thresholding is not the same as sampling and is a privacy-related measure to prevent access to user level metrics and data that may allow the inference of users based on the signals presented.

Cross-domain tracking enables precise attribution of activity to a singular user across different domains. In instances where outbound clicks typically trigger an event through enhanced tracking, they are disregarded if the link leads to a domain included in cross-domain tracking configurations.

1. Log into Google Analytics.
   
   1. For the Further Google Support team, we suggest using the support-team@gofurther.com account.
   2. Login credentials can be found in 1password.
2. Select the account/property in question.
   
   1. Select the account in question.
   2. Click on the admin gear icon in the bottom left.
   3. Then click on Property details.
      
      1. For all support tickets the Property ID is a required field.
3. Click on the question mark in the top right of the menu.
4. Click on Get more help.
5. Scroll down in the Help pop up and click on “Contact us”.
   
   1. Tip: This pop up is moveable. It might be in the way of a screenshot you are trying to grab but you can move it around the window.
6. Fill in the "What can we help with" field.
   
   1. There are only 100 characters allowed in this field.
   2. A simplified version of your question/concern is fine to continue to the next step.
      
      1. For Example, Does Auto-tagging override UTM parameters?
      2. Tip: If you select the Email communication option, this will be automatically filled in the form’s Full Description. Your simplified question can be used as the Subject, and you can use the Full Description field to better detail the issue.
7. Select how you would like to communicate with Google (Chat or Email)
   
   1. Email is better for more complex issues. Chat should be used for quick confirmations.
      
      1. For Example, Does Auto-tagging override UTM parameters?
      2. Tip: You may want to carve out a 30-minute block if you are using the chat option.
         
         1. Once the rep has the information, they check in every 10 mins to keep the chat open, but it may take them some time to provide an answer.
8. Fill in the rest of the required fields for the communication method you select and click Submit.

‍

The goal is to standardize ‘conversion’ reporting between Google Ads and GA4. Advertising attribution reports will include any attribution settings in Google Ads, while the behavioral reports will continue to use existing GA4 attribution models. This way, if a user wants to compare ‘conversion’ attribution between the tools, the ‘Advertising’ reports will be the best place to do that as the Google Ads data should match what is reported in that platform. The hope is that this will cut down on confusion by separating ‘behavioral’ reporting (with session/user-scoped dimensions) and ‘advertising performance’ reporting (with event-scoped dimensions leveraging data-driven attribution and Google Ads attribution settings).

Key events still factor into built-in metrics (like engaged sessions, engagement rate) and can be shared with the Ad Platforms for conversion measurement.They are also used to calculate session and user conversion rate in GA4 reports

Only see ‘conversions’ in the Advertising reports for Key Events that have been shared with Google Ads. If you do not have any link to Google Ads you will not have any Advertising Reports in your GA4 property.

Key event limits will be the same as the conversion limits were prior to this change.

Both conversions and key events will include modeled data.

The ‘counting method’ for key events (choose between ‘once per session’ and ‘once per event’ will still be able to be adjusted.

1. Go to the Firebase Console (console.firebase.google.com) and log in to your account.
2. Select the Firebase project you wish to link to GA4. If you don't have a project yet, you can create one from the Firebase Console.
3. Inside the Firebase project dashboard, find and click on the "Integration" tab from the left sidebar.
4. Look for the Google Analytics card and click on "Get Started."

Google Analytics 4 (GA4) offers both a free tier and a paid tier called 360. Both tiers offer many of the same features, but 360 raises loosens the limits placed on the free tier. 

We recommend all ecommerce websites and apps include a few important parameters in every applicable event:

• Currency
• Value
• Item_id
• Item_category
• Item_variant
• Price: 
• Quantity
• User_id
• Platform

Google’s Universal Analytics has a 13-month historical back-fill to BigQuery, meaning it provides data up to 13 months prior to the date you link your property + view ID to BigQuery. On the other hand, GA4, on the other hand, will not back-fill historical data, and it will only start to populate BigQuery from the day you link GA4 to BigQuery.

In previous versions of Google Analytics, traffic acquisition metrics were based on sessions, which were defined as a group of interactions that a user had with a website within a given time frame. Sessions were categorized by their source and medium, such as organic search, direct, referral, social, email, etc. These metrics helped website owners understand where their visitors came from and how they engaged with their site.

In GA4, however, sessions are no longer the primary unit of analysis. Instead, GA4 focuses on events, which are individual actions that users take on a website, such as page views, clicks, downloads, purchases, etc. Events can be automatically collected by GA4 or customized by the website owner. Events are also categorized by their source and medium, but they are not grouped into sessions. This means that GA4 does not report on session-based metrics such as bounce rate, session duration, pages per session, etc.

To help you identify and understand the root causes of data differences between UA and GA4, Google has developed a tool called Data Discrepancy Assistant. This tool allows you to compare the data reported by UA and GA4 for a specific date range and dimension (such as source/medium, device category, etc.). It also provides explanations for each discrepancy based on the factors mentioned above.

To use the Data Discrepancy Assistant tool, you need to have access to both a UA property and a GA4 property that are linked together. You also need to have the same level of access to both properties. 

Google's New Google Analytics 360 License is an updated version of the Analytics 360 Suite, providing enterprise-level analytics features for businesses. It includes access to Google Analytics 4 (GA4) properties and 360-enabled Universal Analytics (UA) properties.

For upgrading GA4 properties, users on the New Google Analytics 360 License can refer to the official documentation and resources provided by Google or work with your Google Analytics License Reseller. Similarly, users on the Universal Analytics License can find instructions for upgrading their properties before the specified sunset date to avoid data gaps as well as confirm with your Google Analytics License Reseller if your Universal Properties are still eligible for the upgrade.

To get a better understanding of why such a reporting difference exists, it is important to evaluate the tools separately from each other. From what could be found, UA and Looker Studio complement each other as a 1:1 match in data reporting. This would make sense as Looker Studio would provide a general high-level reporting while UA would give a more detailed analysis. This tells us that the difference in reporting with GA4 might boil down to a difference in data aggregation. Using UA as a substitute for Looker Studio, the discrepancy can be seen clearer on what GA4 does differently with its data.