Marketing and measurement

Know what your marketing actually returns.

We connect your advertising, website, and CRM so that every dollar of spend can be traced to the revenue it produced.

What is server-side tracking?

Server-side tracking records leads and sales on a server you control, where conventional tracking depends on the visitor's browser.

Browser-based tracking has become unreliable. Safari, for example, limits cookies set by scripts to seven days (WebKit, Intelligent Tracking Prevention 2.1), which is shorter than most sales cycles.

Your CRM knows which leads became customers. Your ad platform does not.

A sale usually closes weeks after the first click, inside your CRM. The advertising platform never learns about it, so it keeps optimising for form submissions and not for customers.

The remedy is to send closed sales, with their value, back to the platforms that generated them.

What we put in place.

Five components, each with a specific job.

  1. 01

    Server-side tagging.

    Runs in your own cloud account, on your domain, and is not affected by ad blockers.

  2. 02

    Conversion APIs and enhanced conversions.

    Events are sent from server to server with hashed contact details, so they can be matched where browser tracking fails.

  3. 03

    Offline conversion reporting.

    When a lead becomes revenue in your CRM, the advertising platform is told, and bidding can follow profit.

  4. 04

    Identity and de-duplication.

    Each lead is recorded once, so totals are not inflated.

  5. 05

    Call, form, and CRM matching.

    Phone calls are matched to the click that produced them and to the CRM record.

You receive: a working measurement system in your own accounts, with a test log showing that the figures reconcile.

What changes once measurement is reliable.

01

Calls are attributed.

Each call is tied to the campaign and keyword that produced it.

02

Leads are counted once.

Duplicate form submissions no longer inflate the numbers.

03

Platforms optimise for revenue.

Closed sales are reported back, so budgets move toward what converts.

04

The key metric changes.

Cost per lead gives way to cost per closed sale.

Reporting by campaign, keyword, and salesperson.

With the data connected, you can see attendance rate, close rate, and revenue per lead at each level, and make budget decisions on that basis.

StackHubSpotSalesforceGA4CallRailMeta CAPIGoogle Ads APIserver-side GTMBigQuery

Why measurement comes before automation.

An automated system acts on the data it is given. If the data is wrong, the system makes wrong decisions more quickly.

For that reason, where a business also wants AI or automation, we put reliable measurement in place first.

Common questions.

What is the difference between client-side and server-side tracking?
Client-side tracking runs in the visitor's browser, where ad blockers and short cookie lifetimes cause data loss. Server-side tracking collects the same events on a server you control and delivers them reliably.
How long does implementation take?
A standard implementation is typically completed within a few weeks. Offline conversion reporting then becomes more useful over time, at the pace your sales close. The timeline is confirmed in the written plan.
Does this work with GA4 and offline conversions?
Yes. We implement enhanced conversions, conversion APIs, and offline imports, matched by click identifier and hashed contact details.
Is server-side tracking compliant with privacy rules?
Consent requirements still apply and are respected. Identifiers are hashed before they leave your systems, and data processing agreements are available on request.
Do we need to fix measurement before investing in AI?
In most cases, yes. Automated systems depend on accurate data, and you need a reliable baseline to judge whether they are working.
How is this priced?
As a fixed scope with a fixed price, agreed in writing before work starts.

See what your marketing is really producing.

Tell us which platforms and CRM you use, and what you are unsure about.