---
title: "Website Tracking in E-Commerce 2026: The Stack"
canonical_url: "https://www.laioutr.com/en/blog/website-tracking-ecommerce-stack-overview-2026"
locale: en
meta:
  description: "Website tracking in e-commerce has five layers: consent, tag management, analytics, server-side delivery and attribution. What each does and where it stops."
  "og:description": "Website tracking in e-commerce has five layers: consent, tag management, analytics, server-side delivery and attribution. What each does and where it stops."
  "og:title": "Website Tracking in E-Commerce 2026: The Stack"
---

![Hero website tracking ecommerce stack overview 2026 en](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmv856dsldqtc06mq855auujq)

# Website Tracking in E-Commerce 2026: An Honest Stack Overview

Table of contents

1. [1.Why a stack view helps](#why-a-stack-view-helps)
2. [2.The five layers of a tracking stack](#the-five-layers-of-a-tracking-stack)
3. [3.The gaps that remain in every setup](#the-gaps-that-remain-in-every-setup)
4. [4.A practical order for building or cleaning up the stack](#a-practical-order-for-building-or-cleaning-up-the-stack)
5. [5.Where the frontend fits in](#where-the-frontend-fits-in)
6. [6.FAQ](#faq)
7. [7.Conclusion](#conclusion)

1. [1.Why a stack view helps](#why-a-stack-view-helps)
2. [2.The five layers of a tracking stack](#the-five-layers-of-a-tracking-stack)
3. [3.The gaps that remain in every setup](#the-gaps-that-remain-in-every-setup)
4. [4.A practical order for building or cleaning up the stack](#a-practical-order-for-building-or-cleaning-up-the-stack)
5. [5.Where the frontend fits in](#where-the-frontend-fits-in)
6. [6.FAQ](#faq)
7. [7.Conclusion](#conclusion)

Website tracking in e-commerce is not one tool but a stack of five layers: consent management, tag management, analytics, server-side delivery and attribution. Each layer solves a specific problem, and each has hard limits that no vendor can remove. A reliable setup starts with knowing which question each layer answers and which data it will never see.

This overview walks through the stack from the browser to the report, names the typical tools in each layer and is explicit about the gaps that remain even in a well-built setup. It is meant as a starting point for merchants and product or marketing owners who want to sort out their measurement before buying the next tool.

## Why a stack view helps

Most tracking problems in online shops are not caused by a missing tool. They come from layers that were added at different times by different teams and never designed to work together. A consent banner from one vendor, a tag manager container maintained by an agency, an analytics property set up three relaunches ago and an attribution model nobody can explain: that is a common picture.

Looking at tracking as a stack makes three things visible:

- **Dependencies.** Analytics can only count what consent allows and what tags actually send.
- **Ownership.** Each layer needs a clear owner. Legal and data protection own consent rules, engineering owns the data layer, marketing owns the goals and reports.
- **Failure points.** Data gets lost at specific transitions, for example between the click in the storefront and the tag that should fire, or between the browser and the analytics endpoint.

## The five layers of a tracking stack

| Layer | Job | Typical tools | Hard limit |
| --- | --- | --- | --- |
| Consent management | Asks for and stores consent, controls what may load | Consent management platforms, consent APIs | No consent means no tracking for that purpose, regardless of technology |
| Tag management | Loads and fires tags based on rules | Google Tag Manager, Tealium, server-side containers | Only as stable as the page structure it reads |
| Analytics | Collects events and turns them into reports | GA4, Matomo, Piwik PRO, Amplitude, Mixpanel | Counts sessions and events, not people |
| Server-side delivery | Forwards events from a server instead of the browser | GTM Server-Side, Cloudflare Zaraz, RudderStack | Recovers technical losses, not missing consent |
| Attribution | Assigns orders to channels and campaigns | Platform attribution, MMM, incrementality tests | Every model is an assumption, none is ground truth |

### Layer 1: Consent management

Consent sits at the top because it decides what may happen at all. In Germany, storing or reading information on a visitor's device generally requires consent under § 25 TDDDG (formerly TTDSG), unless it is strictly necessary for the service the visitor requested. Processing personal data also needs a legal basis under the GDPR.

Courts take this seriously. The Administrative Court of Hanover ruled in March 2025 that even loading Google Tag Manager requires consent, and that a banner without an equal reject option does not produce valid consent ([VG Hannover, judgment of March 19, 2025, 10 A 5385/22](https://voris.wolterskluwer-online.de/browse/document/230df5cf-d76c-4561-9499-e44445a96f11)). This is not legal advice, and every setup needs to be checked individually, but the direction is clear: consent is the gate for most of the stack.

What consent management cannot do: it cannot create data for visitors who decline. Every report downstream inherits the consent rate as a blind spot.

### Layer 2: Tag management

Tag managers decouple marketing tags from deployments. A team can add a conversion pixel or change a trigger without a release. That flexibility is real, and so is the weak spot: triggers often depend on CSS classes, element positions or button texts. When the storefront changes, triggers break quietly. Our earlier analysis of [why visual tagging still depends on the frontend structure](https://www.laioutr.com/en/blog/google-tag-manager-merge-frontend-tracking-gap) goes into this in detail.

The more robust pattern is a data layer that is part of the component definition: a product tile, a filter or a checkout step emits defined events with defined fields, independent of how the element looks.

### Layer 3: Analytics

Analytics tools turn events into sessions, funnels and reports. The choice between GA4, Matomo, Piwik PRO or a product analytics tool is mostly about data residency, reporting needs and the team that works with it. Three limits apply to all of them:

- They measure devices and browsers, not people. One customer on phone and laptop shows up twice unless there is a login.
- They depend on what arrives. Ad blockers, browser restrictions and failed scripts reduce the input before any processing starts.
- Modeled or estimated data fills some gaps, but it is an estimate and should be labeled as such in reports.

### Layer 4: Server-side delivery

Server-side tracking moves the forwarding of events from the browser to a server or edge endpoint under the shop's own domain. The browser sends one first-party request, the server distributes it to GA4, ad platforms or a data warehouse. This reduces losses from blocked third-party scripts, mitigates cookie lifetime issues in browsers with strict storage rules and removes JavaScript from the page, which helps Core Web Vitals.

It does not replace consent. A server-side setup that tracks visitors who declined is not a technical improvement, it is a compliance problem. The details, including architecture options and deduplication, are covered in [our guide to server-side tracking in e-commerce](https://www.laioutr.com/en/blog/server-side-tracking-ecommerce-complete-measurement-2026).

### Layer 5: Attribution

Attribution answers which channel gets credit for an order. Ad platforms attribute in their own favor, last-click models overweight the final touch, data-driven models need volume and are hard to audit. Marketing mix modeling and incrementality tests are more robust for budget decisions but slower and less granular.

The honest summary: attribution is a decision model, not a measurement. It should be consistent and documented, not perfect.

## The gaps that remain in every setup

Even a well-built stack has gaps. Planning with them is better than hiding them.

1. **Declined consent.** Visitors who decline are not tracked for that purpose. Server-side delivery, fingerprinting or other tricks must not be used to work around this.
2. **Browser restrictions.** Safari has blocked third-party cookies by default since 2020 and limits script-written storage after seven days without interaction ([WebKit, Full Third-Party Cookie Blocking](https://webkit.org/blog/10218/full-third-party-cookie-blocking-and-more/)). Chrome kept third-party cookies, but that does not make cross-site tracking reliable.
3. **Ad blockers.** Blockers filter known tracking domains and scripts. First-party endpoints reduce the loss, they do not eliminate it.
4. **Cross-device journeys.** Without login, one person on several devices remains several users.
5. **Broken triggers.** Tags that fire on visual selectors stop working after redesigns, often without an alert.

## A practical order for building or cleaning up the stack

1. **Define the questions first.** Which decisions should tracking support: budget per channel, funnel drop-offs, product performance? Every event needs a reason.
2. **Write an event schema.** Names, parameters, data types, owner. One schema for all destinations, versioned like code.
3. **Fix consent before tools.** Banner design, categories, reject option on the first layer, documentation. Get this checked by data protection or legal counsel.
4. **Anchor events in the frontend components,** not in visual selectors. That makes tracking survive redesigns.
5. **Add server-side delivery where losses and performance justify it,** with consent signals passed through.
6. **Agree on an attribution model** and document its assumptions.
7. **Monitor event volumes.** A sudden drop in a single event is usually a broken trigger, not a change in customer behavior.

## Where the frontend fits in

Most tracking data originates in the storefront. If the frontend has a clear component model, tracking becomes a property of that model instead of an afterthought. In Laioutr, base event capture runs through the component schema of the frontend and is part of the platform: clicks, views and interactions on sections and blocks are captured without manual tagging, and consent rules are respected. On top of that, the **Server Side Tracking add-on** forwards these events server-side to destinations such as GA4, Meta, TikTok, a data warehouse or RudderStack, with Cloudflare Zaraz or GTM Server-Side as possible providers. The details are on the [Tracking & Analytics product page](https://www.laioutr.com/en/product/tracking-analytics).

Because the frontend runs as a [Composable Headless Frontend](https://www.laioutr.com/en/composable-headless-frontend) on top of the existing commerce backend, the event schema stays stable when the backend changes. And less tag JavaScript in the browser supports the work on [Core Web Vitals and frontend performance](https://www.laioutr.com/en/product/performance-core-web-vitals).

## FAQ

### What does a minimal tracking stack for an online shop need?

A consent management solution, a defined event schema, one analytics tool and a clear owner for each. Tag management and server-side delivery are useful additions once the basics are clean.

### Is server-side tracking a way to track without consent?

No. Server-side tracking changes where events are forwarded, not whether a visitor agreed. Purposes that require consent still require it. Legal questions should be checked case by case with data protection counsel.

### Why do analytics numbers differ from shop orders?

Analytics counts tracked sessions and events, the shop system counts real orders. Declined consent, ad blockers, browser restrictions and broken tags create a gap. A stable gap is normal, a sudden change is a signal to check the setup.

### Which layer should be fixed first?

Consent and the event schema. Without valid consent the data is a risk, and without a schema every tool collects something different.

### Does a new frontend make tracking more reliable?

It can, if events are part of the component model. Then a redesign does not silently break tracking, and fewer scripts in the browser help performance.

## Conclusion

Website tracking in e-commerce works best when each layer has a defined job, a defined owner and documented limits. No stack measures everything, and that is fine as long as the gaps are known. Teams that anchor tracking in the frontend components and treat the frontend as part of a [Composable Digital Experience Platform](https://www.laioutr.com/en/composable-digital-experience-platform), where storefront, data and measurement come together, reduce the most common failure point: tags that break when the shop changes.

---

Share this article

[Share on Facebook](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Fwww.laioutr.com%2Fen%2Fblog%2Fwebsite-tracking-ecommerce-stack-overview-2026) [Share on X](https://x.com/intent/post?url=https%3A%2F%2Fwww.laioutr.com%2Fen%2Fblog%2Fwebsite-tracking-ecommerce-stack-overview-2026&text=) [Share on LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fwww.laioutr.com%2Fen%2Fblog%2Fwebsite-tracking-ecommerce-stack-overview-2026) [Share on Pinterest](https://pinterest.com/pin/create/button/?url=https%3A%2F%2Fwww.laioutr.com%2Fen%2Fblog%2Fwebsite-tracking-ecommerce-stack-overview-2026&description=) [Share via email](mailto:?subject=&body=%0A%0Ahttps%3A%2F%2Fwww.laioutr.com%2Fen%2Fblog%2Fwebsite-tracking-ecommerce-stack-overview-2026)

## More articles on frontend and headless

Practical know-how for frontend development, smart agents, and headless

[To the blog](https://www.laioutr.com/en/blogs/insights)

[![Hero frontend operations multi agent coordination storefront 2026 en](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmvdnuukuo9nt06l88v0h57oj)<h3>Several AI Agents, One Storefront: Coordination Without Collisions</h3>When several AI agents work on the same storefront, conflicts rarely happen between the agents thems…](https://www.laioutr.com/en/blog/frontend-operations-multi-agent-coordination-storefront-2026)

[![Hero frontend operations measuring ai agents outcomes 2026 en](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmvdnthydoeap06la2ojcfoqd)<h3>Measuring AI Agents by Outcomes: Agentic Frontend Management Metrics</h3>AI agents in the frontend should be measured by outcomes, not by activity. The number of prompts, ge…](https://www.laioutr.com/en/blog/frontend-operations-measuring-ai-agents-outcomes-2026)

[![Hero frontend operations execution gap detect vs deploy 2026 en](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmvdns6wxo7zo06l8pq1u047r)<h3>The Execution Gap in the Frontend: Finding Is Cheap, Shipping Is Not</h3>The execution gap in the frontend is the time, and the number of handoffs, between "we know wha…](https://www.laioutr.com/en/blog/frontend-operations-execution-gap-detect-vs-deploy-2026)

[![Hero frontend operations ai layer existing stack without replatforming 2026 en](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmvdnq7bwo79x06l9wjxd6m4x)<h3>Adding an AI Layer to an Existing Commerce Stack Without Replatforming</h3>An AI layer can be added to an existing commerce stack without replacing the shop system. The most p…](https://www.laioutr.com/en/blog/frontend-operations-ai-layer-existing-stack-without-replatforming-2026)

[![Hero frontend operations hidden cost manual storefront changes 2026 en](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmvdnourdo4ln06l897y7lscd)<h3>The Hidden Cost of Manual Storefront Changes and How to Cut It</h3>Manual frontend changes are the many small edits that keep a storefront running day to day: a new ba…](https://www.laioutr.com/en/blog/frontend-operations-hidden-cost-manual-storefront-changes-2026)

[![Hero frontend operations agent task map role risk 2026 en](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmvbb5d3f6l5606lact6cr70s)<h3>Which Frontend Tasks Should AI Agents Take Over? Role and Risk Map</h3>AI agents should first take over the frontend tasks that come up often, involve a lot of manual work…](https://www.laioutr.com/en/blog/frontend-operations-agent-task-map-role-risk-2026)

[![Hero frontend operations monitoring beyond uptime 2026 en](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmvbb4h8w6kg106lagdg131h4)<h3>Frontend Monitoring Beyond Uptime: Signals a Storefront Needs</h3>Frontend monitoring beyond uptime means checking a storefront not only for availability but for what…](https://www.laioutr.com/en/blog/frontend-operations-monitoring-beyond-uptime-2026)

[![Hero frontend operations root cause revenue drop storefront 2026 en](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmvbb1el66i2m06laj68axyua)<h3>Root Cause in the Frontend: When Revenue Drops Start in the Storefront</h3>When revenue or conversion rate drops suddenly, the cause often is not traffic, pricing or the comme…](https://www.laioutr.com/en/blog/frontend-operations-root-cause-revenue-drop-storefront-2026)

[![Hero laioutr academy en](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmvba7ww4640s06l9q29b5w7w)<h3>Laioutr Academy Is Live: The Video Manual for Laioutr</h3>Since October 15, 2026, the Laioutr Academy has been live at academy.laioutr.com. It is the user man…](https://www.laioutr.com/en/blog/laioutr-academy-launch-video-manual-certification)

[![Hero tailwind alpine magento vs component based frontend 2026 en](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmvai9tkiw9rk06mmt53z6mt5)<h3>Tailwind + Alpine vs. Component-Based Frontends for Magento</h3>Hyvä renders Magento pages on the server with PHP templates and layout XML, adds interactivity throu…](https://www.laioutr.com/en/blog/tailwind-alpine-magento-vs-component-based-frontend-2026)

[![Hero orocommerce frontend twig layouts bottleneck en](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmvaiaokow8v906leia28cwal)<h3>OroCommerce Frontend: Out of the Twig and Layouts Bottleneck</h3>The OroCommerce frontend is a server-rendered storefront built from Symfony bundles, OroLayouts and …](https://www.laioutr.com/en/blog/orocommerce-frontend-twig-layouts-bottleneck)

[![Hero magento multichannel personalization web mobile voice 2026 en](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmvai8r4tw93u06mmzl7zm6nc)<h3>One Magento Backend, Many Channels: Personalization in Practice</h3>Personalization across web, mobile and voice on a single Magento backend does not start with a featu…](https://www.laioutr.com/en/blog/magento-multichannel-personalization-web-mobile-voice-2026)

[![Hero edge hosting storefronts peak traffic caching 2026 en](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmvaicbu8wamt06mmftbhsb7j)<h3>Edge Hosting for Storefronts: Caching That Holds Under Peak Load</h3>Edge hosting keeps a storefront fast under load when most requests never reach the origin: pages and…](https://www.laioutr.com/en/blog/edge-hosting-storefronts-peak-traffic-caching-2026)

[![Hero composable commerce 2027 outlook en](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmvai9sb4w8he06le9jw0nlqx)<h3>Composable Commerce 2027: What Shifted and What Comes Next</h3>Composable commerce enters 2027 with a different agenda than a year ago. The architecture question i…](https://www.laioutr.com/en/blog/composable-commerce-2027-outlook)

[![Hero ai engagement conversion frontend personalization en](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmvaiaieiw8qu06le7elyjd3k)<h3>AI Engagement and Conversion: Personalization on the Frontend</h3>AI-driven engagement and conversion on the frontend rests on five mechanics: segments decide who see…](https://www.laioutr.com/en/blog/ai-engagement-conversion-frontend-personalization)

## Apps for the Laioutr platform

[View all apps](https://www.laioutr.com/en/apps)

[![App Shopify](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/resize=width:400/auto_image/cmk19p2kpsk1o07mljlgx3ma7)](https://www.laioutr.com/en/apps/shopify)

Laioutr

[Shopify](https://www.laioutr.com/en/apps/shopify)

Shopify is a commerce platform for selling online and in physical retail.

[![App shopware](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/resize=width:400/auto_image/cmk19p2mzsmns07l8mxvvlllb)](https://www.laioutr.com/en/apps/shopware)

Laioutr

[Shopware](https://www.laioutr.com/en/apps/shopware)

Shopware is a flexible ecommerce platform from Europe for product catalogs and omnichannel commerce.

[![App adobe commerce](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/resize=width:400/auto_image/cmk19p22msmn707l8yvl65rea)](https://www.laioutr.com/en/apps/adobe-commerce)

Laioutr

[Adobe Commerce](https://www.laioutr.com/en/apps/adobe-commerce)

Adobe Commerce is an enterprise commerce platform for complex, global B2C and B2B scenarios.

Planned

[![App B2B sellers suite](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/resize=width:400/auto_image/cmno8wnogmesx08l8ogxv3gid)](https://www.laioutr.com/en/apps/b2b-sellers)

Laioutr

[B2Bsellers](https://www.laioutr.com/en/apps/b2b-sellers)

B2B suite for Shopware that turns an online store into a professional B2B commerce platform.

Planned

[![App commerce layer](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/resize=width:400/auto_image/cmk19p24vsk1a07mlrun4pqiv)](https://www.laioutr.com/en/apps/commerce-layer)

Laioutr

[Commerce Layer](https://www.laioutr.com/en/apps/commerce-layer)

Commerce Layer is a headless commerce platform for making inventory and catalogs available online.

[![App commercetools](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/resize=width:400/auto_image/cmk19p29pbwz607lb1smrjjd3)](https://www.laioutr.com/en/apps/commercetools)

Laioutr

[Commercetools](https://www.laioutr.com/en/apps/commercetools)

Commercetools is a SaaS-based headless ecommerce platform used worldwide.

[![App emporix](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/resize=width:400/auto_image/cmk19p2c5bwzd07lb4cihw58l)](https://www.laioutr.com/en/apps/emporix)

Laioutr

[Emporix](https://www.laioutr.com/en/apps/emporix)

Emporix is a composable, API-first commerce platform for scalable B2B and B2C scenarios.

Planned

[![App HCL Software](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/resize=width:400/auto_image/cmlknq0xp7nkt06mm3nhm6vpf)](https://www.laioutr.com/en/apps/hcl-software)

Laioutr

[HCL Software](https://www.laioutr.com/en/apps/hcl-software)

Enterprise suite for digital commerce and experience with extensive configurability.

Planned

[![App intershop](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/resize=width:400/auto_image/cmlknq10d7zbz06l44qdcwpao)](https://www.laioutr.com/en/apps/intershop)

Laioutr

[Intershop](https://www.laioutr.com/en/apps/intershop)

Enterprise commerce platform for complex B2B and B2C business models.

Planned

[![App magento 2](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/resize=width:400/auto_image/cmm1svkn1mbb407l6vo1np8s2)](https://www.laioutr.com/en/apps/magento-2)

Laioutr

[Magento 2](https://www.laioutr.com/en/apps/magento-2)

Widely used, extensible commerce platform for B2C and B2B scenarios.

[![App Oxid](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/resize=width:400/auto_image/cmk19p2eask1h07mlr6q5kx0k)](https://www.laioutr.com/en/apps/oxid-eshop)

Laioutr

[OXID eShop](https://www.laioutr.com/en/apps/oxid-eshop)

OXID eShop is an extensible commerce platform for complex B2B and B2C requirements.

Planned

[![App cover patchworks](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/resize=width:400/auto_image/cmph2jgr7bs5e08la66xwac9q)](https://www.laioutr.com/en/apps/patchworks)

Laioutr

[Patchworks](https://www.laioutr.com/en/apps/patchworks)

Patchworks is a low-code iPaaS that connects ecommerce, ERP, WMS, 3PL, and marketplaces.

Planned

[![App PRESTASHOP](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/resize=width:400/auto_image/cmpcdbhqnm8st07mn8aol584c)](https://www.laioutr.com/en/apps/PrestaShop)

Laioutr

[Prestashop](https://www.laioutr.com/en/apps/PrestaShop)

Open-source commerce platform for small and midsize merchants in Europe and beyond.

Planned

[![App saleor](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/resize=width:400/auto_image/cmpcdbhwsmjzr07milpv60c1r)](https://www.laioutr.com/en/apps/saleor)

Laioutr

[Saleor](https://www.laioutr.com/en/apps/saleor)

Open-source, API-first commerce platform built on GraphQL for custom storefronts.

Planned

[![App Commercecloud](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/resize=width:400/auto_image/cmk19p26ysmne07l82vn6q45s)](https://www.laioutr.com/en/apps/salesforce-commerce-cloud)

Laioutr

[Salesforce Commerce Cloud](https://www.laioutr.com/en/apps/salesforce-commerce-cloud)

Salesforce Commerce Cloud is a cloud-based enterprise commerce platform for businesses of any size.

Planned

[![App SAP](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/resize=width:400/auto_image/cmk19p2gasmnl07l8u6936vg4)](https://www.laioutr.com/en/apps/sap-commerce-cloud)

Laioutr

[SAP Commerce Cloud](https://www.laioutr.com/en/apps/sap-commerce-cloud)

Enterprise commerce platform for complex catalogs, pricing models, and omnichannel journeys.

Planned

[![App SCAYLE](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/resize=width:400/auto_image/cmk19p2ihbwzk07lbl6d3mrzy)](https://www.laioutr.com/en/apps/scayle)

Laioutr

[Scayle](https://www.laioutr.com/en/apps/scayle)

SCAYLE is a commerce engine that helps brands and retailers scale their business.

Planned

[![App spryker](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/resize=width:400/auto_image/cmk19p2p4sk1v07ml2vx76nwh)](https://www.laioutr.com/en/apps/spryker)

Laioutr

[Spryker](https://www.laioutr.com/en/apps/spryker)

Composable commerce platform for sophisticated B2B and B2C business models.

[![App Sylius](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/resize=width:400/auto_image/cmk19p2rhbwzr07lbmrgxt51s)](https://www.laioutr.com/en/apps/sylius)

Laioutr

[Sylius](https://www.laioutr.com/en/apps/sylius)

Sylius is a developer-friendly ecommerce framework for B2C and B2B shopping experiences.

Planned

[![App vendure](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/resize=width:400/auto_image/cmk19p2tgsk2207mltugd287f)](https://www.laioutr.com/en/apps/vendure)

Laioutr

[Vendure](https://www.laioutr.com/en/apps/vendure)

Vendure is a headless commerce platform for businesses with complex requirements.

Coming Soon

[![App VTEX](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/resize=width:400/auto_image/cmk19p2vosmnz07l8d45obeq9)](https://www.laioutr.com/en/apps/vtex)

Laioutr

[VTEX](https://www.laioutr.com/en/apps/vtex)

Cloud-native, composable commerce platform for B2B and B2C at scale.

Planned

[![App Websale](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/resize=width:400/auto_image/cmkav7t75rwim06l1v4t9o0cb)](https://www.laioutr.com/en/apps/websale)

Laioutr

[Websale](https://www.laioutr.com/en/apps/websale)

Stable, enterprise-ready commerce backend for complex retail environments.

![Strategy call about the Laioutr platform](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/resize=width:1024/auto_image/cmolld7ym133w07les4g75kr9)

Strategy call

## The frontend as a control layer

A conversation about stack, roadmap and replatforming scenario. The outcome: a clear picture of how Laioutr fits, what it costs and how fast the go-live can happen.  
  
*"After 30 minutes, we knew Laioutr makes our replatforming feasible."*  
*Daniel B., CEO,* [*hygibox.de*](https://hygibox.de)

[Book a demo](https://www.laioutr.com/en/contact)

## Structured Data

```json
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "Organization",
      "@id": "https://www.laioutr.com/#identity",
      "name": "Laioutr",
      "legalName": "Laioutr GmbH",
      "url": "https://www.laioutr.com/",
      "logo": {
        "@type": "ImageObject",
        "url": "https://www.laioutr.com/laioutr-logo.png",
        "width": 400,
        "height": 400
      },
      "email": "info@laioutr.com",
      "telephone": "+49 30 75435715",
      "address": {
        "@type": "PostalAddress",
        "streetAddress": "Münchweilersteig 5",
        "postalCode": "12559",
        "addressLocality": "Berlin",
        "addressCountry": "DE"
      },
      "vatID": "DE450905846",
      "sameAs": [
        "https://www.linkedin.com/company/laioutr",
        "https://www.youtube.com/@Laioutr",
        "https://x.com/laioutr"
      ]
    },
    {
      "@type": "WebSite",
      "@id": "https://www.laioutr.com/en/#website",
      "url": "https://www.laioutr.com/en/",
      "name": "Laioutr",
      "inLanguage": "en",
      "publisher": {
        "@id": "https://www.laioutr.com/#identity"
      }
    },
    {
      "@type": "BlogPosting",
      "@id": "https://www.laioutr.com/en/blog/website-tracking-ecommerce-stack-overview-2026#article",
      "headline": "Website Tracking in E-Commerce 2026: An Honest Stack Overview",
      "description": "Website tracking in e-commerce has five layers: consent, tag management, analytics, server-side delivery and attribution. What each does and where it stops.",
      "image": [
        "https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmv856dsldqtc06mq855auujq"
      ],
      "datePublished": "2026-10-15T10:51:29.643413+00:00",
      "dateModified": "2026-10-14T13:24:54.306501+00:00",
      "inLanguage": "en",
      "articleSection": "Insights",
      "keywords": "Composable, Performance, Marketing, Storefront Experience",
      "author": {
        "@id": "https://www.laioutr.com/#identity"
      },
      "publisher": {
        "@id": "https://www.laioutr.com/#identity"
      },
      "mainEntityOfPage": {
        "@id": "https://www.laioutr.com/en/blog/website-tracking-ecommerce-stack-overview-2026#webpage"
      },
      "isPartOf": {
        "@id": "https://www.laioutr.com/en/#website"
      }
    },
    {
      "@type": "WebPage",
      "@id": "https://www.laioutr.com/en/blog/website-tracking-ecommerce-stack-overview-2026#webpage",
      "url": "https://www.laioutr.com/en/blog/website-tracking-ecommerce-stack-overview-2026",
      "name": "Website Tracking in E-Commerce 2026: An Honest Stack Overview",
      "description": "Website tracking in e-commerce has five layers: consent, tag management, analytics, server-side delivery and attribution. What each does and where it stops.",
      "inLanguage": "en",
      "isPartOf": {
        "@id": "https://www.laioutr.com/en/#website"
      },
      "breadcrumb": {
        "@id": "https://www.laioutr.com/en/blog/website-tracking-ecommerce-stack-overview-2026#breadcrumb"
      },
      "primaryImageOfPage": {
        "@type": "ImageObject",
        "url": "https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmv856dsldqtc06mq855auujq"
      },
      "datePublished": "2026-10-15T10:51:29.643413+00:00",
      "dateModified": "2026-10-14T13:24:54.306501+00:00",
      "mainEntity": {
        "@id": "https://www.laioutr.com/en/blog/website-tracking-ecommerce-stack-overview-2026#article"
      }
    },
    {
      "@type": "BreadcrumbList",
      "@id": "https://www.laioutr.com/en/blog/website-tracking-ecommerce-stack-overview-2026#breadcrumb",
      "itemListElement": [
        {
          "@type": "ListItem",
          "position": 1,
          "name": "Laioutr",
          "item": "https://www.laioutr.com/en/"
        },
        {
          "@type": "ListItem",
          "position": 2,
          "name": "Insights",
          "item": "https://www.laioutr.com/en/blogs/insights"
        },
        {
          "@type": "ListItem",
          "position": 3,
          "name": "Website Tracking in E-Commerce 2026: An Honest Stack Overview"
        }
      ]
    }
  ]
}
```
