Skip to content
Orvenant
Orvenant

Analytics & tracking

Measure what your business can act on.

Analytics and tracking implementation with clear event definitions, consent boundaries and reporting. Understand the journey from visit to meaningful enquiry or sale.

Measure decisions, not just activity.

A busy dashboard can still leave a team unsure which enquiries became useful conversations. Start with the decisions a report should support: where to invest, which page needs work, and when a lead should be followed up. We map the journey from an eligible visit to a meaningful action and identify what can actually be observed. That keeps page views, email clicks and confirmed enquiries from being treated as the same thing.

A measurement plan your team can inspect.

The implementation follows agreed definitions and the consent choices made by the business and its visitors.

Event dictionary

Name the actions that matter, their permitted parameters and where they originate. Assign an owner to each definition so a later website or CRM change does not silently change the report.

Explore Event dictionary

Consent-aware collection

Review when tags may run, what data may be sent and how a visitor can change a choice. Avoid placing form text, credentials or unnecessary identifiers in analytics events.

Verification and reporting

Compare browser events with the destination system, check duplicate paths and document missing-data conditions. Build reports around questions the team can answer, not every available metric.

Explore Verification and reporting

Trace one customer action end to end.

We choose a small set of real journeys, such as finding a service, opening contact and completing a permitted enquiry. For each, we check the browser, consent state, analytics destination and CRM outcome where access has been approved. An email composer opening is an intent signal; it is not proof that the message was sent. The resulting acceptance record makes later changes testable by someone other than the person who configured the tag.

Interpret the gaps honestly.

Browsers, blockers, consent choices and people moving between devices limit what any analytics system sees. We state those limits alongside the reports. Advertising attribution or customer matching needs a separate purpose, notice and approval; a general analytics installation does not authorize it. Your organization decides the lawful basis and retention settings with its advisors, and we implement the approved technical boundary.

Keep the definitions with the business.

Your team receives the event map, account and access ownership, a verification checklist and a record of known gaps. When a form, consent notice or CRM stage changes, the same record shows which events need retesting. For the wider acquisition journey, see our paid search and conversion optimization services.

Some of the teams we have worked with.

Across talent, fitness, mobility, payments and local commerce.
RandstadClassPassVeezuRushpaySupport Black Owned

Questions before we start.

Can analytics show which campaigns produced customers?

It can support that question only when campaign tags, consent, lead identity and CRM outcomes are connected in an approved way. We distinguish observed events from inferred attribution and agree which customer data, if any, may be used before building the link.

Do we need a new analytics platform?

Not necessarily. We first review the current property, tag implementation, event definitions and access. Correcting duplicate events or unclear lead stages may be more useful than moving to another tool.

A DIRECT CONVERSATION

Bring us the problem. We’ll work through the next step.

Share what exists today and what you want to change. We can discuss the scope, dependencies and a practical way forward.

Privacy settings

Optional Google Analytics measures page visits and contact-option use. Rejecting keeps Analytics off. Accepting allows analytics cookies. Advertising features stay off, and enquiry contents and contact details are not sent to Analytics.

Withdrawing stops future collection and removes this site’s accessible Analytics cookies. It does not erase information already received by Google. Privacy notice · Cookie notice