{"id":3836,"date":"2026-08-26T13:04:14","date_gmt":"2026-08-26T11:04:14","guid":{"rendered":"https:\/\/thedatastory.nl\/?p=3836"},"modified":"2026-08-26T13:18:41","modified_gmt":"2026-08-26T11:18:41","slug":"the-real-value-of-server-side-tracking-building-the-business-case","status":"publish","type":"post","link":"https:\/\/thedatastory.nl\/en\/data-stories\/the-real-value-of-server-side-tracking-building-the-business-case\/","title":{"rendered":"The real value of server-side tracking: Building the business case"},"content":{"rendered":"<div data-elementor-type=\"wp-post\" data-elementor-id=\"3836\" class=\"elementor elementor-3836\" data-elementor-post-type=\"post\">\n\t\t\t\t<div class=\"elementor-element elementor-element-1ad793d6 e-flex e-con-boxed e-con e-parent\" data-id=\"1ad793d6\" data-element_type=\"container\" data-e-type=\"container\">\n\t\t\t\t\t<div class=\"e-con-inner\">\n\t\t\t\t<div class=\"elementor-element elementor-element-1cf9a815 elementor-widget elementor-widget-text-editor\" data-id=\"1cf9a815\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t\n<p class=\"wp-block-paragraph\">Compare your ad platform reports against your own order data and the numbers rarely match. Meta reports fewer purchases than recorded by your online store or CRM, GA4 gives you a whole different number, and your ROAS changes depending on which number you used.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Conversions get lost on the way from the visitor&#8217;s browser to the ad platform. Ad blockers stop the requests, browsers delete the cookies that connect a click to a purchase, and some events never fire at all. The platform can\u2019t count what it never received.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The established fix to browser-level limitations is server-side tracking. Instead of the browser sending event data straight to Meta, Google Ads or GA4, the data first goes to a server you control, which forwards it to those tools. With server-side tracking, fewer events go missing along the way.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Deciding to implement it is the easy part. The difficulty starts when you have to justify the investment to whoever approves next quarter&#8217;s budget. Saying that your company needs server-side tracking means asking for another subscription and a technical project that needs resources. Without making a business case, most people in the room cannot evaluate if the investment is worth it. But if you put a figure on the conversions you\u2019re losing, the story becomes clearer.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In this article, we will explain how you can build that case. You\u2019ll see how to calculate the number of conversions your ad platforms are missing and what share of your budget is spent on incomplete data, learn how to answer questions from finance, marketing, IT and legal, and find out how to test server-side tracking alongside your current setup before committing to a full migration.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Why the technical argument isn&#8217;t enough<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">With server-side tracking, ad blockers stop fewer requests, cookies survive longer, and pages load faster because fewer third-party scripts run in the browser. Each of those statements is true. However, each one also describes how the tracking setup behaves, without saying what the company earns or saves as a result. The person deciding on the budget sees a new cost and no figure to weigh it against.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Two arguments work better.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The first is that missing conversions cost you money immediately, not just at reporting time. Google Ads and Meta decide where to spend by learning from the conversions you send them. A purchase that never reaches the platform is recorded as a visitor who did not buy, so the platform shifts budget away from the audience that actually produced the sale. Every day the data stays incomplete, spending decisions are made against a distorted picture of who converts.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The second is that your CFO is comparing server-side tracking against the same money spent on ads, whether or not anyone says so out loud. That comparison needs a number on both sides. Explaining how the technology works gives them nothing to weigh, while the count of missing conversions and the share of spend allocated without them does.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Before running any calculation, check for signal loss, meaning the difference between the conversions that actually happened and the conversions recorded by your ad platform. It\u2019s hard to spot it directly in your reports, but it shows up as inconsistencies between systems. Start by checking for these four things:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Your CRM or online store records more orders than the ad platform reports for the same period.<\/li>\n\n\n\n<li>ROAS drops while budget, bids and creative stay the same.<\/li>\n\n\n\n<li>The share of GA4 traffic that arrives without an identifiable source keeps growing.<\/li>\n\n\n\n<li>Retargeting audiences get smaller, because visitors that the browser didn\u2019t record were never added to them.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Measuring the gap<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The calculation below turns that discrepancy into two figures you can bring to a budget conversation. The first is how many conversions your platforms never received, and the second is how much spend was allocated without them. You need five numbers, and the first four should cover the same 30-day window so the comparison is like for like.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Conversions in your own system, meaning your shop, order system or CRM, which is your record of actual purchases that were made<\/li>\n\n\n\n<li>Conversions reported by the ad platform taken from Google Ads or Meta<\/li>\n\n\n\n<li>Ad spend for that period<\/li>\n\n\n\n<li>Average order or lead value<\/li>\n\n\n\n<li>Consent rate from your consent management platform<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">The figures below come from a worked example in TAGGRS&#8217;s documentation. Run the same steps with your own numbers.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Step 1. Missing conversions.<\/strong> Subtract platform-reported conversions from the conversions in your own system. A store with 500 orders in its order system and 380 conversions reported by the ad platform is missing 120 per month.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Step 2. Signal loss percentage.<\/strong> Divide the missing conversions by your own total. Here, 120 divided by 500 gives 24%, meaning the platform saw roughly three quarters of what happened.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Step 3. The consent ceiling.<\/strong> Some of that 24% can\u2019t be recovered. Visitors who decline cookies cannot be tracked by any setup, server-side or not, so your consent rate limits what you\u2019ll be able to measure. Multiply your own conversion total by that rate to find the consent ceiling. Using the example above, assume a consent rate of 90%. Its ceiling is 450 orders, so of the 120 missing conversions, 70 were lost for technical reasons and 50 were never available to measure in the first place.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Server-side tracking recovers the 70. A better cookie banner can raise the consent rate and move the ceiling above 450, but neither reaches the people who declined, so bring the 70 to your stakeholders rather than the 120.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Two reference points from TAGGRS&#8217;s data tell you whether the gap you calculated is a real problem. A gap of 5% to 8% comes from ad platforms and your own system counting conversions over different time windows, so it needs no action. A gap above 10% that stays there month after month is signal loss. Calculate it for each platform separately, because Meta typically loses more than Google Ads. Meta relies more heavily on browser pixels, which leaves it more exposed to ad blockers and to Intelligent Tracking Prevention, the Safari feature that limits how long tracking cookies survive.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Step 4. Conversion value missing from the model.<\/strong> Multiply missing conversions by average order value. At \u20ac150 per order, those 120 conversions represent \u20ac18,000 a month in revenue the business already earned that the ad platforms never received. This is not lost revenue, since the sales really happened. It is revenue the platforms could not use to decide where to spend.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Step 5. Ad spend allocated on incomplete data.<\/strong> Multiply monthly spend by the signal loss percentage. On \u20ac30,000 of spend at 24% signal loss, that comes to \u20ac7,200 a month. Consent-related and technical losses both count here, because the platform is missing the data either way.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Be specific about what this number means \u2013 it\u2019s not \u20ac7,200 of proven waste. It is the amount of spend whose targeting decisions were made while a quarter of the conversion data was missing. Some of that budget still went to the right campaigns. Nobody can say how much, and that uncertainty is the argument for fixing it.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Step 6. Compare against the cost.<\/strong> Hosting through TAGGRS runs under \u20ac200 a month for most setups. When compared against the \u20ac7,200 being allocated without complete data, the decision on the table is whether to spend under 3% of the affected amount to complete the data behind it.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Recovering that data improves two things:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Conversions you already made start appearing in the platform, so campaigns that were being under-credited get the sales they produced and budget shifts toward what\u2019s effective.<\/li>\n\n\n\n<li>As a result, ad platforms receive more complete data and bid differently. This is where efficiency gains come from, and they take longer to appear. TAGGRS sees measured conversion volume rise within the first 30 days, with CPA and ROAS changes usually following within three months.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Below roughly \u20ac2,000 a month in paid media, the spend affected by signal loss is too small for the recovery to cover the hosting cost. In that situation, build your case around compliance and data control instead.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Once server-side tracking is live, the TAGGRS dashboard reports several of these numbers for you. It shows your consent rate, how many events ad blockers and browser tracking prevention are blocking, and the volume of each event type you send. You can then repeat the calculation each month instead of treating it as a one-off exercise.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The process above is described in more detail in <a href=\"https:\/\/taggrs.io\/calculate-server-side-tracking-roi\/\">TAGGRS&#8217;s ROI guide<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>What each stakeholder asks<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Getting approval usually means having to convince several people who don\u2019t respond to the same arguments. The table below sets out what each of them tends to ask and how you should address their concerns.<br><\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><tbody><tr><td><strong>Stakeholder<\/strong><\/td><td><strong>What they ask<\/strong><\/td><td><strong>What to answer<\/strong><\/td><td><strong>What convinces them<\/strong><\/td><\/tr><tr><td>CFO \/ Finance<\/td><td>Why another subscription?<\/td><td>The hosting cost is small next to the spend currently being allocated on incomplete data<\/td><td>Your own numbers based on the calculation above from the last 30 days<\/td><\/tr><tr><td>CMO \/ Marketing lead<\/td><td>Which of our channels are actually working?<\/td><td>Platforms lose different amounts of data, so the channel that looks weakest may be the one losing the most<\/td><td>Signal loss worked out per platform instead of one combined figure<\/td><\/tr><tr><td>Performance marketer<\/td><td>Will this disrupt live campaigns?<\/td><td>The new setup runs alongside the old one and only takes over once the numbers check out<\/td><td>Event Match Quality before and after, and conversion volume during the parallel run<\/td><\/tr><tr><td>IT \/ Development<\/td><td>How much work does it require and who will maintain it?<\/td><td>A subdomain and a DNS record, with hosting and scaling handled by the provider. Most of the effort goes into the data layer<\/td><td>A written scope and a page-speed measurement before and after<\/td><\/tr><tr><td>DPO \/ Legal<\/td><td>Where will our data end up?<\/td><td>You control which fields leave your systems and which country processes them<\/td><td>The server location, a record of where data flows, and the processor agreement listing sub-processors<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Event Match Quality is Meta&#8217;s score for how well the customer details you send match its own records. It improves as server-side events carry more complete data.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">One word of warning regarding the CMO row: work per platform rather than per channel, because splitting your own orders by channel needs the tracking data that is missing. Do not add the platform figures together, since two platforms often claim the same order.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>How to test it before committing<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A test is easier to get approved than a migration, because nothing is irreversible until you switch over. The sequence below takes 60 days. Server-side data only becomes comparable to your old numbers once it has run for a full clean month, which is why you need to wait so long for the final measurement.<br><\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Baseline<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Record the five numbers per platform before changing anything, because you cannot show improvement without a starting point. Add the Meta Event Match Quality score and the share of GA4 traffic that arrives without an identifiable source. Neither belongs in the calculation, but your performance marketer and CMO will ask for both. <a href=\"https:\/\/taggrs.io\/website-tracking-checker\/\">Run a free tracking audit<\/a> alongside that to establish which platforms currently deliver data client-side or server-side, how long each cookie survives, and whether any scripts fire before consent.<br><\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Parallel run<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Server-side runs alongside your existing client-side setup, so no campaign depends on the new setup while you are still validating it. Configure deduplication before you start. Deduplication matches the browser event and the server event that describe the same conversion so the platform counts it once. Without it, platforms count the same purchase twice and inflate reported ROAS, which makes every number you present afterwards easy to dismiss. Clearly state that data collected server-side usually includes fewer conversions during the first two weeks, since it has no historical data yet.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">First read<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Once the parallel run clears those first weeks, compare how many events each path delivered per platform, then check whether Event Match Quality has changed and what happened to page speed. The gap between the two paths shows how many events the server carried that the browser lost, which is your first proof that the setup works.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Switch<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Set server-side conversions as primary and client-side to secondary, so platforms optimize on the more complete data. Report the gap in delivered events as an interim result while the longer measurement runs.<br><\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Re-measure at 30 and 60 days<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Run the calculation from earlier again, now on clean server-side data. Comparing the result against your baseline gives you the before and after that closes the business case.<br><\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Privacy<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Your DPO or legal counsel may well be the stakeholder with the strongest opinion. The ePrivacy Directive and the GDPR set cookie consent requirements in the EU, and regulators are enforcing them more actively. In the Netherlands, the Autoriteit Persoonsgegevens has monitored cookie use more strictly since 2024, and its first cookie fine was \u20ac600,000, issued to the company behind Kruidvat for using tracking cookies without valid consent.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Server-side tracking changes three things that matter when it comes to <a href=\"https:\/\/thedatastory.nl\/en\/data-stories\/3-ways-to-ensure-privacy-in-server-side-google-tag-manager\/\">meeting privacy requirements<\/a>. Fields can be filtered, hashed or removed on your own server before anything reaches Meta or Google. This lets you decide what data leaves your systems rather than sending a full browser payload and trusting the recipient&#8217;s settings. You choose where the processing happens, which matters because data held by US providers can be reached by US authorities under the CLOUD Act regardless of where the servers sit. On top of that, you can document exactly where your client data ends up, which is difficult with a client-side setup where a dozen scripts send data from the browser to their own destinations.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Server-side tracking does not work around consent. Consent still determines whether you are able to track users and what data you can collect, and server-side tags have to respect consent signals like any others. What changes is how much personal data leaves your control once consent has been given.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Key capabilities worth knowing about<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Closing the measurement gap is a starting point. Once your events run through a server you control, that server can handle jobs you are currently paying other tools to do.<br><\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img fetchpriority=\"high\" decoding=\"async\" width=\"588\" height=\"391\" src=\"https:\/\/thedatastory.nl\/wp-content\/uploads\/2026\/08\/unnamed-19-1.jpg\" alt=\"\" class=\"wp-image-3838\" srcset=\"https:\/\/thedatastory.nl\/wp-content\/uploads\/2026\/08\/unnamed-19-1.jpg 588w, https:\/\/thedatastory.nl\/wp-content\/uploads\/2026\/08\/unnamed-19-1-18x12.png 18w, https:\/\/thedatastory.nl\/wp-content\/uploads\/2026\/08\/unnamed-19-1-300x199.png 300w\" sizes=\"(max-width: 588px) 100vw, 588px\" \/><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\">Google Ads offline conversions<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Webhooks from a CRM or backend send confirmed results to Google Ads, so bidding works from closed revenue rather than from form submissions that may never turn into customers. These events are often not actually offline anymore. The tag is commonly used as a server-to-server conversion path that does not depend on cookies, ad blockers or JavaScript execution. Google Ads authorization runs through the platform connection, which removes the manual service-account setup and credential management, and removes the need for a dedicated offline conversion tool. The same setup applies when <a href=\"https:\/\/thedatastory.nl\/en\/data-stories\/ga4-measurement-protocol-sending-server-side-events-with-webhooks\/\">sending server-side events with webhooks<\/a> using GA4.<br><\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Infrastructure settings<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Cookie recovery for iOS ITP and click ID recovery both affect how many conversions can be attributed. The Enhanced Tracking Script keeps data flowing where ad blockers would otherwise stop it and filters bot traffic on the server before it reaches your reports. A server-side CDN serves your tracking script from infrastructure closer to the visitor, which shortens load time.<br><\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Profit tracking<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">You can route profit data, meaning revenue minus product and shipping costs, through the same server so Google Ads and GA4 optimize on margin instead of turnover. That stops the algorithm from chasing high-revenue products you barely make money on. It runs on infrastructure you already pay for and can replace a separate profit-tracking tool.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Most marketing teams accumulate single-purpose tools over time, each carrying its own subscription and integration. Once the server handles those jobs, some of those tools become redundant. That gives the CFO a second argument alongside better data, which is a shorter list of subscriptions, and it leaves marketing with fewer systems they need to use for work.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Where to start<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The gap between knowing that server-side tracking works and getting it approved can be closed with two numbers. The first is how much of your ad spend is currently being allocated on incomplete data. The second is what changed while client-side and server-side ran in parallel.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Both come from your own account, and the first one you can calculate yourself. Pull conversions from your own system, platform-reported conversions, spend and the average order value for the last 30 days, work through the steps above, and check the result against your consent rate. If the gap holds above 10% month over month, you can start building your business case for server-side tracking.<\/p>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>","protected":false},"excerpt":{"rendered":"<p>Compare your ad platform reports against your own order data and the numbers rarely match. Meta reports fewer purchases than recorded by your online store or CRM, GA4 gives you [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":3837,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_price":"","_stock":"","_tribe_ticket_header":"","_tribe_default_ticket_provider":"","_tribe_ticket_capacity":"0","_ticket_start_date":"","_ticket_end_date":"","_tribe_ticket_show_description":"","_tribe_ticket_show_not_going":false,"_tribe_ticket_use_global_stock":"","_tribe_ticket_global_stock_level":"","_global_stock_mode":"","_global_stock_cap":"","_tribe_rsvp_for_event":"","_tribe_ticket_going_count":"","_tribe_ticket_not_going_count":"","_tribe_tickets_list":"[]","_tribe_ticket_has_attendee_info_fields":false,"footnotes":""},"categories":[2],"tags":[],"class_list":["post-3836","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-data-stories"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v28.3 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>The real value of server-side tracking: Building the business case - The Data Story<\/title>\n<meta name=\"description\" content=\"Ad blockers and browser limits ruining your ROAS? Learn how to measure the gap between your CRM and ad platforms, align stakeholders, and fix missing conversion data using server-side tracking.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/thedatastory.nl\/en\/data-stories\/the-real-value-of-server-side-tracking-building-the-business-case\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"The real value of server-side tracking: Building the business case - The Data Story\" \/>\n<meta property=\"og:description\" content=\"Ad blockers and browser limits ruining your ROAS? Learn how to measure the gap between your CRM and ad platforms, align stakeholders, and fix missing conversion data using server-side tracking.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/thedatastory.nl\/en\/data-stories\/the-real-value-of-server-side-tracking-building-the-business-case\/\" \/>\n<meta property=\"og:site_name\" content=\"The Data Story\" \/>\n<meta property=\"article:published_time\" content=\"2026-08-26T11:04:14+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-08-26T11:18:41+00:00\" \/>\n<meta property=\"og:image\" content=\"http:\/\/thedatastory.nl\/wp-content\/uploads\/2026\/08\/unnamed-19.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"588\" \/>\n\t<meta property=\"og:image:height\" content=\"391\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"The Data Story\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"The Data Story\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"14 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/thedatastory.nl\\\/nl\\\/data-stories\\\/the-real-value-of-server-side-tracking-building-the-business-case\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/thedatastory.nl\\\/nl\\\/data-stories\\\/the-real-value-of-server-side-tracking-building-the-business-case\\\/\"},\"author\":{\"name\":\"The Data Story\",\"@id\":\"https:\\\/\\\/thedatastory.nl\\\/en\\\/#\\\/schema\\\/person\\\/e218295bc2730947de16723cb69d18f3\"},\"headline\":\"The real value of server-side tracking: Building the business case\",\"datePublished\":\"2026-08-26T11:04:14+00:00\",\"dateModified\":\"2026-08-26T11:18:41+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/thedatastory.nl\\\/nl\\\/data-stories\\\/the-real-value-of-server-side-tracking-building-the-business-case\\\/\"},\"wordCount\":2733,\"publisher\":{\"@id\":\"https:\\\/\\\/thedatastory.nl\\\/en\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/thedatastory.nl\\\/nl\\\/data-stories\\\/the-real-value-of-server-side-tracking-building-the-business-case\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/thedatastory.nl\\\/wp-content\\\/uploads\\\/2026\\\/08\\\/unnamed-19.jpg\",\"articleSection\":[\"Data stories\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/thedatastory.nl\\\/nl\\\/data-stories\\\/the-real-value-of-server-side-tracking-building-the-business-case\\\/\",\"url\":\"https:\\\/\\\/thedatastory.nl\\\/nl\\\/data-stories\\\/the-real-value-of-server-side-tracking-building-the-business-case\\\/\",\"name\":\"The real value of server-side tracking: Building the business case - The Data Story\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/thedatastory.nl\\\/en\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/thedatastory.nl\\\/nl\\\/data-stories\\\/the-real-value-of-server-side-tracking-building-the-business-case\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/thedatastory.nl\\\/nl\\\/data-stories\\\/the-real-value-of-server-side-tracking-building-the-business-case\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/thedatastory.nl\\\/wp-content\\\/uploads\\\/2026\\\/08\\\/unnamed-19.jpg\",\"datePublished\":\"2026-08-26T11:04:14+00:00\",\"dateModified\":\"2026-08-26T11:18:41+00:00\",\"description\":\"Ad blockers and browser limits ruining your ROAS? Learn how to measure the gap between your CRM and ad platforms, align stakeholders, and fix missing conversion data using server-side tracking.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/thedatastory.nl\\\/nl\\\/data-stories\\\/the-real-value-of-server-side-tracking-building-the-business-case\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/thedatastory.nl\\\/nl\\\/data-stories\\\/the-real-value-of-server-side-tracking-building-the-business-case\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/thedatastory.nl\\\/nl\\\/data-stories\\\/the-real-value-of-server-side-tracking-building-the-business-case\\\/#primaryimage\",\"url\":\"https:\\\/\\\/thedatastory.nl\\\/wp-content\\\/uploads\\\/2026\\\/08\\\/unnamed-19.jpg\",\"contentUrl\":\"https:\\\/\\\/thedatastory.nl\\\/wp-content\\\/uploads\\\/2026\\\/08\\\/unnamed-19.jpg\",\"width\":588,\"height\":391},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/thedatastory.nl\\\/nl\\\/data-stories\\\/the-real-value-of-server-side-tracking-building-the-business-case\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/thedatastory.nl\\\/en\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Data stories\",\"item\":\"https:\\\/\\\/thedatastory.nl\\\/en\\\/data-stories\\\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"The real value of server-side tracking: Building the business case\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/thedatastory.nl\\\/en\\\/#website\",\"url\":\"https:\\\/\\\/thedatastory.nl\\\/en\\\/\",\"name\":\"The Data Story\",\"description\":\"Data Analyse, Visualisatie &amp; Automation\",\"publisher\":{\"@id\":\"https:\\\/\\\/thedatastory.nl\\\/en\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/thedatastory.nl\\\/en\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/thedatastory.nl\\\/en\\\/#organization\",\"name\":\"The Data Story\",\"url\":\"https:\\\/\\\/thedatastory.nl\\\/en\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/thedatastory.nl\\\/en\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/thedatastory.nl\\\/wp-content\\\/uploads\\\/2021\\\/11\\\/Logo-negatief.svg\",\"contentUrl\":\"https:\\\/\\\/thedatastory.nl\\\/wp-content\\\/uploads\\\/2021\\\/11\\\/Logo-negatief.svg\",\"width\":250,\"height\":49,\"caption\":\"The Data Story\"},\"image\":{\"@id\":\"https:\\\/\\\/thedatastory.nl\\\/en\\\/#\\\/schema\\\/logo\\\/image\\\/\"}},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/thedatastory.nl\\\/en\\\/#\\\/schema\\\/person\\\/e218295bc2730947de16723cb69d18f3\",\"name\":\"The Data Story\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/3b7086714fe59d0954156d3cedeeaf914f3630d097c0c9587f9fb4793ce63818?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/3b7086714fe59d0954156d3cedeeaf914f3630d097c0c9587f9fb4793ce63818?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/3b7086714fe59d0954156d3cedeeaf914f3630d097c0c9587f9fb4793ce63818?s=96&d=mm&r=g\",\"caption\":\"The Data Story\"},\"url\":\"https:\\\/\\\/thedatastory.nl\\\/en\\\/author\\\/the-data-story\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"The real value of server-side tracking: Building the business case - The Data Story","description":"Ad blockers and browser limits ruining your ROAS? Learn how to measure the gap between your CRM and ad platforms, align stakeholders, and fix missing conversion data using server-side tracking.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/thedatastory.nl\/en\/data-stories\/the-real-value-of-server-side-tracking-building-the-business-case\/","og_locale":"en_US","og_type":"article","og_title":"The real value of server-side tracking: Building the business case - The Data Story","og_description":"Ad blockers and browser limits ruining your ROAS? Learn how to measure the gap between your CRM and ad platforms, align stakeholders, and fix missing conversion data using server-side tracking.","og_url":"https:\/\/thedatastory.nl\/en\/data-stories\/the-real-value-of-server-side-tracking-building-the-business-case\/","og_site_name":"The Data Story","article_published_time":"2026-08-26T11:04:14+00:00","article_modified_time":"2026-08-26T11:18:41+00:00","og_image":[{"width":588,"height":391,"url":"http:\/\/thedatastory.nl\/wp-content\/uploads\/2026\/08\/unnamed-19.jpg","type":"image\/jpeg"}],"author":"The Data Story","twitter_card":"summary_large_image","twitter_misc":{"Written by":"The Data Story","Est. reading time":"14 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/thedatastory.nl\/nl\/data-stories\/the-real-value-of-server-side-tracking-building-the-business-case\/#article","isPartOf":{"@id":"https:\/\/thedatastory.nl\/nl\/data-stories\/the-real-value-of-server-side-tracking-building-the-business-case\/"},"author":{"name":"The Data Story","@id":"https:\/\/thedatastory.nl\/en\/#\/schema\/person\/e218295bc2730947de16723cb69d18f3"},"headline":"The real value of server-side tracking: Building the business case","datePublished":"2026-08-26T11:04:14+00:00","dateModified":"2026-08-26T11:18:41+00:00","mainEntityOfPage":{"@id":"https:\/\/thedatastory.nl\/nl\/data-stories\/the-real-value-of-server-side-tracking-building-the-business-case\/"},"wordCount":2733,"publisher":{"@id":"https:\/\/thedatastory.nl\/en\/#organization"},"image":{"@id":"https:\/\/thedatastory.nl\/nl\/data-stories\/the-real-value-of-server-side-tracking-building-the-business-case\/#primaryimage"},"thumbnailUrl":"https:\/\/thedatastory.nl\/wp-content\/uploads\/2026\/08\/unnamed-19.jpg","articleSection":["Data stories"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/thedatastory.nl\/nl\/data-stories\/the-real-value-of-server-side-tracking-building-the-business-case\/","url":"https:\/\/thedatastory.nl\/nl\/data-stories\/the-real-value-of-server-side-tracking-building-the-business-case\/","name":"The real value of server-side tracking: Building the business case - The Data Story","isPartOf":{"@id":"https:\/\/thedatastory.nl\/en\/#website"},"primaryImageOfPage":{"@id":"https:\/\/thedatastory.nl\/nl\/data-stories\/the-real-value-of-server-side-tracking-building-the-business-case\/#primaryimage"},"image":{"@id":"https:\/\/thedatastory.nl\/nl\/data-stories\/the-real-value-of-server-side-tracking-building-the-business-case\/#primaryimage"},"thumbnailUrl":"https:\/\/thedatastory.nl\/wp-content\/uploads\/2026\/08\/unnamed-19.jpg","datePublished":"2026-08-26T11:04:14+00:00","dateModified":"2026-08-26T11:18:41+00:00","description":"Ad blockers and browser limits ruining your ROAS? Learn how to measure the gap between your CRM and ad platforms, align stakeholders, and fix missing conversion data using server-side tracking.","breadcrumb":{"@id":"https:\/\/thedatastory.nl\/nl\/data-stories\/the-real-value-of-server-side-tracking-building-the-business-case\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/thedatastory.nl\/nl\/data-stories\/the-real-value-of-server-side-tracking-building-the-business-case\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/thedatastory.nl\/nl\/data-stories\/the-real-value-of-server-side-tracking-building-the-business-case\/#primaryimage","url":"https:\/\/thedatastory.nl\/wp-content\/uploads\/2026\/08\/unnamed-19.jpg","contentUrl":"https:\/\/thedatastory.nl\/wp-content\/uploads\/2026\/08\/unnamed-19.jpg","width":588,"height":391},{"@type":"BreadcrumbList","@id":"https:\/\/thedatastory.nl\/nl\/data-stories\/the-real-value-of-server-side-tracking-building-the-business-case\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/thedatastory.nl\/en\/"},{"@type":"ListItem","position":2,"name":"Data stories","item":"https:\/\/thedatastory.nl\/en\/data-stories\/"},{"@type":"ListItem","position":3,"name":"The real value of server-side tracking: Building the business case"}]},{"@type":"WebSite","@id":"https:\/\/thedatastory.nl\/en\/#website","url":"https:\/\/thedatastory.nl\/en\/","name":"The Data Story","description":"Data Analyse, Visualisatie &amp; Automation","publisher":{"@id":"https:\/\/thedatastory.nl\/en\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/thedatastory.nl\/en\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/thedatastory.nl\/en\/#organization","name":"The Data Story","url":"https:\/\/thedatastory.nl\/en\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/thedatastory.nl\/en\/#\/schema\/logo\/image\/","url":"https:\/\/thedatastory.nl\/wp-content\/uploads\/2021\/11\/Logo-negatief.svg","contentUrl":"https:\/\/thedatastory.nl\/wp-content\/uploads\/2021\/11\/Logo-negatief.svg","width":250,"height":49,"caption":"The Data Story"},"image":{"@id":"https:\/\/thedatastory.nl\/en\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"https:\/\/thedatastory.nl\/en\/#\/schema\/person\/e218295bc2730947de16723cb69d18f3","name":"The Data Story","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/3b7086714fe59d0954156d3cedeeaf914f3630d097c0c9587f9fb4793ce63818?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/3b7086714fe59d0954156d3cedeeaf914f3630d097c0c9587f9fb4793ce63818?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/3b7086714fe59d0954156d3cedeeaf914f3630d097c0c9587f9fb4793ce63818?s=96&d=mm&r=g","caption":"The Data Story"},"url":"https:\/\/thedatastory.nl\/en\/author\/the-data-story\/"}]}},"_links":{"self":[{"href":"https:\/\/thedatastory.nl\/en\/wp-json\/wp\/v2\/posts\/3836","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/thedatastory.nl\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/thedatastory.nl\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/thedatastory.nl\/en\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/thedatastory.nl\/en\/wp-json\/wp\/v2\/comments?post=3836"}],"version-history":[{"count":5,"href":"https:\/\/thedatastory.nl\/en\/wp-json\/wp\/v2\/posts\/3836\/revisions"}],"predecessor-version":[{"id":3844,"href":"https:\/\/thedatastory.nl\/en\/wp-json\/wp\/v2\/posts\/3836\/revisions\/3844"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/thedatastory.nl\/en\/wp-json\/wp\/v2\/media\/3837"}],"wp:attachment":[{"href":"https:\/\/thedatastory.nl\/en\/wp-json\/wp\/v2\/media?parent=3836"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/thedatastory.nl\/en\/wp-json\/wp\/v2\/categories?post=3836"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/thedatastory.nl\/en\/wp-json\/wp\/v2\/tags?post=3836"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}