}
This website uses cookies so that we can provide you with the best user experience and deliver advertising messages and offers. To read more about the cookies we use and to change your settings, please see our cookie policy. Cookie Policy
Scam alert. Mintense never offers jobs or paid tasks on WhatsApp or Telegram and never asks for cryptocurrency. Read more

GA4 for international websites selling across Europe

GA4, or Google Analytics 4, is Google's free tool for measuring what visitors do on your website. For a UK B2B firm with several European sites, the most practical setup is one property and one web stream shared by every domain, with cross-domain measurement switched on, a short list of key events for enquiries and Consent Mode v2 set up for UK and EU visitors.

This guide covers how to structure properties for .co.uk, .de and .fr domains or language folders, which events and dimensions to track, how pounds and euros are handled and how the UK analytics cookie exemption introduced in 2026 compares with EU rules. It ends with the mistakes we see most often and a monthly checklist.

What is GA4 and what does it measure on a B2B website?

Google Analytics 4 records every interaction on your website as an event. A page view is an event, and so are a scroll, a click on a phone number or a submitted quote form. Each event can carry parameters that describe it, such as the form name or the language of the page.

For a B2B firm this model fits well, because most of what matters happens in a few actions spread over several visits. A buyer in Lyon may read a product page in March and send a quote request in May, after two more visits from a search.

GA4 measures behaviour on your site. It does not know whether the enquiry turned into an order. That information lives in your CRM, and the most useful setups connect the two through a lead ID or a value you assign to each type of enquiry.

Should you use one GA4 property or several for multiple domains?

For most UK SMEs the answer is one property with one web stream, even when the business runs separate country domains such as a .co.uk, a .de and a .fr. All domains share the same measurement ID, the code that starts with G-, and you separate the markets in reports by hostname or by country.

A single property gives you one view of the buyer journey. When a German visitor arrives on the .de site and later requests a quote on the .co.uk site, GA4 can keep it as one user and one session, provided cross-domain measurement is configured.

Separate properties make sense in a few cases. One is when each country is run by an independent team with its own budget and its own access rights. Another is when the domains belong to different legal entities that must not share data.

Language folders on one domain, such as /de/ and /fr/, are the simplest case of all. One property and one stream cover everything, and no cross-domain setup is needed. The choice has SEO consequences too, which our guide to structuring URLs for international SEO explains.

How do you set up GA4 cross domain tracking?

Cross-domain measurement passes the visitor's identifier from one domain to the next through a URL parameter called _gl. Without it, a move from your .co.uk site to your .de site starts a new session, and the second domain records your own website as the referral source.

Google's cross-domain measurement guide sets two conditions. Every page on every domain must use the same Google tag ID from the same web stream, and you need the Editor role or above on the account.

  • Open Admin, then Data streams, and select your web stream.
  • Click Configure tag settings, then Configure your domains.
  • Add a condition for each domain, for example contains example.de, up to a maximum of 100 conditions.
  • Save, then click a link from one domain to another and check that the destination URL carries the _gl parameter.

Redirects are the usual reason the test fails. If your server sends the visitor from example.de to www.example.de and drops the query string, the _gl parameter disappears with it. Test your language switcher too.

Subdomains such as shop.example.co.uk do not always need cross-domain links, but Google recommends including them in the configuration to avoid self-referrals. Add external payment or booking domains to the unwanted referrals list, so a return from the payment page does not appear as a new source.

Which key events should a B2B site track?

Key events are the events you mark as important for the business, the GA4 name for what used to be conversions. A standard property can have up to 30 of them, and Analytics 360 raises the limit to 50. For a B2B site that sells across Europe, six to ten are usually enough.

  • generate_lead, sent when a contact or quote form is submitted successfully, with a parameter for the form type.
  • A call event for clicks on tel: links, split by the number clicked, since each country office may have its own number.
  • file_download for price lists, data sheets and catalogues, with the file name and language as parameters.
  • An email click event for mailto: links, plus a booking event if you use a meeting scheduler.

Fire the lead event on the confirmation, after validation, and never on the click of the submit button. Event names can be up to 40 characters long and each event can carry up to 25 parameters. Keep the names in English across all markets. A form called demande_devis on the French site and quote_request on the UK site would split the same action into two rows in every report.

Assigning a value helps when you compare countries. If a quote request is worth more to you than a brochure download, give each key event a notional value in pounds and use it consistently.

How do you read GA4 reports by country and language?

GA4 offers two dimensions that are easy to confuse. Country is derived from the visitor's IP address at the time of the visit. Language comes from the browser settings. A Belgian buyer can appear as Belgium with French or Dutch as the language, depending on how the computer is set up.

Neither dimension tells you which version of your site the visitor used. For that you need the hostname for country domains or the page path for language folders. An exploration with country as rows and hostname as columns shows whether Germans land on your German pages.

That comparison often reveals work for your SEO team. Large numbers of German visitors on English pages usually mean the German version is missing or poorly signalled to Google. Our hreflang guide explains how to tell search engines which version to show in each country.

Which custom dimensions are worth creating?

A custom dimension turns an event parameter into something you can use in reports. A standard property allows 50 event-scoped and 25 user-scoped custom dimensions, 10 item-scoped dimensions and 50 custom metrics. Data is collected only from the day you create the dimension, so register them early.

For an international B2B site the most useful ones describe the page and the lead. A site_language parameter, read from the lang attribute of the page, gives you the language of the content regardless of the browser. A site_market parameter, such as uk or de, helps when the same language serves several countries.

Avoid high-cardinality values. Google treats a dimension with more than 500 possible values as high cardinality, and reports may then group the rarer values under (other). Never send personal data such as email addresses as parameters.

How do you manage GA4 across European markets, languages and currencies?

Start with the reporting currency. A property shows all monetary values in one currency, set in the property details, and the default is US dollars. A UK firm will normally choose pounds. Changing it later also converts historical data.

When your euro sites send a value with a lead or an order, send the currency parameter too. Google says that if you set a value, the currency is required for revenue metrics to be computed accurately. GA4 converts the euro amount into pounds using the previous day's exchange rate, while the BigQuery export keeps the original local currency.

Languages are the second layer. Keep event and parameter names identical across all versions of the site and translate only what the visitor sees. Accounts and access follow the organisation. Your company should own the GA4 account, and agencies or country managers should be added as users with the lowest role that lets them work.

Brexit split the regulation. UK visitors fall under PECR and UK GDPR, while visitors in EU countries fall under the ePrivacy rules of their member state and the EU GDPR. One cookie banner can serve both groups if it meets the stricter standard, which in practice means prior consent for analytics in most EU countries.

Consent Mode is the mechanism that passes the visitor's cookie choices to Google tags. Version 2 uses four signals. analytics_storage controls analytics cookies, ad_storage controls advertising cookies, ad_user_data covers sending user data to Google for advertising and ad_personalization covers personalised advertising.

There are two implementations. In basic mode the tags stay blocked until the visitor answers the banner, and nothing reaches Google if they refuse. In advanced mode the tags load with consent set to denied by default and send cookieless pings until the visitor accepts, which lets Google build a more detailed model.

Behavioural modelling fills the gaps left by visitors who refuse analytics cookies. According to Google's modelling documentation, a property becomes eligible only when it collects at least 1,000 events a day with analytics_storage denied for at least 7 days, and at least 1,000 daily users with analytics_storage granted on at least 7 of the previous 28 days.

Many UK B2B sites never reach those thresholds, especially once traffic is split across several European markets. You then see only consented data. Modelled data appears only when the Blended reporting identity is selected in Admin.

Google's EU user consent policy covers UK visitors as well as those in the EEA and Switzerland. If you use Google Ads remarketing or import GA4 conversions into Google Ads, the advertising signals must reflect real consent from your visitors.

Not always, since 5 February 2026. The Data (Use and Access) Act 2025 amended regulation 6 of PECR and added a new Schedule A1, which came into force on that date through the Commencement No. 6 Regulations. One of the new exceptions covers storage and access for statistical purposes.

The text of Schedule 12 of the Act sets the conditions. The sole purpose must be to collect statistical information about how your service or website is used with a view to improving it. The information may be shared only with someone who helps you make those improvements. Visitors must receive clear and comprehensive information about the purpose and have a simple, free means of objecting.

The ICO's guidance on the exceptions narrows it further. The ICO says the exception concerns how a service is used and does not extend to identifying the people who use it. A third-party analytics provider must act as your processor and must not link the data with other information it holds. The exception does not cover any purpose related to online advertising.

For GA4 this has practical consequences. A property linked to Google Ads, with Google Signals on or audiences built for remarketing, serves advertising purposes and still needs consent. A stripped-down configuration used only to improve the site may qualify, but you must still offer an easy way to object, and the ICO says you cannot rely on browser settings alone. Take legal advice before you remove the consent step for analytics. Firms with EU traffic often keep one consent banner for all visitors, since that traffic needs consent anyway.

What rules apply to visitors from EU countries?

The UK exemption does not travel. Visitors in Germany or France fall under the national law that implements the ePrivacy Directive, and in most member states analytics cookies need prior consent unless they meet the conditions set by the local regulator.

Some regulators accept consent-free audience measurement under strict rules. The CNIL in France, for example, sets limits on cookie lifetime and on how long the data is kept. A standard GA4 setup does not usually meet them, so for EU visitors you should plan on asking for consent.

The banner must speak the visitor's language. A French buyer who lands on your .fr site and sees an English consent text is unlikely to give informed consent. Translate the banner and the privacy notice for every market, and keep the button to refuse as visible as the button to accept.

EU GDPR may apply to you directly when you target customers in the Union, even without an office there. Our article on the EU AI Act for UK businesses shows how EU rules reach UK firms in a related area.

Is it lawful to send GA4 data to the United States?

For UK data, the UK-US data bridge has applied since 12 October 2023. The Data Protection (Adequacy) (United States of America) Regulations 2023 allow transfers to US organisations listed on the Data Privacy Framework List as participating in the UK Extension, without other safeguards such as standard contractual clauses.

For EU data, the European Commission adopted its adequacy decision for the EU-US Data Privacy Framework on 10 July 2023. On 3 September 2025 the EU General Court dismissed a challenge to that decision, and an appeal is pending before the Court of Justice.

Check the official list for every US provider you use, since a certification can lapse. Google also states that Google Analytics does not log or store individual IP addresses from UK users, nor from users in the EU and Switzerland, and that these addresses are used briefly for coarse location before being discarded. Your privacy notice should name GA4 and state the safeguard you rely on for the transfer.

The Google Ads link brings cost and click data into GA4 and lets you import key events into Google Ads for bidding. You need the Editor role in GA4 and administrative access in Google Ads. A property can have up to 400 links, and a manager account counts as one.

Once linked, create conversions in Google Ads from your GA4 key events, and choose carefully which ones count as primary for bidding. Our PPC management service sets up this link for campaigns across several European countries, and the guide to Performance Max in several countries shows how conversion choices shape results.

Search Console has stricter limits. A web stream can be linked to only one Search Console property, and a GA4 property can have only one stream linked. To create the link you need the Editor role in GA4 and verified ownership in Search Console. The data arrives with a 48-hour delay and covers at most the last 16 months.

With several country domains this means you pick one Search Console property for GA4 and use Search Console itself for the others. The two new reports, organic search queries and organic search traffic, sit in an unpublished collection. Publish the collection from the Library so the reports appear in the menu.

How long does GA4 keep data and when do you need BigQuery?

A standard property keeps user-level and event-level data for 2 or 14 months. Analytics 360 can keep event data for up to 50 months. The setting affects explorations and funnel reports only, while the standard aggregated reports remain available beyond it.

Set retention to 14 months as soon as you create the property, unless your privacy policy says otherwise. With two months you cannot compare this autumn with last autumn in an exploration.

The BigQuery export copies raw events into your own Google Cloud project. Standard properties have a daily export limit of one million events. The streaming export has a cost of 0.05 US dollars per gigabyte, which Google estimates at roughly 600,000 events. The export does not bring in history from before the link, so connect it early. You need BigQuery when you want to keep raw data longer than 14 months or join web data with CRM records.

What are the most common GA4 mistakes on international sites?

Most problems we find come from setups made in a hurry, then copied from one market to the next. Our SEO audit includes a check of the GA4 configuration for this reason.

  • Different measurement IDs on the .co.uk and the .de site, so the same buyer appears twice and your own domains show up as referrals.
  • A lead event fired on the click of the submit button, which counts failed attempts and spam as enquiries.
  • Event names translated per market, which splits one action into several rows in every report.
  • Retention left at two months and the reporting currency left in US dollars.
  • Internal traffic from your own offices left unfiltered, which inflates small markets.
  • A cookie banner that loads GA4 before consent on EU pages, or a banner in English on a German site.

Another frequent gap is AI traffic. Visits from AI assistants such as ChatGPT or Gemini may arrive as referrals that nobody reviews.

What should you check in GA4 every month?

A monthly routine of half an hour catches most problems before they distort a quarter of data.

  • Compare the leads in GA4 with the enquiries received by sales for each country, and investigate any gap above a few units.
  • Look at the referral report for your own domains, payment providers or unknown spam sources, and fix the configuration where needed.
  • Review the landing pages by country and language, looking for markets that land on the wrong language version.
  • Check that the Google Ads and Search Console links are active and that the consent banner still works in every language.

If you want a second pair of eyes on your measurement before you open a new market, our international SEO agency team reviews GA4 setups as part of wider work on multilingual sites, with specialists who read each market in its own language.

Ask us to review your GA4 setup

Frequently asked questions

Is GA4 free for a UK business?

Yes. The standard version of Google Analytics 4 costs nothing, whatever the number of domains or countries you measure. The paid version, Analytics 360, adds higher limits and longer data retention, and suits large organisations. Most UK SMEs never need it. Your real costs are the time spent on setup and maintenance, plus any paid consent platform or BigQuery usage beyond the free tier.

Can one GA4 property track a .co.uk, a .de and a .fr site?

Yes, and for most firms it is the best option. Install the same Google tag, from the same web stream, on every domain and configure cross-domain measurement in the stream settings. GA4 then treats a visitor who moves between your domains as one user. You can still separate the markets in reports by filtering on hostname or on a custom dimension for the site language. Separate properties make sense only when each market needs independent access or data must stay apart.

Has the Data (Use and Access) Act removed the cookie banner for GA4?

Only in some cases and only for UK visitors. Since 5 February 2026 PECR allows storage and access without consent when the sole purpose is collecting statistics to improve your website, the data is shared only with providers who help with that, and visitors get clear information and an easy way to object. A GA4 setup linked to Google Ads or used for remarketing serves advertising and still needs consent. EU visitors follow their own national rules, which usually require consent.

Why do GA4 numbers differ from my CRM?

Several reasons add up. Visitors who refuse analytics cookies are missing from GA4 unless modelling applies, and many B2B sites are too small to qualify. Some enquiries arrive by phone or email without a tracked event. Lead events fired on a button click also count failed submissions and spam. Compare both sources market by market every month, and treat GA4 as the guide to trends and channels while the CRM remains the record of real enquiries and revenue.

Should GA4 report in pounds or euros?

Choose the currency your management reads, which for a UK company is usually pounds sterling. The reporting currency is a property setting and the default is US dollars, so change it on day one. Your euro sites can keep sending values in euros, as long as each event includes the currency parameter. GA4 converts those amounts using the previous day's exchange rate, and the BigQuery export keeps the original currency for anyone who needs it.

How long does it take to set up GA4 properly on an international site?

For a site with three or four language versions, a careful setup usually takes a few working days spread over two or three weeks. The work covers the tag on every domain, cross-domain links, key events, custom dimensions, consent configuration and links to Google Ads and Search Console. Testing takes longer than configuration, because every form and phone link must be checked in each market, along with the language switcher.

Our services

More from our blog