Services
Web Design & DevelopmentWebsite CareSEOMeta AdsAnalytics & Tracking
WorkPricingAbout Contact
Start a project

Restaurant

Jeepney Web Design and Development

Most businesses have analytics installed and still cannot answer the only question that matters: which page, campaign or click produced that enquiry. Usually the tracking was never set up for that — or it was, and nobody ever tested it.

  • SectorRestaurant
  • MarketNew Zealand
  • Year2025
  • ServicesWeb Design & Development, SEO, Analytics & Tracking
the starting point

The situation

A browser pixel and a server-side event both reporting the same action without a shared identifier, plus a thank-you page that fires again on refresh. The numbers look healthy and mean nothing.

A browser pixel and a server-side event both reporting the same action without a shared identifier, plus a thank-you page that fires again on refresh. The numbers look healthy and mean nothing.

the problem

What needed solving

  • A browser pixel and a server-side event both reporting the same action without a shared identifier, plus a thank-you page that fires again on refresh. The numbers look healthy and mean nothing.
approach

How it was approached

  1. 01

    A browser pixel and a server-side event both reporting the same action without a shared identifier, plus a thank-you page that fires again on refresh. The numbers look healthy and mean nothing.

technical detail

Implementation

what was builtdetail
ItemDetail
A browser pixel and a server-side event both reporting the same action without a shared identifier, plus a thank-you page that fires again on refresh. The numbers look healthy and mean nothing.
decisions

Key decisions and constraints

A browser pixel and a server-side event both reporting the same action without a shared identifier, plus a thank-you page that fires again on refresh. The numbers look healthy and mean nothing.

evidence

The work

outcome

What changed

A browser pixel and a server-side event both reporting the same action without a shared identifier, plus a thank-you page that fires again on refresh. The numbers look healthy and mean nothing.
A browser pixel and a server-side event both reporting the same action without a shared identifier, plus a thank-you page that fires again on refresh. The numbers look healthy and mean nothing.
A browser pixel and a server-side event both reporting the same action without a shared identifier, plus a thank-you page that fires again on refresh. The numbers look healthy and mean nothing.

Working on something similar?

Describe the business and what is not working. You will get a straight answer about the approach, the likely timeframe and roughly what it costs.

Reply within one business day