Skip to content
WebrenewDocs

Leads and business tools

Add Google Analytics when you need it

See which channels bring visitors and what they do next. Verify the setup before trusting the numbers.

Who this helps
Owners who want to measure website visits with GA4.
Before starting
Have a live domain, an Analytics account, and the site's privacy and consent arrangements ready.
Done when
A test visit appears in the correct GA4 property, with a verified page address.

01

Decide what to collect first

Start with visits and one meaningful enquiry action. Collect only the information needed to make a business decision.

Launch includes Webrenew Analytics. GA4 is an optional separate service, installed through Custom code or a supported integration.

  1. Confirm the privacy notice and consent requirements for the business's visitors.
  2. Ask Webrenew or the site's developer to configure and test any required consent controls before enabling tags.
  3. Keep customer names, email addresses, phone numbers, and message text out of analytics events and URLs.

A banner on webrenew.com does not control a separate customer domain. Remove the installed snippet and publish to stop its tag. This does not delete past provider data.

02

Create the property and web stream

Use a Google account controlled by the business. Invite an agency or developer instead of giving away the only owner login.

  1. Open Google Analytics. In Admin, create a property for the business website.
  2. Choose the reporting time zone and currency used by the business.
  3. Add a Web data stream for the final HTTPS domain.
  4. Copy the Measurement ID that begins with G- from the stream details.

The Measurement ID identifies the stream. It is not a Google login, an API secret, or a GTM container ID.

03

Connect a Launch website

Use the Google tag installation snippet for the correct web stream. Launch's Analytics tab reports Webrenew Analytics; it is not a GA4 ID installer.

  1. Copy the official Google tag snippet for the selected web stream.
  2. Open Site overview → Custom code and place the snippet in Head code.
  3. Configure any required consent controls before the tag can collect data.
  4. Save and publish the site.
  5. Test on the connected custom domain. Custom code is off on the webrenew.app address.

Do not install the same stream through both this snippet and another tag manager. Duplicate installations can inflate counts.

04

Connect a self-hosted website

A downloaded site needs its own tag and consent integration. Check which export format the project uses before editing it.

  1. Send the developer the Measurement ID and the live domain.
  2. Ask for one installation in the shared site layout, with the agreed consent behaviour.
  3. Build and deploy the update through the normal hosting process.
  4. Test page views on direct loads and when navigating between pages.

A GTM- ID belongs to Google Tag Manager. Use the correct official container installation when choosing Tag Manager instead of a direct Google tag.

05

Verify a real visit

Use Realtime for a quick connection check. Use DebugView to inspect a specific device's events.

  1. Open the live site in a test browser. Grant analytics consent if the site's setup requires it.
  2. Open GA4 Reports → Realtime and look for the visit.
  3. For detailed checks, connect the live URL at tagassistant.google.com to enable debug mode for that device.
  4. Open Admin → Data display → DebugView. Check page_view and its page_location.
  5. Navigate to another page. Check for missing or duplicate page views.

If nothing appears, check the property, G- ID, live domain, consent state, and test-browser extensions. Standard reports take longer than Realtime.

06

Read the reports that help decisions

Use Traffic acquisition for the source of sessions. Use Landing page to see where visits begin. Report menus can vary by property setup.

  1. Compare source and medium over the same date range each week.
  2. Add the verified enquiry key event to the review.
  3. Compare the result with qualified enquiries and won work in the team's records.
  4. Investigate sudden changes before adjusting the marketing budget.

Visitors, sessions, and events are different counts. Consent choices and blockers reduce coverage, so analytics is not a complete customer ledger.