Skip to content
WebrenewDocs

Leads and business tools

See what visitors do on your website

Read visits, events, and goals without installing a separate analytics account.

Who this helps
Site Owners and Admins enable analytics. Site collaborators can inspect the site's reports.
Before starting
Publish the website and use an owner's Site or Pro plan.
Done when
A live visit and a relevant customer action appear in the correct site's reports.

01

Turn on Webrenew Analytics

Open Site overview → Analytics and enable Webrenew Analytics. It uses no cookies or visitor browser storage.

The setting normally applies to the live site immediately. If the app reports that the live update failed, publish to apply the saved setting.

  1. Enable analytics for the intended site.
  2. Open a live page, not just the editor preview.
  3. Return to Analytics and check the matching time range and address.
  4. Compare the new visit with the report.

Turning analytics on cannot recover visits that happened before collection began. Browser blockers and excluded traffic can also affect counts.

02

Read visitors, views, and sources

Choose 7 days, 30 days, or 90 days. Use the address filter when more than one site address appears.

Launch counts visitors once per day. Views count page visits. A multi-day visitor total is not a count of distinct people across the whole period.

The breakdowns cover pages, referrers, UTM sources, countries, devices, browsers, and systems.

  1. Compare the same period and address when evaluating changes.
  2. Inspect landing pages and useful sources.
  3. Check the actual enquiries before judging business results.
  4. Use Export CSV for the report data within its displayed export limit.

03

Measure useful actions

Analytics can record outbound links, email links, phone links, file downloads, and accepted form submissions. Custom site events can also appear.

Form submitted represents a submission accepted by lead intake. A phone or email click is an intent signal; it does not prove a completed call or message.

  1. Test one useful action on the live site.
  2. Find its exact event name in the Events section.
  3. Inspect the event's page and relevant details.
  4. Select Export events for a copy.

Keep customer names, email addresses, phone numbers, message text, and other private details out of custom event names and properties.

04

Make the important action a goal

A goal highlights an existing event or a page path. It reports visitors who reached it; it does not install a new form or event.

  1. Choose Event or Page in the goal controls.
  2. For an event, use its exact name, such as Form submitted.
  3. For a page, enter its path, such as /thank-you.
  4. Select Add goal and check the resulting report.

A thank-you page view can occur without a new submission. Prefer the confirmed form event when measuring accepted enquiries. Removing a goal keeps its underlying events and views.

05

Add an event when the built-in actions are not enough

Ask Launch to track the specific action, or use track from wr/ui in site code. Use a stable descriptive name and a few non-personal details.

Example for a developer · call after the actual action
import { track } from 'wr/ui'

track('Pricing option selected', { plan: 'garden-care' })

An event should report something that happened. Do not fire a completed-booking event merely because someone clicked a booking link.

06

Know what happens when collection stops

Turning collection off stops new data. A plan ending can also stop collection and schedule deletion of existing analytics data.

Use the deletion date displayed in Analytics as the account-specific deadline. Export needed reports before that date.

Webrenew Analytics and Google Analytics are separate systems. Enabling one does not configure the other.