Measure the actions that matter and understand the gaps. Clear event definitions, tested tracking and reporting that helps you decide what to do next.
Conversion tracking records agreed website actions so you can assess marketing and the customer journey. I help define the outcomes, review existing analytics and tags, configure supported events and test what is actually recorded. The work can cover website analytics, advertising conversion signals and a practical reporting view within an agreed platform scope.
We separate intent from completion and business value. Clicking a phone link is not the same as having a conversation; submitting a form is not the same as becoming a suitable lead. Reports explain those differences and the limits created by consent choices, browser restrictions, external platforms and attribution methods. Good tracking improves your evidence; it does not manufacture campaign performance.
Useful when the business needs to trust a specific decision, rather than collect more charts.
Your website analytics, ad account and enquiry inbox show different totals. We inspect definitions, date settings, attribution and duplicate signals before treating any one figure as the whole truth.
Reports combine button clicks, form starts and submissions. We define a meaningful primary outcome and keep supporting actions visible without inflating the headline number.
A new site, campaign or form changes how actions happen. We map the journey and test measurement before launch, including what cannot be observed on external systems.
The engagement covers agreed setup and verification, with enough documentation for your business to keep control.
Define each action, trigger, required values and intended use. Identify primary business outcomes versus diagnostic events. Agree naming, ownership and the reporting question each event answers before adding tags.
Review the agreed analytics, tag management and advertising accounts, existing plugins and consent configuration. Locate duplicated tags, missing paths and access gaps. Check which system generates an event and which destinations receive it.
Implement the supported events and connections in scope. Test success, validation errors, repeat actions and relevant consent states; check that completion signals fire at the correct point and avoid accidental duplication. Do not put form contents or unnecessary personal information into analytics events.
Compare recorded actions with the available business records over an agreed period. Explain attribution windows, reporting delays and observability gaps. Deliver event documentation and a report or dashboard built around decisions, with responsibility for future checks.
Illustrative measurement plans. These examples do not report client traffic, bookings or revenue.
An ad account reports conversions, but the contractor cannot relate the number to worthwhile enquiries.
The approachSeparate phone-link clicks and successful form submissions. Add a practical lead-quality review, with any offline status connection assessed against the available systems and permissions.
What to checkReport observed actions and suitable enquiries as distinct stages, explaining unmatched or unobservable contacts.
The website sends players to an external booking provider without exposing confirmed bookings to website analytics.
The approachTrack the relevant outgoing action, check provider-supported completion data and document any cross-domain limitation. Label a booking-link click as a handoff until completion can be verified.
What to checkUse observed handoffs and separately available provider totals without treating them as interchangeable.
A product business sells standard items and receives made-to-order requests through the same site.
The approachDefine separate purchase and enquiry events. For supported ecommerce tracking, check order identifiers, value handling and duplicates against actual order records; define cancellations and refunds in reporting.
What to checkReport completed orders, order value and custom enquiries separately, with the measurement and reconciliation limits stated.
An event should have a definition and a test before it becomes a headline in a report.
| Action | What to record | Acceptance check and limit |
|---|---|---|
| Visitor clicks a phone link. | Contact intent from the relevant page. | Record the click once; do not label it a completed call or qualified lead. |
| Form shows a validation error. | A diagnostic error signal only if needed and safely defined. | No successful-submission event; exclude entered personal details from analytics. |
| Form submission succeeds. | Successful submission for the agreed form. | Verify the success path and actual delivery; check refresh or duplicate tag behaviour. |
| Visitor moves to an external booking system. | Outgoing booking handoff. | Confirm the link and label the observability boundary until completion data is supported. |
| A supported store records a completed order. | Purchase with an agreed identifier and value definition. | Check one event per order and reconcile to order records; explain refunds and attribution separately. |
Start with the business decision, action definitions and accounts involved. Identify data owners, consent settings and any third-party journey boundary.
Inspect existing tags and events, remove agreed duplication and implement the scoped measurement plan. Keep a record of changes and account responsibilities.
Test successful, failed and repeated actions across the relevant devices and consent states. Check event receipt and the underlying form, order or handoff rather than relying on an installed tag alone.
Compare an agreed sample with business records, document differences and explain the reporting view. Give your team the event definitions and a checklist for rechecking after site or platform changes.
The right scope makes the work useful. Agree the deliverables, dependencies and responsibilities before starting.
Scope follows the platforms, events, forms, ecommerce requirements, consent setup, external handoffs and reporting connections. A straightforward lead form differs from a store with order data and several advertising destinations. Tool fees and specialist integration work are identified separately.
Definitions and account access come first. Configuration is followed by live-path testing; reconciliation needs an agreed observation period and access to the relevant business records. A platform’s reporting delay is not the same as an implementation fault.
I define, implement and verify the agreed measurement. You own the accounts, approve data collection choices and supply access plus business records for reconciliation. Your team or adviser owns privacy policy decisions; third-party providers determine which completion data their systems expose. Future site changes need an assigned recheck owner.
The event acceptance table shows how actions are distinguished and implementation is checked. Russley’s website connects visitors with an existing DotGolf booking route: a useful example of the kind of external handoff that needs its own measurement definition. The tracking scope starts by checking what that external system can actually report.
A documented website project with an existing external booking handoff.
They can use different definitions, attribution windows, date treatment and measurement methods. Duplicated tags, consent choices and reporting delay can add further differences. We compare the specific action and settings before reconciling totals; disagreement alone does not prove either account is broken.
No. Some actions happen by phone, offline, across devices or on systems that do not expose completion data. Consent and browser choices also create gaps. We define what is observed, what comes from business records and what remains an estimate instead of promising complete visibility.
Sometimes it is part of a useful implementation, but the real success path needs checking. A page may be revisited, loaded directly or used by several forms. The test should establish that a genuine successful submission is recorded as intended and that errors are not counted as success.
These can form part of the agreed scope. We review your website platform, analytics, tag manager and advertising accounts, then specify the supported events and destinations. Ecommerce, offline outcomes, call tracking and server-side setups each need their own capability and scope check.
It cannot recreate events that were never collected. Existing records may help explain a historic period, but they should not be presented as newly measured website behaviour. We document the implementation date and any breaks in comparability when reading later reports.
An event definition list, the scoped configuration, test evidence, known limitations and the agreed reporting view. Your business retains account ownership. We also identify when checks should be repeated, such as after a form replacement, site release or connected-platform change.
Choose the service that solves the problem in front of you.
Use trustworthy outcome data to prioritise and assess journey improvements.
Connect campaign optimisation to clearly defined conversion signals.
Assess paid social actions with explicit measurement and attribution boundaries.
Connect recorded actions to tested marketing follow-up where the systems support it.
Work directly with Dan Smith. Based in Christchurch, working with businesses across New Zealand.
Bring your website, platforms and the report you are trying to trust. We can define the important actions, check the gaps and scope a measurement setup you can use.
Good websites work harder. Cookies help us see what’s working.
Essential cookies keep things running. With your permission, analytics cookies help us understand how you use the site, and marketing cookies help us measure ads and show relevant ads. Optional tracking stays off until you say yes. You can change your mind in Cookie Preferences.
The essentials keep this site working. Analytics and marketing cookies are optional. Choose what suits you and change your mind here at any time.
Essential cookies enable basic functions and are necessary for the proper function of the website.
Optional analytics cookies help us understand visits and interactions using browser identifiers. They run only if you accept Statistics and the relevant service.
Google Analytics 4 measures page visits and meaningful interactions after you accept analytics cookies. We do not send contact form answers, names, email addresses or phone numbers in analytics events.
Service URL: policies.google.com (opens in a new window)
Marketing cookies are used to follow visitors to websites. The intention is to show ads that are relevant and engaging to the individual user.
Measures page visits and successful enquiries and helps Daniel James show relevant ads on Facebook and Instagram after you visit. This runs only if you accept Marketing and Facebook Pixel.
Service URL: www.facebook.com (opens in a new window)