Analytics and tracking so you can see real enquiries

Who this is for

You have a site and you cannot answer a basic question: which page led to the last ten enquiries? Sometimes the tag was never installed. Sometimes three old tags fight each other. Sometimes the form "works" in the inbox and never reaches analytics. This service fixes that measurement. It does not create the traffic.

You should be willing to put the analytics property in a Google account you control. We will not park your history in our login. If you want ads conversion tracking as well, say so, because the ads account is a second access grant. Google Ads work itself is Google Ads management. This page is the measurement layer.

What we set up

A short list of events, written down before we touch the tag. For a marketing site that is usually the form submit, the click to call, the click to email, and the click to WhatsApp if you use it. For a shop, add purchase, with the value the platform already knows, not a number we invent. Page views stay on, because without them the events have no context.

We respect a consent choice where your site already asks for one. ENZORA's own site loads analytics only after a visitor accepts. We will not bypass a banner you are required to show. If you have no banner and your counsel says you need one, we tell you before we ship the tag. We are not your lawyer.

The check is a real test. We submit the form or place a test order and we show you the event in the realtime or debug view. A screenshot of a tag assistant with no test lead is not a handoff. Our notes on how measurement sat beside speed work are in Next.js Core Web Vitals on the Vercel free tier, which is about our stack. Your tag can sit on WordPress, Shopify, or a custom site. The test is the same.

The sequence

1. List the events and the account that will own them.
2. Remove duplicate or abandoned tags when you agree they are unused. We do not delete a tag you still need for ads.
3. Install the remaining tag in the way the platform allows, after consent if consent exists.
4. Run the test lead and confirm it in the tool and in your inbox.
5. Write a half page that says what each event means and what it does not mean.

Cross-domain checkout and some embedded booking tools need an extra step. If we cannot see inside the embed, we say the event will be incomplete rather than faking a complete setup.

Problems that make reports lie

Counting the thank-you page as a conversion when people can open that URL directly. We prefer the submit event, and we still note the thank-you URL as a backup if the event is hard to fire.

Internal traffic. Your own tests will inflate a small site. We add a filter when the tool allows it, and we tell you to use it.

Mixing currencies or tax in a purchase event. We pass the value the store reports and we label the currency. We do not "correct" your revenue in the tag.

Judging a redesign on a three day window. Tracking lets you compare later. It does not make a week of data a verdict. If you are deciding whether to rebuild, read signs you need a redesign and use the events as one input.

What we will not sell

A custom looker studio mural with twenty charts for a site that gets a handful of enquiries a week. The half page note is the report. If you want a monthly reading of those events, it can sit inside SEO growth or a care quote. Rankings are not part of this service.

We also do not install a tag manager container you do not control, and we do not add extra marketing tags "while we are in there" without naming them.

Related work

The form itself may need a clearer page. That is conversion optimization. The site build prices, if tracking is part of a new site, are on pricing. Ask for the event list review at contact.