Server-side attribution

Attribution your clients can reconcile to real sales.

Browser tracking is breaking down, and with it your ability to prove the ads worked. Metiva measures every conversion first-party and server-side, ties it to the real person and the original ad click, and sends that truth back to Meta, Google, LinkedIn and TikTok.

30 minutes, no slides. We map your real attribution gap live. Dutch or English.

go.metiva.io/web-intelligence
Metiva web intelligence: company-level visitor identification

A real Metiva web intelligence view with demo data, not a render.

The post-cookie problem

When the ad dashboard stops matching the client's sales, the retainer is next.

Apple's iOS changes and the end of third-party cookies broke browser-side tracking. Ad platforms now optimise against form-fills they can no longer reliably see, and the conversions in your dashboard drift away from the deals your client actually closed.

  • Conversions go missing, so your reported results understate what the ads really did.
  • The platform optimises blind, chasing cheap clicks and form-fills instead of revenue.
  • Attribution stops reconciling, and the harder a number is to defend, the harder the renewal.

Metiva closes the loop inside the same system that holds the deals, so what the ad produced and what the client sold describe one truth.

Actual revenuePlatform-reportedthe gap

How it works

One first-party loop, from anonymous click to revenue and back.

The pixel captures the click at the source. Metiva resolves it to a real person and carries it onto the deal. When the deal advances, Metiva fires the conversion back to the ad platforms server to server, with the original click ID. No browser required for the part that matters.

Ad clickon the client siteFirst-party pixelmtv.js, first-partyPerson + dealresolved in MetivaDeal wonstage changeCAPIto 4 ad platformsThe conversion, and the revenue, sent back to the platform
1

Capture

mtv.js records the visit, the UTM and the ad click-ID slots, first-party.

2

Resolve

On form capture the click folds onto one canonical person record.

3

Convert

A stage change (call booked, deal won) fires a server-side conversion.

4

Reconcile

Spend joins your first-party funnel for ROI you can defend.

Server-side CAPI to Meta, Google, LinkedIn and TikTok, with a deterministic event ID so retries never double-count.

Server-side CAPI

When a deal advances, the conversion goes back, server to server.

When a deal changes stage, a call booked or a deal won, Metiva fires a server-side conversion to the ad platforms with hashed PII and the original click ID. Real adapters exist for Meta CAPI, Google (Enhanced Conversions for Leads plus Offline Conversion Import), LinkedIn CAPI and TikTok Events.

  • Four ad platforms, real adapters, mapped per deal stage to the events you choose.
  • A deterministic event ID shared with the browser pixel, so the platform deduplicates instead of double-counting.
  • Idempotent retries with a per-deal lock, backoff that respects each platform, and match-quality monitoring.
Book a demo
Metivaserver-sideMetaGoogleLinkedInTikTok

One deterministic event ID, shared with the browser pixel, so the platform deduplicates instead of double-counting.

Company-level de-anonymization

See which companies are on the site, resolve to a person only on consent.

Most of your traffic never fills in a form. Metiva surfaces who is on the site at the company level where person-level consent is not present, and resolves to a named person only when someone consents through a form. Consent is deny-by-default, IP addresses are truncated and encrypted at rest, and right-to-erasure is built in.

  • Company or account level where consent is absent. Person level only on consented form capture.
  • Deny-by-default consent gating, with targeting forwards suppressed until consent is granted.
  • IP truncation and encryption at rest, configurable retention, and delete-visitor-data erasure.

We do not publish a match-rate figure we cannot stand behind. We will show you real results on your own traffic in the demo.

How consent and compliance work
go.metiva.io/web-intelligence
Metiva web intelligence: company-level visitor identification

White-label reporting

Report ROI to each client, under your own brand.

Every client gets a per-company, branded reporting surface, built on the same first-party data the conversions came from. Show spend joined to leads, calls, closes and revenue per creative, with blended ROAS, CPL and cost-per-closed-lead graded against the targets you set. Because it is first-party and server-side, the numbers reconcile to what the client actually sold.

  • Per-client, branded, first-party reporting. Configurable pixel and tracking domain per company.
  • Spend joined to your funnel for blended ROAS, CPL and cost-per-closed-lead per creative.
  • Read-only per brand, so a client sees their results and nothing of your internals.
How agencies retain clients
Client logoQ3 performance
Read-only
Blended ROAS
4.7x
Cost per closed lead
EUR 214
Won-deal revenue
EUR 99k

Powered by your agency

Ad ROI and web intelligence

Spend joined to your funnel, for ROI you can defend.

Metiva blends ad spend with your first-party funnel so you can see blended ROAS, CPL and cost-per-closed-lead per creative, next to live web intelligence about who is on the site. Because attribution sits on the same records as the deals and the invoices, the ROI reconciles to real revenue.

  • Blended ROAS, CPL and cost-per-closed-lead per creative and per concept.
  • Won-deal revenue joined to spend, read from the same spine the deals live on.
  • Live web intelligence about the companies on the site, consent-gated.
See how one record powers the pipeline
go.metiva.io
Metiva command center: MRR, active clients, open pipeline and cash-in for an agency workspace
4
Ad platforms with real CAPI adapters (Meta, Google, LinkedIn, TikTok).
12
Ad click-ID slots captured first-party.
Server-side
Every conversion fired server to server, not browser-dependent.
1
First-party pixel on your client's own domain.

These are capability counts, not performance claims. We will show real numbers on your traffic in the demo.

Compliant by architecture

Built for the AVG, not bolted on after.

Compliance is a design decision in Metiva, which is exactly why it is safe to sell. Consent is off until granted, person-level data only on consent, IPs truncated and encrypted, and each client's data isolated by design and fail-closed.

Deny-by-default consent

Targeting forwards are suppressed until consent is decided and granted. Nothing leaks before the visitor says yes.

IP truncation and encryption

IP addresses are truncated and encrypted at rest, with configurable retention and audited reveal. Production hard-fails without an encryption key.

Right to erasure

Delete-visitor-data is built in, so a person can be removed cleanly when they ask.

Isolated by design

Each client's data is isolated by design and fail-closed, so one client can never see another's. Your data stays in the EU.

Questions

Straight answers for media buyers.

Yes. That is the point. The pixel is first-party and server-processed, so it captures and keeps the click ID even when third-party cookies and browser-side tracking are blocked. The conversion upload to the ad platforms happens server to server, which does not depend on the browser at all.

We keep de-anonymization at the company or account level where person-level consent is not present, and resolve to a named person only when someone consents through a form. Consent is deny-by-default, IPs are truncated and encrypted, and erasure is built in. This is designed for the AVG, not bolted on after.

Meta, Google, LinkedIn and TikTok, with real adapters: Meta CAPI, Google Enhanced Conversions for Leads plus Offline Conversion Import, LinkedIn CAPI and TikTok Events. You map each deal stage to the events you want per platform.

Every event carries a deterministic event ID shared between the browser pixel and the server-side upload, so the platform deduplicates. Retries use the same ID and a per-deal lock, so a retry can never fire the conversion twice.

It does the job that matters for paid media: tie the click to the person, the deal and the revenue, and feed that back to the platforms. It is first-party web intelligence plus closed-loop attribution, reported per client under your brand, not a generic web-analytics suite.

It is part of one operating system. The attribution loop runs on the same records as your inbox, pipeline, contracts and invoicing, which is why the numbers reconcile to real deals instead of living in a separate tool.

Metiva is priced per company, not per seat: a one-time implementation, then a monthly service retainer (a supportabonnement) priced by the client brands you manage, with unlimited seats. The monthly is a service retainer, not software rental: hosting, maintained integrations, support, and accurate attribution. Tell us how you run and we quote you directly, on WhatsApp or by email. See how it is priced on the pricing page.

The wedge, inside the whole system

Attribution your clients can finally reconcile to real sales.

Server-side, first-party, tied to the deal, reported under your brand. Part of one operating system you run your whole agency on.

30 minutes. No slides. We map your real attribution gap live. Dutch or English.