To add a new website to Google Analytics, create a GA4 property, add a web data stream with the site's full URL, install the Measurement ID tag on every page, and confirm visits in the Realtime report. For a small B2B site this is a short task. The harder part is deciding which questions the data should answer, such as which pricing and demo page visits come from target accounts.

Decide Which Site and Which Question First
Small B2B teams often run a marketing site, a product subdomain, and a pricing or docs site. Before you touch settings, decide whether the new site belongs in an existing property or its own. A separate property fits a site with a different audience or owner. A shared property fits when you want one funnel view across domains.
Write down the one question the site has to answer. For example: which landing pages bring in demo requests from companies with 11 to 200 employees? A clear question tells you which events to track and which reports to build, so you do not end up with a dashboard full of page views nobody uses.
Related: Google Analytics Setup for Small B2B Sales Teams
Step-by-Step: Add the Site as a GA4 Property
- Sign in to Google Analytics and open the Admin area.
- Create a property under the account you want, then enter the property name, reporting time zone, and currency.
- Add business details, including the industry category and company size that match how you sell.
- Create a web data stream and enter the full URL, including https.
- Copy the Measurement ID, which starts with G-.
- Install the tag on every page through your site template, a tag manager, or your CMS plugin.
- Check the Realtime report while you load the site in a separate browser to confirm the visit appears.
Install the Tag Without Breaking Tracking
Place the tag in the header template so it loads on every page, including pricing, demo, and contact pages. Avoid pasting it in several places. Duplicate tags inflate session counts and make pipeline reports unreliable.
If your visitors include people in the EU or UK, make sure your consent banner controls when analytics tags fire. Our guide on GDPR and CCPA rules for visitor identification covers the same consent logic for identification tools.
Related: Google Analytics Setup for B2B Teams: Step-by-Step
Set Up Key Events That Map to Pipeline
Default page views say little about buying intent. Mark the actions that signal a real evaluation as key events, so they show up in your conversion reports.
- Demo or meeting requests submitted from your booking page or form.
- Pricing page views, which often show the strongest buying signal in B2B.
- Contact form submissions from sales-qualified pages.
- Trial or signup starts if your product offers them.
Metrics to Review in the First 30 Days
In the first month, focus on a short list. Look at traffic by channel to see which sources reach your decision-makers. Check landing page performance on pricing and demo pages, not just the homepage. Compare conversion rate from each form, and watch engaged sessions to separate real visits from bounces.
Set a baseline now, so you can judge changes later. Our article on visitor ID metrics that measure pipeline explains how to move from traffic counts to pipeline numbers.
Where Google Analytics Stops and Visitor Identification Starts
Google Analytics shows how many sessions reached your pricing page and which channel sent them. It does not tell you which company or person was on the other end. Happierleads is a B2B website visitor identification platform that de-anonymizes anonymous website traffic and reveals the exact person behind each visit, so your team can act on a pricing page view while the interest is fresh.
Identified visits can then feed AI lead scoring, intent data, email outreach automation, and CRM integrations. For teams running HubSpot or Salesforce, the setup guide for HubSpot and Salesforce visitor identification shows how the data reaches existing records. If you are a small SaaS team, the visitor ID playbook for B2B SaaS covers how to route those visits to the right person.
Common Mistakes Small Teams Make
- Installing the tag twice, which inflates sessions and conversions.
- Skipping key events, so reports show traffic but not demo or pricing activity.
- Leaving internal traffic in reports, including your own team's visits.
- Missing cross-domain setup when the new site and the main site share a user journey.
- Ignoring consent settings for visitors in regions with strict rules.
Final Checks Before You Rely on the Data
Before you trust the numbers, confirm that visits appear in Realtime, key events fire on test submissions, and no duplicate tags load on any page. Then review the data weekly for the first month. Clean setup turns Google Analytics into a reliable base for the pipeline decisions your team makes each week.
If you want the visits on your pricing and demo pages to become named accounts your team can contact, book a free demo of Happierleads and we will show you how identification fits into your current setup.
Frequently asked questions
Do I need a new Google Analytics account to add a second website?
Not necessarily. You can add a new property to an existing account. Create a separate account only if the sites need completely separate access controls or billing.
What is a web data stream in GA4?
A web data stream connects one website URL to a GA4 property. You enter the full URL, and Google provides a Measurement ID that you install on the site.
How do I know the tag is working?
Open the Realtime report and load the site in another browser. If your visit appears within a few moments, the tag is firing. Check key events by submitting a test form.
Can Google Analytics show which company is visiting my site?
Google Analytics reports sessions, sources, and behavior, but it does not identify the company behind a visit. Website visitor identification tools such as Happierleads are built for that purpose.
Should I track pricing page views as a key event?
Many B2B teams do, because pricing page visits often signal stronger buying intent than general blog reads. Track them alongside demo requests and form submissions.




