How to Set Up Google Analytics for Multiple Publishing Sites

Why Multi-Site Analytics Matters for Publishers

If you're running more than one publishing site—whether it's author platforms, niche content hubs, or a portfolio of digital properties—you already know the pain: logging into five different Google Analytics accounts, hunting for the same metric across dashboards, and never quite knowing which site is performing best.

Most publishers treat each site's analytics in isolation. That's a missed opportunity. When you can see how traffic flows between your sites, which audiences overlap, and how your portfolio performs as a system, you make better decisions about content, product launches, and affiliate strategy.

This post walks you through setting up Google Analytics 4 (GA4) across multiple sites, connecting them to a unified reporting layer, and building dashboards that actually answer your business questions.

Step 1: Audit Your Current Analytics Setup

Before you add anything new, document what you have.

• List every site you operate (including subdomains, staging environments, and any properties you plan to launch soon).
• Check which analytics tool is currently installed on each. Most publishers mix Universal Analytics (UA), GA4, and sometimes nothing at all.
• Note the Google Account owner for each property. Consolidating under a single Google Account makes administration much easier.
• Record any custom events or goals you're tracking. You'll want to replicate these across your portfolio.

If you're using tools like Archieboy Holdings' portfolio management approach, this audit also helps you understand which sites feed traffic to others and which operate independently.

Step 2: Create or Consolidate Your Google Account Structure

GA4 properties live inside Google Analytics accounts, which live inside Google Accounts. The hierarchy matters.

Recommended structure for multi-site publishers:

• One Google Account (your main business email) that owns all GA4 properties.
• One Google Analytics account (within that Google Account) for your entire publishing portfolio.
• One GA4 property per website, plus one master property that aggregates data from all sites.

If you're already scattered across multiple Google Accounts, now's the time to consolidate. Add team members to your main Google Account and give them the appropriate roles (Editor, Analyst, Viewer) at the property level.

Setting Up Your Master Property

A master property is a GA4 property that collects data from all your sites using a single tracking ID. It's not a replacement for individual site tracking—you keep those intact—but it gives you a bird's-eye view of your entire portfolio.

To create one:

1. Go to Admin in your GA4 account.
2. Click Create Property and name it something clear, like "[Your Company] - Master Portfolio."
3. Use the same Google Analytics account you're consolidating into.
4. Copy the measurement ID (looks like G-XXXXXXXXXX).
5. Install this tracking code on every site in your portfolio, in addition to each site's individual GA4 tag.

Yes, you'll have two GA4 tags firing on each page. That's intentional: one feeds the individual site property (for detailed, site-specific analysis), and one feeds the master property (for portfolio-level insights).

Step 3: Install GA4 Tags Correctly

The cleanest way to manage multiple GA4 tags is through Google Tag Manager (GTM), not by hardcoding snippets.

Basic GTM setup for multi-site tracking:

1. Create one GTM container per website (don't try to share a container across sites—it gets messy).
2. Add two GA4 tags in each container:
   • Tag 1: Fire the site-specific GA4 measurement ID.
   • Tag 2: Fire the master portfolio GA4 measurement ID.
3. Set both tags to fire on all pages (trigger: "All Pages").
4. Test in GTM's Preview mode before publishing.

If you don't use GTM yet, add it. It saves you from touching code every time you need to adjust tracking, and it's free.

Custom Events Across Sites

Beyond page views, you probably care about conversions: email signups, affiliate clicks, product purchases, or content downloads.

Define your key events once, then implement them consistently across all sites:

• signup — email list subscription.
• affiliate_click — user clicked an affiliate link.
• purchase — user bought something.
• content_download — user downloaded a lead magnet, template, or resource.

In GTM, create a tag for each event. Use consistent naming across all sites so your master property can aggregate meaningful data.

Step 4: Set Up Cross-Domain Tracking (If Applicable)

If your sites share a common domain (e.g., site1.yourcompany.com, site2.yourcompany.com), GA4 will automatically link sessions across them. If they're separate domains, you need to tell GA4 they're related.

To enable cross-domain tracking in GA4:

1. Go to Admin → Data Streams → select your data stream.
2. Scroll to More Tagging Settings → Configure Your Domains.
3. List all domains in your portfolio (e.g., site1.com, site2.com, site3.com).
4. GA4 will automatically pass a _gl parameter in links between these domains to maintain session continuity.

This matters because it lets you see the full user journey: if someone lands on site1.com, reads an article, clicks a link to site2.com, and signs up there, you'll see that as one continuous session, not two separate visits.

Step 5: Build Dashboards That Answer Real Questions

GA4's default reports are generic. Custom dashboards should answer the questions you actually care about.

Example dashboard for a multi-site publisher:

• Portfolio Overview — Total sessions, users, and conversions across all sites (from your master property).
• Site Performance Comparison — Sessions, bounce rate, and conversion rate broken down by site.
• Traffic Flow — Which sites send traffic to which other sites (using the cross-domain data).
• Conversion Funnel — Email signups → affiliate clicks → purchases, across the entire portfolio.
• Top Content — Most-visited pages across all sites, ranked by engagement time.

To build a custom dashboard:

1. In GA4, click Dashboards (left sidebar).
2. Click Create New Dashboard.
3. Add cards by clicking Add Card and choosing your metric (Sessions, Users, Conversion Rate, etc.).
4. Use filters to segment by site, traffic source, or user segment.
5. Save and share with your team.

Step 6: Set Up Alerts for Anomalies

You don't need to stare at dashboards all day. GA4 alerts notify you when something unusual happens.

Useful alerts for publishers:

• Traffic to any site drops by more than 20% in a day (catches broken tracking or a real traffic problem).
• Conversion rate spikes by more than 30% (might be a data error or a genuinely successful campaign).
• A specific page gets 10x its normal traffic (could be a viral moment or bot traffic).

To create an alert, go to Admin → Alerts → Create Alert. Set your threshold and choose how to be notified (email is usually fine).

Step 7: Connect GA4 to Your Reporting Tools

GA4's interface is useful, but if you're building dashboards for stakeholders or running a data-driven operation, you'll want to pull data into a tool like Google Sheets, Data Studio, or a BI platform.

GA4 to Google Sheets: Use the free Google Analytics connector add-on. It's limited to 100,000 rows per query, but fine for most publishers.

GA4 to Data Studio: GA4 has a native connector. You can build interactive dashboards your team can filter and explore without touching the GA4 interface.

GA4 to BigQuery: If you're serious about data, enable BigQuery linking in GA4. It exports raw event data (not aggregated) to BigQuery, where you can run SQL queries and combine GA4 with other data sources.

Common Mistakes to Avoid

Mixing UA and GA4 without a plan. If you still have Universal Analytics properties, migrate them to GA4 before the end of 2024. UA is deprecated. Pick a cutover date and stick to it.

Not filtering out internal traffic. Your own team's visits will skew your data. In GA4 Admin, create a filter that excludes traffic from your office IP address (or your team's home IPs if remote).

Tracking PII. Don't send names, email addresses, or user IDs to GA4 in event parameters. Google will flag this, and it violates privacy regulations. Use user IDs only if you've set up proper consent and data governance.

Ignoring data latency. GA4 data is not real-time. Expect a 24–48 hour delay for final numbers. Don't panic if your dashboard looks incomplete—it will catch up.

Putting It Together: A Checklist

• ☐ Audit all existing analytics installations across your portfolio.
• ☐ Consolidate under one Google Account and GA4 account.
• ☐ Create a master GA4 property for portfolio-level tracking.
• ☐ Set up Google Tag Manager on each site.
• ☐ Install both individual and master GA4 tags via GTM.
• ☐ Define and implement consistent custom events across all sites.
• ☐ Configure cross-domain tracking if applicable.
• ☐ Build 3–5 custom dashboards that answer your key questions.
• ☐ Set up anomaly alerts for your most important metrics.
• ☐ Connect GA4 to your reporting tools (Sheets, Data Studio, or BigQuery).
• ☐ Document your setup for your team.

Next Steps

Once your analytics infrastructure is solid, you can start asking harder questions: Which traffic sources drive the most valuable users? How does content on one site influence conversions on another? Which audience segments are most likely to engage with your affiliate offers?

That's where multi-site analytics really pays off. You're no longer flying blind across your portfolio—you can see patterns, optimize strategically, and grow with confidence.

If you're managing a portfolio of publishing properties, tools like Archieboy Holdings can help you centralize not just analytics but your entire content and affiliate operation. The cleaner your data infrastructure, the easier it is to scale.

Start with this setup, give yourself a week to let data accumulate, then dive into your dashboards. You'll be surprised what you find.