Importing geographical data enables the mapping of geographical IDs to custom regions, allowing you to report on and analyze your Analytics data in ways that are better aligned with your business' organization.
Note: The previous link opens to the last Analytics property you accessed. You must be signed in to a Google Account to open the property. You can change the property using the property selector. You must be an Editor or above at the property level to collect granular location and device data.
In Google Analytics 4, IP addresses are used at collection time to determine location information (country, city, latitude and longitude of city) and then discarded before data is logged in any data center or server.
These URLs can stem not only from Google Ads accounts, but from any other source such as social networks, blogs, or other websites. When Analytics doesn't receive the necessary parameters to identify where traffic from manually tagged URLs comes from, (not set) appears.
The page_location parameter must be 1,000 characters or fewer. If you override the page_location parameter, make sure that the URL path is valid. If you assign an invalid URL path, the Page location dimension will be empty. You can use the Campaign URL Builder to check whether a URL path is valid.
Google Analytics 4 does not log or store individual IP addresses. Analytics does provide coarse geo-location data by deriving the following metadata from IP addresses: City (and the derived latitude, and longitude of the city), Continent, Country, Region, Subcontinent (and ID-based counterparts).
You need a Google tag ID to set up a Google Analytics 4 property for your website using Google Tag Manager and many content management systems (CMSes). A Google tag is a piece of code that you place on your website.
Discover how to set up Google Analytics for your website or app by creating a Google Analytics 4 property, adding a data stream, and adding your Google Analytics code.
Google Analytics stores data from your website or app in two types of tables optimized for either performance or flexibility. One group of tables aggregates your data to provide fast, unsampled results to the most common requests.
