[MUSIC PLAYING]
KRISTA SEIDEN: Hey, everyone.
I'm Krista Seiden, and I'm here today
with Breen Baker, who is a product
manager on Google Analytics.
Breen, thank you so much for being with us here today.
BREEN BAKER: Thanks for having me, Krista.
KRISTA SEIDEN: Of course.
Today, Breen is going to tell us all about subproperties
in Google Analytics 4.
Subproperties are really cool because they
allow you to see a subset of your data
rather than the entire source property
so that you can do things like look for individual data sets
by geo or location or for different governance needs.
So with that, I'm going to hand it over to Breen,
and he's going to walk us through subproperties
in Google Analytics 4.
BREEN BAKER: Thanks, Krista.
So we'd like to start with why we designed subproperties
to begin with, and that's to govern your data.
So subproperties were designed to filter a subset of your data
and to give it to a subset of users.
Most commonly, we see regional subsets of brands.
You're also going to want to consider very heavily if you
have an app or apps or not.
Apps have a limitation where an app can only be
linked with one GA4 property.
And so if you do need a subset of app data
to go to any other team, you're going
to need to use a subproperty.
And then lastly, one of the key points to leave you with
is that subproperties are just like other properties.
They have the same limits, the same quota, the same access
controls.
They're able to do integrations.
And they behave like ordinary properties.
And you should expect them to behave
like ordinary properties.
Second, I wanted to go over the difference between governance
and organization.
It is true that subproperties were
created to replace some of the features
from Universal Analytics Views.
However, they are not here to replace
all of the features of Views.
You'll see some of the settings that
used to reside in a Universal Analytics View
now just reside at the property level.
You're also going to find that there's a cost associated
with subproperties.
So you're not going to want to use them 1 to 1
in every situation.
So when you are considering, how do I organize and govern
my data, you're going to want to look at a host of tools instead
of just one.
You will want to look at subproperties, again,
when a subset of people need to look at a subset of data,
and really only them or only they can look at that data.
You're also going to want to consider
user management in general and most especially, report
collections.
So groups of reports that can be created for a team
can be used to organize data, where
one team could see the data from another team,
you don't have that governance need, but ultimately,
you do want to organize so that that team can focus.
We also wanted to cover that there is a cost.
And I said this before with subproperties.
The cost is one half of an event.
So if you have a mutually exclusive subset
of data broken into regions, it'll
be one half the cost of the original ordinary property
with respect to events.
And it's for that reason is one of the key reasons we're
advising you not to create a subproperty for every View
from Universal Analytics.
We'll finish with an example in a demo.
So the example shows our most common setup.
So all of the data for a given brand or business unit
has been collected into a single ordinary property.
And that has been broken up into that mutually exclusive subset
of geolocated data, in this case, regions.
So every event from the main ordinary property
is being processed in one of these regional properties,
and there's no overlap.
So they're mutually exclusive.
And with that, you'll get one half the charge
for all of the events processed in the ordinary property.
And with this comes the ability for only these teams, only
these regions, to see this data and for them
to have separate integrations and separate configurations.
And with that, we will go to a demo.
So here, we find ourselves in the Admin section of the Google
Merch GA4 demo property.
The first thing you'll probably notice
is that three items down, you'll see a newish menu item called
Subproperty Management.
I would also be able to create a subproperty if I came up
to the top and clicked the blue button for Create
Property, where I can see that I can create all three property
types.
So I'm going to go ahead and select
Subproperty, which brings me to the subproperty creation page.
I'm going to need to select an ordinary property to build
from.
For that, I'll select the Google Merch GA4
property I was just in.
I'm going to need to test this-- or sorry, name this property.
I'll name it test just for now.
Acknowledge that there's an additional cost,
and click Next.
Next, I'm brought to the Data Filter section, where
I can create multiple different condition
groups to filter out events based on browser, region, page,
et cetera.
Let's say I want to create one of those very classic regional
breakdowns.
So I can select Country.
I can add a condition.
I have many of my standard condition options here.
Let's say I want it to match specifically the United States.
Go ahead and click Apply.
And now, if I undid my filters, I
would create a property that only showed events
coming from the United States.
If I wanted to actually finish and create this property,
I'd click Next and fill out some of the business information
that helps us understand who you are
and why specifically you've created this property.
I'm not going to click the Create button.
But I could if I wanted to.
And that would create a subproperty.
And from that point going forward,
all events processed in the ordinary property
would be processed in the subproperty
if they came from the United States.
KRISTA SEIDEN: Thanks so much, Breen,
for showing us how simple and easy to use subproperties
in Google Analytics 4 are.
There are so many awesome use cases to use for subproperties,
and I hope that you can get started with these today.