Trustworthy data
Events verified one by one, with no duplicates and no gaps.
Analytics & Tracking
Without correct data every decision is an opinion. I set up a measurement system connecting visits, enquiries and sales, while respecting the user's consent.
The Meta Pixel collects events from the user’s browser; the Conversions API sends them from your server. The data type is the same, but the server channel is not interrupted by browser restrictions, extensions or third-party limits, so it reduces the number of unrecorded conversions.
The two are not alternatives: Meta’s recommended setup uses both, with a deduplication key so the same event is not counted twice. The Conversions API requires a server-side component and an access token, which must never sit in the website’s code. Consent still governs everything: events are sent only when the user has allowed it.
Who this is for
Measurement serves the activities that generate the data: explore Google and Meta Ads campaigns and see how organic visibility is measured.
Problems I solve
The solution
I start from a measurement plan: which actions genuinely matter to the business, what they are called, which details they should carry. Skip this and you simply accumulate useless events.
Then I implement everything in Google Tag Manager, with consistent events in Analytics 4 and the advertising platforms, verifying every tag in preview and real-time mode.
Finally I build a lean dashboard with the few metrics that support decisions: contacts, sources, cost per lead, trends over time.
What is included
Concrete benefits
Events verified one by one, with no duplicates and no gaps.
A few clear metrics instead of reports nobody reads.
Platforms receive correct signals and optimise better.
Tags wired to consent, with Consent Mode v2 configured.
Comparison
| Aspect | Meta Pixel (browser) | Conversions API (server) |
|---|---|---|
| Data origin | The user’s browser. | Your server, from the events it records. |
| When it is enough | Getting started, modest volumes, need to launch quickly. | Conversion loss is visible, or ad spend is significant. |
| Limits | Events lost to browser restrictions and extensions. | Requires server-side development, token management and deduplication checks. |
| Together | Recommended setup: both active, sharing an event identifier to avoid double counting. | |
How I work
The same sequence applies to a website, a campaign and an automation project. It keeps decisions traceable and avoids work done for its own sake.
I study your market, your competitors, the data you already have and how enquiries reach you today. Without analysis, every decision is guesswork.
We define measurable goals, priorities and budget. We decide what comes first and what can wait, in a written plan you can actually read.
Structure, content, interfaces and conversion paths are designed before a single line of code is written or a campaign goes live.
I build the website, campaigns, automations and tracking, with quality checks on speed, accessibility and data accuracy.
We review results with real data and act where it matters. The work does not end at launch.
Frequently asked questions
Sources and references
Content on this page last reviewed: September 2026. The tools referenced above are changed by their own providers: where in doubt, the official documentation linked here takes precedence.
Related services
Google Ads, Meta Ads, remarketing and lead generation.
Explore Google and Meta AdsAdvertisingSEO, Local SEO, GEO and visibility in AI answers.
Explore SEO and AI SearchSEO & AI SearchCRM, GoHighLevel, WhatsApp, email and workflows.
Explore CRM and automationCRM & AutomationTell me about your project. We will look at your goals, obstacles and opportunities together and identify the most effective solution.