--- title: "What Is Server-Side Conversion Tracking? How the Conversion API Works, Why Browser-Based Tracking Loses Data, Cookie Consent, Event Selection, Setup Steps, Lost Conversion Estimate and Setup Audit" description: "What is server-side conversion tracking? How the Conversions API works, data loss in browser-based tracking, cookie consent, setup steps, lost conversion estimate." url: https://www.faprika.com/en/blog/what-is-server-side-conversion-tracking language: en site: Faprika --- # What Is Server-Side Conversion Tracking? How the Conversion API Works, Why Browser-Based Tracking Loses Data, Cookie Consent, Event Selection, Setup Steps, Lost Conversion Estimate and Setup Audit > What is server-side conversion tracking? How the Conversions API works, data loss in browser-based tracking, cookie consent, setup steps, lost conversion estimate. A common oddity in ad management: your store panel shows twenty orders in a day, while the ad platform's report counts fifteen conversions. Those five orders really happened and the money reached your account, but the ad system could not link them to your ad. The problem often lies not in the ad but in the measurement: the purchase information leaves the customer's browser and gets lost on the way. This guide answers, in order, what **server-side conversion tracking** is, how the Conversions API sends events, why browser-based tracking loses data and how cookie consent fits into the picture. You will also find the setup steps in the Faprika panel, a lost conversion estimate calculator and a checklist you can use to verify your setup. We do not give a fixed loss percentage: this rate varies from store to store and is measured with your own data. Key Takeaway “Browser-based tracking relies on a single path, and that path can narrow because of cookies, blockers and phone OS versions. Server-side tracking also sends the same event from the store's own server and fills in the missing record. The goal is not to invent more conversions, but not to lose the conversions that actually happened.” ## What Is Server-Side Conversion Tracking? Server-side conversion tracking means that events such as add-to-cart and purchase are sent to the ad platform not only from the visitor's browser but also from the store's own server. The interface this method uses is generally called the Conversions API. On the classic path, a small piece of code (the pixel) is placed on the store page. When the customer reaches the purchase page, this code sends a “a purchase happened” message from the browser to the ad platform. On the server-side path, the same information is also sent directly to the platform by the store system when the order is completed. Whatever the customer's browser does, the record on the server stays in place. The table below puts the two approaches side by side and summarizes the difference. | Feature | Browser-based tracking only | Server-side tracking | Both together | | --- | --- | --- | --- | | Where does the event come from? | From the customer's browser | From the store server | From both the browser and the server | | Dependence on cookies | High | Lower | The browser side stays tied to cookies | | Effect of blockers | Affected | Proceeds independently of browser settings | The missing record is completed from the server | | Setup effort | Low | ID and token setup required | One-time extra setup | | Recommended use | Carries a risk of loss on its own | Usually not set up on its own | The setup ad platforms recommend | *Görsel: Server-side conversion tracking illustration: comparison of browser-only tracking with the Conversions API path sent from both browser and server (Browser only versus browser and server together)* Okumanızı öneririz Reklam Analitiği: İnternet Reklamlarınızın Etkisini Nasıl Ölçersiniz? ## Why Does Browser-Based Tracking Lose Data? Browser-based tracking depends on cookies and on the browser allowing the tracking code to run, so it loses data wherever these permissions narrow. The loss is not a malfunction; it is the natural result of decisions made on the browser side. The pixel uses cookies to recognize the visitor and link a conversion to an ad click. When this link breaks, the platform may see the purchase but cannot say which ad it came from, or may not see it at all. The main causes are: - **Cookies deleted or declined:** The visitor can clear cookies or decline them in the consent window. In this case the record in the browser starts out incomplete. - **Tracking blockers:** Some browser extensions and settings block tracking codes from running; the pixel may never fire. - **Phone operating system versions:** In some versions of the phone operating system, data transmission through the browser is restricted and pixel data is left incomplete. Faprika's Conversions API tutorial also notes that the pixel, which sends data through the browser, causes data loss in these versions. - **Page closed too early:** If the customer closes the tab after payment without reaching the thank-you page, the event in the browser may never be sent. The server, however, already knows about the order record. | Reason | What happens? | What does server-side tracking provide? | | --- | --- | --- | | Cookie deletion or refusal | Conversion cannot be linked to the ad click | The event is also sent from the order record through the server | | Tracking blocker | Pixel does not run, event is never sent | Sends a record independent of browser settings | | Phone version restriction | Some events do not reach the platform | The missing event is completed through the server path | | Page closed too early | Purchase event is not triggered | The server sends the event when the order is completed | Tip Don't estimate the loss, compare it See the loss rate with your own store's data, not with a number you found online. For one week, write the order count in the store panel next to the conversions reported by the ad platform. The gap is not only measurement loss (reporting time and attribution rules also play a part), but it gives you the order of magnitude. ## How Does Data Loss Affect Ad Performance? Missing conversion data makes ad reports look worse than reality and makes it harder for the ad platform to learn which audience buys. The result is wrong decisions and wasted budget. The effect shows up in three places: - **Reporting:** Part of the completed sales is not credited to the ad. A campaign that is working profitably looks weak in the report and is needlessly cut back or stopped. - **Optimization:** Ad platforms learn from conversion events. The more complete the events are, the better they can tune the target audience and delivery; missing events mean insufficient signal for learning. - **Remarketing:** If intermediate events such as add-to-cart are lost, the audiences of interested visitors shrink. This is why fixing measurement is one of the cheapest jobs to do before increasing the ad budget. You can find how conversion rate and measurement quality are linked in the article [Dönüşüm Oranı Optimizasyonu (CRO) Nedir?](https://www.faprika.com/blog/donusum-orani-optimizasyonu-cro-nedir) and which indicators to monitor in the guide [E-Commerce Metrics: The 15 KPIs You Need to Track and Their Calculation Formulas](https://www.faprika.com/en/blog/e-commerce-metrics) . Okumanızı öneririz Dönüşüm Oranı Optimizasyonu (CRO) Nedir? ## How Does the Conversions API Work? The Conversions API is a connection that sends an event in the store system (such as add-to-cart or purchase) from server to server to the ad platform's events manager. Even if the browser code does not run, the event is sent because the record exists in the order system. The flow can be summarized in four steps: the customer completes the purchase, the pixel in the browser reports the event, the store server reports the same event through its own path, and the platform records the event in the events manager. If the records from the two paths match, they are treated as a single event; if one is missing, the other record stands in for it. *Görsel: Conversions API event flow: purchase, browser report, server report and record in the events manager (The path of a purchase event from the browser and the server to the platform)* ### Which Events Are Sent? You choose the events: when setting up the Conversions API in the ad platform's events manager, the events you want to track are checked. The two most commonly used examples are add-to-cart and purchase. | Event | When does it occur? | Why is it tracked? | | --- | --- | --- | | Add to cart | When the customer adds a product to the cart | To see interested visitors and remarketing audiences | | Purchase | When the order is completed | To measure the real result of the ad and the optimization signal | The list of other selectable events varies by platform; rather than turning on events you do not need, it is healthier to send completely the few events that will support your decisions. ### What Happens If the Same Event Arrives Through Two Paths? When an event is sent from both the browser and the server, the platform must understand that the two records belong to a single purchase; otherwise the same sale may be counted twice. How duplicate events are merged is the ad platform's rule and is verified during setup according to the platform's guidelines. After setup, check in the events manager which sources the event comes from and whether there is an unexpected jump in numbers. If the numbers are clearly higher than your order count, consider that there may be double counting in the setup and review the setting. Tip Keep the information you send simple Only the information that tracking requires should go to the platform through the Conversions API. Thinking “the more information, the better the match” both increases your data protection obligations and complicates your privacy notice. ## How Do Cookie Consent and Data Protection Law Affect Server-Side Tracking? Server-side tracking does not remove cookie consent and personal data protection obligations; the visitor's choices must also be reflected in the tracking setup. The only difference of the method is the path the data takes; the question of which data you process on what basis applies in full. Pay attention to three points: - **Choices must be respected:** If the visitor declined tracking, this choice must be reflected in both browser and server tracking. The assumption “it is fine because it goes from the server” is wrong. - **The privacy notice must be up to date:** Your privacy and cookie text should explain that data is shared for ad measurement. - **The legal assessment is yours:** Which data can be processed on what basis is your business's decision; where you are unsure, consult your legal adviser. You can get information about Faprika's cookie consent window and cookie management solution [Cookie Management](https://www.faprika.com/en/cookie-management) page; some features vary by plan. The full subject of privacy notices, explicit consent and cookies is covered in practice in the article [How to Achieve KVKK Compliance for an E-Commerce Site? Disclosure Notice, Explicit Consent, Cookies, İYS and Rights Requests: A Practical Guide](https://www.faprika.com/en/blog/kvkk-compliance) The article [Çerezler E-Ticaret Sitenizin Sağlığı İçin İyi mi Kötü mü?](https://www.faprika.com/blog/cerezler-e-ticaret-sitenizin-sagligi-icin-iyi-mi-kotu-mu) is also useful for the general impact of cookies. Recommended reading How to Ensure KVKK Compliance for an E-commerce Site? A Practical Guide to Privacy Notices, Explicit Consent, Cookies, IYS and Data Subject Requests ## How Do You Set Up the Conversions API in Faprika? Setup in Faprika is done in two places: a dataset ID and an access token are created in the ad platform's events manager, and then these two pieces of information are entered in the pixel field under Add-ons in the Faprika panel. You do not need to write any code. | Step | Where? | What is done? | | --- | --- | --- | | 1 | Ad platform, events manager | Start the Conversions API with the manual setup option | | 2 | Events manager | Select the events you want to track (e.g. add to cart, purchase) | | 3 | Events Manager, settings | Copy the dataset ID | | 4 | Events Manager, settings | Generate and copy an access token | | 5 | Faprika panel, Add-ons, pixel section | Paste the dataset ID into the pixel ID field and the token into the Conversions API ID field | | 6 | Faprika panel | Tick the “Active” box and click Save | *Görsel: Illustration of the Conversions API setup in the Faprika panel: pixel ID field, Conversions API ID field and Active box (Two fields and one checkbox in the panel)* A full walkthrough with screenshots is in the [Conversions API setup guide](https://www.faprika.com/en/tutorials/facebook-conversion-api-setup). An access token works like a password: paste it only into the panel, never share it by email or message, and never show it to anyone. ### Analytics and Product Feed Integrations In Faprika, the search engine's analytics integration and product feed (shopping catalog) integration come ready in the plans. Analytics covers visitor behavior, while the product feed gets your products listed in search results; they are two separate tools that complete ad measurement. You can find the analytics setup in the [analytics setup guide](https://www.faprika.com/en/tutorials/google-analytics-4) and on the [integration add-on page](https://www.faprika.com/en/add-ons/google-analytics-4). To see which integration is in which plan, check the [e-commerce plan](https://www.faprika.com/en/pricing) comparison. We recommend reading E-Commerce Metrics: 15 KPIs You Need to Track and Their Calculation Formulas ## How Is Lost Conversion Estimated? The calculator below shows how much of your monthly purchase count may not appear in browser-based tracking and what that is worth in order value. Enter an estimated rate instead of an exact figure; if you do not know the rate, try different values to see how sensitive the result is. Three values are entered: the monthly purchase count from the store panel, the estimated share you think browser-based tracking misses, and the average order value. “currency” is written instead of a currency symbol; read it in your own currency. The numbers in the example only show how it works and do not reflect your store's data. Lost conversion estimate Monthly purchases (units) Estimated share not seen in the browser (%) Average order value (currency) Purchases visible in the browser (units)**320** Purchases not visible in the browser (units)**80** Value of visible purchases (currency)**320.000** Value of invisible purchases (currency)**80.000** At this rate the invisible share stays low. Still, compare your order count with the numbers in Events Manager to verify your estimate. At this rate a considerable share of sales is missing from the ad report. Server-side tracking helps close this gap; verify the real rate with your own data. At this rate most sales do not show in the ad report. If such an estimate is real, reports become misleading; first test the rate against your order data, then make the setup a priority. Calculation: visible = monthly purchases × (1 − rate); invisible = monthly purchases × rate; value = units × average order value. This is an estimate; a purchase not visible in the browser is a completed sale, only the measurement is lost. The gap between the ad report and the store panel is not caused by tracking loss alone; reporting delay and attribution rules also play a part. Keep two things in mind when reading the result. First, an “invisible” sale is not a lost sale: the money is in your account, but the ad system could not credit it to the ad. Second, this gap is a real cost in ad decisions: a profitable campaign that looks unprofitable gets cut by mistake. If you want to know how to raise purchase value and average basket, see [How to Increase Average Order Value: 12 Ways to Raise Revenue per Order in E-Commerce](https://www.faprika.com/en/blog/increase-average-order-value). ## How to Verify Tracking After Setup The safest way to verify the setup is to place a test order, confirm the event appears in Events Manager, and then check over a few days that the numbers stay consistent with your order count. Setup is done once; verification is done regularly. 1. **Place a test order:** Create a small order with a real payment (or use your test environment) and confirm the purchase event appears in Events Manager. 2. **Check the sources:** Confirm the event arrives from both the browser and the server, and that the source information lists both paths. 3. **Compare the numbers:** After a week, put the purchase count in Events Manager next to the order count in the store panel. They will not match exactly, but there should be a consistent relationship. 4. **Look for double counting:** If the event count is noticeably higher than the order count, review the duplicate event setting. 5. **Check regularly:** Repeat the same comparison every month; setting changes (a new checkout page, a new theme, a new consent window) can break measurement. When interpreting intermediate events such as cart abandonment, [What Is an Abandoned Cart? How to Reduce Cart Abandonment Rate in E-Commerce](https://www.faprika.com/en/blog/what-is-an-abandoned-cart) explains how to read the measurement results. ## What Are Common Mistakes in Server-Side Tracking? Common mistakes are treating the setup as finished without verifying it, ignoring the cookie preference, and misreading events that arrive via two paths. Each is fixed with a small setting or habit. - **Sharing the token:** The access token lets someone send events on your behalf on the platform. It must not be put in a screenshot, an email or a shared chat. - **Forgetting the “Active” box:** Even if the ID fields are filled in, tracking does not work unless “Active” is ticked and saved. - **Pasting into the wrong field:** The dataset ID goes into the pixel ID field and the token into the Conversions API ID field; if they are swapped, events do not reach the platform. - **Duplicating events unnecessarily:** Turning on events you will not use scatters the signal and makes control harder. - **Ignoring the consent preference:** Continuing server-side tracking after a user has declined creates both legal and reputational risk. - **Trying to match the report exactly to the store panel:** The platform report and the order count are calculated with different rules; the goal is consistency, not exact equality. ## Who Should Prioritize Server-Side Tracking? It is a priority for stores that spend on ads and get most of their sales from ads, and less urgent for stores that run no ads. The method's value shows where measurement turns into an ad decision. If any of these describes you, bring the setup forward: - The conversion count in the ad report is regularly and noticeably lower than the order count in the store panel. - Most of your traffic comes from mobile. - You are thinking of raising your ad budget but do not trust the results. - Your remarketing audiences are smaller than you expected. To get to know your target audience better, [What Is Customer Segmentation? How to Segment with RFM Analysis in E-Commerce](https://www.faprika.com/en/blog/customer-segmentation) sharpens your campaigns when combined with sound measurement. ## How Do You Turn Measurement Data into Ad Decisions? Complete measurement creates value only when it is used to decide: which campaign's budget goes up, which is cut, and which audience is reached again now rests on a more reliable base. Finishing the setup is half the job; the other half is reading the report regularly. A practical reading routine could look like this: - **Weekly comparison:** On the same day each week, write the purchase count in Events Manager next to the order count in the store panel and watch how the gap moves. If the gap suddenly changes, question any setting or theme change. - **Campaign-level evaluation:** Before switching a campaign off, consider whether missing events make it look worse than it is. Do not decide from a single week's view. - **Audience check:** Once add-to-cart events arrive in full, review the size of your remarketing audiences; if the audience has grown, measurement has improved. - **Budget limit:** After fixing measurement, raise the budget gradually rather than all at once and watch the result at each step. To interpret what the numbers mean, track indicators such as conversion rate, average order value and customer acquisition cost in the same table. The definitions and formulas of these indicators are explained in the [e-commerce metrics](https://www.faprika.com/en/blog/e-commerce-metrics) guide, and the general framework of cookie restrictions is explained in [çerezler yazısında](https://www.faprika.com/blog/cerezler-e-ticaret-sitenizin-sagligi-icin-iyi-mi-kotu-mu) . Okumanızı öneririz Çerezler E-Ticaret Sitenizin Sağlığı İçin İyi mi Kötü mü? Tip Note down measurement changes Keep a log of the dates you put a new checkout page, a new consent window or a new theme live. When tracking numbers suddenly shift, putting the dates side by side lets you find the cause in minutes. ## Setup Checklist: 8-Point Audit The checklist below shows in eight points whether the setup is complete. If all eight are done, your measurement rests on a solid foundation. *Görsel: Server-side conversion tracking checklist: dataset ID, access token, panel fields, active box, event selection, test order, cookie consent and regular measurement (Eight checks)* Server-side tracking check Dataset ID created in Events Manager Access token created and stored in a safe place Pixel ID and Conversions API ID fields filled in the panel “Active” box ticked and settings saved Events to track (such as add to cart, purchase) selected Test order visible in Events Manager Cookie consent preference correctly reflected in tracking Event counts regularly compared with order count Items that apply**2 / 8** The setup does not look complete yet. First complete the ID fields, the token and the “Active” box. The basics are in place but gaps remain. Review the event selection, the test order and the cookie preference. Your setup looks solid. Now compare the numbers regularly and use the event data in your ad decisions. | Field | Check | Done? | | --- | --- | --- | | Dataset | Dataset ID created in Events Manager | Yes / No | | Token | Access token created and stored safely | Yes / No | | Panel | Pixel ID and Conversions API ID filled in | Yes / No | | Active | Active box ticked, settings saved | Yes / No | | Event | Events such as add to cart and purchase selected | Yes / No | | Test | Test order visible in Events Manager | Yes / No | | Approval | Cookie consent preference reflected in tracking | Yes / No | | Measurement | Event counts regularly compared with order count | Yes / No | ## Frequently Asked Questions **What is server-side conversion tracking?** It means events such as purchases and add-to-cart actions are sent to the ad platform not only from the customer's browser but also from the store's server. This way, events lost in the browser because of cookie restrictions, blockers or phone OS versions are completed via the server path. **What is the difference between the Conversions API and the pixel?** The pixel sends the event from the browser and relies on cookies. The Conversions API sends the event from the store server. Ad platforms generally recommend using both together; the pixel carries browser information, and the API fills in the missing record. **Does setting up server-side tracking make cookie consent unnecessary?** No. Server-side tracking only changes the path the data takes; the visitor's consent choice, the privacy notice and personal data protection obligations apply in full. Continuing tracking that was declined through the server path is not a correct practice. **How do I set up the Conversions API in Faprika?** You create a dataset ID and an access token in the ad platform's events manager. In the Faprika panel, under Add-ons, paste the dataset ID into the pixel ID field and the token into the Conversions API ID field, select the events, check the “Active” box and save. **What percentage is the lost conversion rate?** There is no single rate that applies to everyone; it varies with the store's traffic mix, the devices used and cookie choices. You can see your own rate by comparing the order count in the store panel with the conversions reported by the ad platform; the calculator in this guide also shows the effect of different rates. **How do I know the setup works correctly?** Place a test order and check that the purchase event appears in the events manager and that the source information includes both browser and server. Then compare the event count with your order count for a week, and if there is a clear excess, review the duplicate event setting. Collect your ad data in full In Faprika, set up the Conversions API with a few fields from the panel and complete your measurement with analytics and product feed integrations. Let's plan your measurement setup together with our experts. Request a Demo #### You May Also Like - [**What Is an Abandoned Cart? How to Reduce Cart Abandonment Rate in E-Commerce**](https://www.faprika.com/en/blog/what-is-an-abandoned-cart) - [**E-Ticarette Veri Analitiği Kullanarak Büyümek**](https://www.faprika.com/blog/e-ticarette-veri-analitigi-kullanarak-buyumek) - [**What Is Customer Segmentation? How to Segment Customers with RFM Analysis in E-Commerce**](https://www.faprika.com/en/blog/customer-segmentation) - [**E-Commerce Conversion Rate: How to Increase It? Tips to Multiply Your Sales**](https://www.faprika.com/en/blog/how-to-increase-e-commerce-conversion-rate)