It is not an implementation error or the fault of one platform. This is simply how measurement set up in the browser works today, whoever configured it.
Tracking scripts loaded in the browser are often blocked by ad blockers before they run. The order exists, the event does not.
Under Intelligent Tracking Prevention, Safari deletes cookies set by script after 7 days, while selected Google cookies live for 180 days or a year. A return visit after that looks like new traffic, even though it is the same customer.
The algorithm learns from what came back to it. A missing conversion does not spoil the report; it spoils the next budget decision.
Four stages, each with a deadline. On your side there is access to grant and one decision to make: what exactly we count as an order.
1 week
We match orders from your store against events in the ad platforms. We check where most of them go missing: in which browsers and at which checkout step.
1-2 weeks
We set up the server container on your domain: in Google Cloud on Cloud Run or App Engine, or with a container hosting provider such as Stape. The choice depends on traffic and on who will maintain it afterwards.
2-4 weeks
We move events from the browser (client-side) container to the server container one at a time, starting with the purchase. We take care of deduplication along the way, so the same order is not counted twice.
1-2 weeks
We repeat the measurement from the first stage and show the difference on the same numbers. What remains is an inventory: which event goes to which system and with what data.
The rating alongside is an average from three sites and covers the whole JustIdea agency, not this one service. Server-side tracking proves itself only after a few months anyway, so it is worth knowing how we work during that time.
weighted average of 224 reviews across three platforms. Clients gave them, and each site below links to the profile with the full text of every review.
Read the reviewsAn implementation is finished only when the platform confirms the events have reached it. Partner statuses give us a view of that answer at the source, not just in the analytics tool.
When the ad platform and the report drift apart, we have a route to raise it on Google's side, not just our own hypothesis. On top of that, access to features before their public launch.
On Meta's side, browser events and server events do not count the same way. Partner status gives us access to event match quality diagnostics, without which a server setup is guesswork.
A third channel in which the same tracking has to be confirmed separately. We read the numbers in the Microsoft Advertising dashboard, because only there can you see what reached it.
The prices below are ours. You pay for the server and the consent tool directly to the providers, because that cost depends on store traffic and stays on your side even if we stop working together. We give the ranges for those amounts in the FAQ below the pricing.
Server, event migration and documentation, paid once.
Tracking that keeps up with the store: new events, site rebuilds, changes on the platforms' side.
Checking that data is still flowing, before you notice it in the monthly report.
The call is led by a new business specialist. When we get into the details of an account, the specialist for that channel joins in. We reply within one business day.
Before the meeting we review your website, your visibility and what your campaigns show from the outside. We will not open with “so, what does your company do?”.
The reply comes from the same new business specialist who will run the call. No qualification form and no call from an unknown number.
We go through your numbers and your questions. If it turns out we are not the right fit, we will tell you straight away.
