---
canonical: https://further.ai/blog/ga4-guide-chapter-6-setting-up-your-ga4-property
meta-clarity-site-verification: 348d1891-f643-4080-bd66-b7c73102bc6c
meta-description: This guide provides step-by-step instructions on setting up your GA4 property for optimal tracking and analysis.
meta-google-site-verification: WrI8ERHjae8awr7ol2W23H3FbSHdehtwGuAwRBds6EI
meta-og:description: This guide provides step-by-step instructions on setting up your GA4 property for optimal tracking and analysis.
meta-og:image: https://cdn.prod.website-files.com/64fb873eb25058d1bc2035d0/653ab6c177b282f5d9b12db0_Futher%20Web%20Assets_FURTHER_Opengraph.png
meta-og:title: GA4 Guide Chapter 6: Setting Up Your GA4 Property | Further
meta-og:type: website
meta-twitter:card: summary_large_image
meta-twitter:description: This guide provides step-by-step instructions on setting up your GA4 property for optimal tracking and analysis.
meta-twitter:title: GA4 Guide Chapter 6: Setting Up Your GA4 Property | Further
meta-viewport: width=device-width, initial-scale=1
title: GA4 Guide Chapter 6: Setting Up Your GA4 Property | Further
---

# GA4 Guide Chapter 6: Setting Up Your GA4 Property

**Publisher:** Organization Further  
**Author:** Person  
**Published:** Jun 25, 2024

---

[Our Thinking](/our-thinking/blog) > [Blog](/our-thinking/blog) > Google | Partner | Guide

# GA4 Guide Chapter 6: Setting Up Your GA4 Property

**Sep 13, 2022**

Now that we’ve covered the important background of GA4, data collection, and events, this chapter will show you how to get your property configured to start correctly sending data to it.

## ACCOUNT STRUCTURE

### THE ACCOUNT
Each organization typically has one account that houses all of its properties. However, each account can house a mixture of up to 80 Universal Analytics and GA4 properties, subproperties, or roll-up properties. An organization that requires more than 80 properties can request a limit extension but may need multiple accounts.

### PROPERTIES AND DATA STREAMS
Each source property typically represents one brand (which may span multiple domains or subdomains). Within each property, GA4 introduces new data streams. Each property may receive data from up to 50 data streams (websites, apps, etc.).

Every data stream you set up contains a unique measurement ID associated with your gtag or Google Tag Manager configuration. The data from each stream is combined into one property. Because GA4 adopted Firebase’s event-centric data model, a property can now include websites and mobile apps together (if the Firebase SDK tracks them). If you have data from multiple data streams in one property, two built-in dimensions will help you distinguish between them: **Stream ID** and **Stream Name**.

### ROLL-UP PROPERTIES
A roll-up property is a particular type of property that combines the data from multiple (up to 50) source properties into a single property. For example, if you have several brands in separate properties that you want to see separately, but it would also help to view that data together, a roll-up property is a good option. *Just like how it was for Universal Analytics, roll-up properties are only available for 360 customers.*

**Some important features to note:**
- The cost for roll-up property events is one-half the cost of events in the source properties (based on the terms of your 360 contract)
- Data starts accumulating on the day of creation (no historical data before creation)
- Users are deduplicated if they are found across multiple source properties
- Google Signals must be activated in the roll-up property for source property Google Signals data to populate
- Source property data can be identified using the Source Property ID or Source Property Name dimensions

**Actions you can take in a roll-up property:**
- Add or remove users (not inherited from source property)
- Link to Google Ads
- Create custom dimensions and metrics
- Mark events as conversions
- Create audiences

**Actions you can NOT take in a roll-up property:**
- Create new events
- Create a sub-property

### SUBPROPERTIES (A.K.A. THE REPLACEMENT FOR VIEWS)
A [subproperty](https://support.google.com/analytics/answer/11525732?hl=en) is a type of property that gets its data from one other property to govern user access to data and govern data by filtering events. This might be useful if you have several distinct user groups in one user experience. For example, you might need to have one domain with a distinct user flow that’s separated into subproperties for different subdomains, AND the user experience needs to be translated into varying languages. This is possible with subproperties.

Subproperties have replaced views in GA4. The two big differences that you need to know are:
1. *These are only available to 360 customers.*
2. Unlike Universal Analytics views, these are considered properties, which means that they are a part of your 80 property limit, and they have most of the functionality of a regular property (integrations, filters, audiences, etc.).

**Some important features to note:**
- Just like roll-up properties, the cost for sub-property events is one-half the cost of events in the source property (based on the terms of your 360 contract)
- Data starts accumulating on the day of creation (no historical data before creation)

**Actions you can take in a sub-property:**
- Add or remove users (not inherited from source properties)
- Mark events as conversions
- Create audiences
- Delete data
- Connect to Google Ads
- Import data except for offline data
- Create custom dimensions and metrics

**Actions you can NOT take in a sub-property:**
- Create new events
- Add or delete data streams
- Modify or Create events in UI

## IMPORTANT ADMIN SECTION SETTINGS

You can find each of the features in this section by clicking on the gear button in the lower left-hand corner of your side panel.

### ENHANCED MEASUREMENT
GA4 provides some helpful enhanced measurement events—for websites only—that are tracked similarly across many brands. These are:

*(Note: These events include Page views, Scrolls, Outbound clicks, Site search, Video engagement, and File downloads.)*

These are automatically enabled when the configuration associated with the data stream’s measurement ID is placed directly on the site using gtag or Google Tag Manager. Still, you do have the option to turn any or all of them off. I recommend doing this if you don’t plan on utilizing this data or if you plan to create a custom event in its place. Turning them off will reduce the overall size of the JavaScript file being downloaded on your browser. You can click on the gear icon in this section to do this. A view will appear, allowing you to toggle each event on or off.

You can configure additional options for page views and site search. For page views, If you click on advanced settings, you can turn on the ‘page changes based on browser history events’ option, along with page loads, which is helpful if your site is built as a single-page application.

Site search is automatically set up to capture the search term based on the URL’s `q`, `s`, `search`, `query`, or `keyword` parameter. However, if your search term is denoted with another URL query parameter, you can also make that change in the advanced settings.

### DATA SETTINGS

**Google Signals**  
Google Signals is Google’s identity software that enables them to recognize users as they navigate across devices if they are logged into a Google account and if they have enabled ads personalization. It enables some powerful features within GA4, including the following:
- The ability for GA4 to identify users more accurately across devices
- Populating demographics and interest reports
- Collecting a greater quantity of user identification as cookies are phased out, which allows for more accurate conversion modeling and behavioral modeling where there are gaps.

This feature is not automatically enabled, so if you want to utilize its features, you’ll have to go into the ‘Data Collection’ section under ‘Data Settings’ and 1) Turn this setting on, 2) Customize regional settings based on your Legal department’s recommendation, and 3) Acknowledge the user data collection statement.

**Data Retention**  
In the free version of GA4, your data retention setting is automatically set to two months. This means that you can only set your lookback window to two months. But don’t panic! There are 2 major caveats: First, This only applies to Explore reporting. Second, you can change this to 14 months if you go into the Data Retention section of your Data Settings.

Since GA4 relies heavily on Explore reporting to do real analysis in GA4, you may be concerned that you can’t look back past 14 months. Keep in mind that you can still utilize Google Data Studio and BigQuery (which has a free export option for even non-360 users in GA4) to look at a bigger window of historical data.

If you’re a 360 customer, you can adjust your data retention settings similarly, but you have longer lookback windows to choose from, the longest being 50 months.

**Data Filters (Internal Traffic, Developer Devices)**  
There ARE still data filters in GA4 properties outside subproperties, but not at the same level as Universal Analytics views. While you need to use a sub-property to filter your data based on region, subdomain, etc., you can use the data filters in the admin section on properties to filter out the following:

*   **Internal Traffic** – GA4 automatically sets up a parameter for you called `traffic_type` with a value set to `internal` (you can change this value name). Any IP address that is set to have the value of “internal” will automatically be identified with the dimension of “Test data filter name” in reporting (if the ‘Testing’ filter state is chosen, which is the automatic setting) or not at all evaluated or included in reporting (if ‘Active’ is chosen). To make this actually work, you will need to set up a rule identifying the specific IP addresses that you want to include or exclude within your data stream settings (click into your selected data stream > more tagging settings > define internal traffic).
*   **Developer Traffic** – GA4 allows you to exclude any event with the `debug_mode` or `debug_event` parameter set to the value of `1`. This could be helpful if you had some event testing that you wanted to do outside of preview mode. The important thing to remember here is to remove the parameter when you want an event that you’re testing actually to transfer to your reports. Remember that you must enable this feature—it is not turned on by default.

### REPORTING IDENTITY
Your reporting identity is core to your initial GA4 setup and one of the biggest feature changes in this new version. You now have three different options to choose from that offer various different user identification methods:

**Blended** – This is the most comprehensive option that utilizes all of Google’s proprietary technology. This option identifies users in one of four ways (in order):
- *User ID:* This is the first and most accurate way that Google will try to identify a user. If your users can log in to your site or app, and you have assigned a `user_id` to them in your GA4 tags, this is how they will be identified.
- *Google Signals:* If enabled, this will identify users based on the Google Signals criteria above.
- *Device ID:* This is the legacy cookie-based option to identify users based on the device. On a browser, this is the Client ID based on the `_ga` cookie, and this value is from the app-instance ID on a mobile app.
- *Modeling:* If consent mode is in place that allows users to opt out of analytics cookies, it will cause gaps in your data. Google’s behavioral modeling can fill in these gaps by estimating the behavior of these users based on similar users who have accepted analytics cookies.

**Observed** – This option identifies users by User-ID, Google Signals, and Device ID but does not use Modeling.

**Device-based** – This ONLY identifies users by Device ID and does not utilize User-ID, Google Signals or Modeling.

### ATTRIBUTION SETTINGS
Attribution settings allow you to choose how you want conversion credit assigned to your channel groupings, source, medium, campaign, etc. [Chapter 11](https://www.gofurther.com/blog/ga4-guide-chapter-11-optimizing-acquisition-channels) covers this in more detail.

**Attribution models:**
- *Data-driven* – Google’s machine learning capabilities evaluate which paths lead to conversions.
- *Last click* – Ignores direct traffic and attributes 100% of the conversion value to the last tactic that the customer clicked (or engaged view through for YouTube) before converting.
- *First click* – Gives all credit for the conversion to the first channel a customer clicked (or engaged view through for YouTube) before converting.
- *Linear* – Distributes the credit for the conversion equally across all the channels a customer clicked (or engaged view through for YouTube) before converting.
- *Position-based* – Attributes 40% credit to the first and last interaction, and the remaining 20% credit is distributed evenly to the middle interactions.
- *Time decay* – Gives more credit to the touchpoints that happened closer in time to the conversion. Credit is distributed using a seven-day half-life.
- *Ads-preferred last click* – Attributes 100% of the conversion value to the last Google Ads channel that the customer clicked through before converting.

***Tip: The ‘Model Comparison’ report in the Advertising report suite is a beneficial tool to decide which model you want to use.***

**Lookback windows:**
You can also specify your lookback windows in this section. For example, if you have your attribution acquisition lookback window set to seven days, if somebody came into your site initially through a Google Ad and the user converted after four days, Google Ads would get credit for that conversion. If that user came back on the ninth day through Organic Search and then converted, Organic Search would get credit for that conversion.

## CONFIGURE SECTION SETTINGS

You can find each of the features in this section by clicking on the ‘Configure’ button in the top section of your side panel.

### CUSTOM DEFINITIONS (SPECIFICALLY, CUSTOM DIMENSIONS)
In the GA4 data model, every event has a simple structure. We start with the event, then use event parameters (describing the event) and user properties (describing the user). Custom dimensions are just parameters that you send with your custom events that you can see and use in your GA4 reporting.

**How to set up Custom Definitions**  
To set these up, go into the ‘Custom Definitions’ tab of the ‘Configure’ section. Start by putting the name of your dimension, then choose scoping: either ‘event’ or ‘user’. You’ll then add a description and the parameter name that will coincide with your parameter name when you send the event.

**Key differences between UA and GA4 CDs**
- *Fewer scoping options* – In GA4, we don’t yet have session- or product-scoped custom dimensions (though 'item'-scoped parameters are built-in for e-commerce).
- *No index number* – Custom dimensions are no longer associated with an index number; they are identified by name.
- *Character limit* – Event-scoped values are limited to 100 characters; user-scoped values are limited to 36 characters.
- *Creation limit* – GA4 (free) allows 50 event-scoped and 25 user-scoped dimensions. GA360 allows 125 event-scoped and 100 user-scoped dimensions.

### AUDIENCES
Creating audiences in GA4 is a way of grouping users, primarily for Google Ads targeting. It allows marketers to target people based on actions taken on their website or app.

**How to set up Audiences**
- *Templates* – Includes ‘Predictive’ templates utilizing machine learning (requires sufficient data).
- *Condition scoping* – Specify if events had to happen in the same session.
- *Condition sequencing* – Target users who performed specific events in a certain order.
- *Membership duration* – Automatically set at 30 days (customizable).
- *Audience trigger* – Creates an event each time a new member joins the audience.

**Key differences between UA and GA4 audiences**  
You can save up to 100 audiences in the standard version and up to 400 in 360. Once created, you can only change the name, though you can archive old ones.

### CONVERSIONS
In GA4, ‘Goals’ are replaced by conversions. All conversions are based on events.

**How to set up Conversions**  
Go to the ‘Configure’ tab, then the ‘Events’ page, and toggle your desired event on or off. If you need a conversion based on specific parameters (e.g., a specific form type), you must create a new unique event for that specific action first.

**Key differences between UA and GA4 Conversions**  
In UA, goals were often session-based (did it happen once?). In GA4, conversions are event-based (tracked every time they happen). GA4 also requires making a new event if you need specific context around a conversion, rather than configuring rules within the goal setup itself.

## CONCLUSION
Although this is not an exhaustive list of all GA4 features, keeping these settings in mind will help as you start your migration or implementation. If you want more in-depth information, you can also check out our [Youtube channel](https://www.youtube.com/@Further_Worldwide)!

## Read More Insights From Our Team

*   [Target Micro-Segments in Google Ads with Compass](/blog/target-micro-segments-in-google-ads-with-compass) — **Jim Koenig** (Google Partner, Data Cloud, AI)
*   [Google Next 2025: A Deep Dive into AI, Data, and the Future of Cloud](/blog/google-next-2025-a-deep-dive-into-ai-data-and-the-future-of-cloud) — **Jason Tabeling** (Google Partner, Solutions, AI)
*   [The Future of Data Warehousing With Google Cloud Platform](/blog/the-future-of-data-warehousing-with-google-cloud-platform) — **Jim Koenig** (Google Partner, Data Solutions)

[View All](/our-thinking/blog)

## Take your company further. Unlock the power of data-driven decisions.

[Go Further Today](/contact)