Attribution infrastructure, so you stop paying for guesses.
First-party click tracking, server-to-server postbacks, and warehouse reporting that answers in earnings per click. Built on your domains, in your accounts.
- Audit what fires
- Stand up the spine
- Model and reconcile
- Hand you the dial
Add up the conversions your platforms report and compare the total to the revenue in your accounting system. The first number is almost always larger, often by a multiple. Each platform is answering a different question with partial visibility, and the sum of several partial truths is not a truth.
We build the spine underneath instead: click tracking on domains you own, conversions reported server-side, and a warehouse that reconciles to the finance number and answers in earnings per click.
Concretely, what you get.
First-party click spine
Redirect and tracking infrastructure on your domains. Durable click IDs, bot filtering, a permanent event record.
Server-to-server postbacks
Conversions reported from your server to every platform and network, so attribution survives ad blockers, ITP and consent gates.
Warehouse and rollups
Modelled spend and revenue rolled to EPC, EPV, revenue per page and contribution margin.
Platform plumbing
GA4, Meta CAPI, Google Ads offline and enhanced conversions, affiliate networks — wired and validated against live traffic.
Integrity monitoring
Automated checks for dead links, broken postbacks and silent tracking failures. A quiet failure looks exactly like a bad week.
Dashboards that answer
Built around the decisions you make weekly, not around what the BI tool renders by default.
- 01
Audit what fires.
Instrument live traffic, compare what platforms claim against what the server saw. The gap is the story.
- 02
Stand up the spine.
Click infrastructure and postbacks deployed alongside existing tracking, so nothing goes dark.
- 03
Model and reconcile.
Warehouse the events, join spend to revenue, reconcile to finance until they agree.
- 04
Hand you the dial.
Dashboards, alerting, documented model. Budget arguments get settled by data instead of seniority.
Four ways in. Pick by what you need holding.
Most firms make you book a call to learn what it costs. Here are the ranges, the timelines, and what comes out the other end — so the first conversation can be about your project.
- 011 week
Scoping engagement
You have an idea, a prototype, or a stalled project and need a real plan with a real number.
from $15,000- → Written scope: what ships, what doesn't, what it costs
- → Architecture sketch with the cost-per-request model
- → Eval plan — how we'll know it works
- → Fixed price or rate-plus-ceiling for the build
Start with a scopeusually leads to product build - 026–16 weeks
Product build
You know what you need built and you want it running in production, in your repository, on a date.
$60,000 – $250,000- → A live system: web, native mobile, or agent — typed end to end
- → Thin slice in production by week three
- → Evaluation harness you can run yourself
- → Runbooks, a working local environment, a named handover
Scope a buildusually leads to retained operation - 038–20 weeks
Platform & infrastructure
The attribution spine, the data layer, or the multi-surface system the rest of the business stands on.
from $150,000- → First-party click tracking on your domains, server-side postbacks
- → Warehouse model reconciled to finance
- → Shared engines every property inherits
- → Integrity monitoring on the whole chain
Scope a platformusually leads to retained operation - 04Monthly, 3-month minimum
Retained operation
You want what we built to keep improving, with one accountable party and a weekly number.
from $12,000 / month- → Deploys, incidents, and iteration against the eval harness
- → Weekly one-page readout: what moved, what changed, what's next
- → Cost-drift and quality monitoring
- → An exit written into the agreement from day one
- Minimum
- Minimum engagement is $25,000. Below that, a senior build team rarely pays for itself and we will say so.
- Ranges
- Ranges, not quotes. The scoping week is what turns a range into a number, and it is credited against the build if you proceed.
- Ownership
- Every tier creates repositories, cloud accounts and domains in your name from the first commit. Nothing is held.
Asked and answered.
- Isn't this what GA4 is for?
- GA4 is one reporting surface, not an attribution system. It can't see server-side conversions it wasn't told about, can't reconcile spend to revenue, and doesn't own your click data. We treat it as one destination among several.
- Will this survive cookie deprecation?
- That's the point of building it first-party and server-side. Click identifiers live on your domain and conversions are reported server to server.
- Do we own the infrastructure?
- Yes — your domains, your cloud accounts. Built so you could fire us and keep every byte.
- How long does it take?
- Roughly a week of audit, then four to eight weeks depending on how many platforms and networks need wiring.
- What if the new numbers look worse?
- They sometimes do, and that is the system working. Decide in advance that you want the real number rather than the comfortable one.
Need attribution?.
Two honest paragraphs beat a ten-page RFP. We answer inside one business day, and the first call is 45 minutes with someone who can scope it.
Or write directly — t@moher.ai