Collect the data › Data Layers
Module 5 of 21 Collect the data
Data Layers
The contract with the developer
4 sections about 47 min
- 01 What Is a Data Layer The data layer is a contract between your developers and your analytics. Who builds it, why it is the most fragile thing you own, and the rule you never break.
- 02 Adobe Client Data Layer (ACDL) The Adobe Client Data Layer, step by step: declare, push, catch it in Launch. Where its event history earns its keep, and what it honestly costs.
- 03 Do You Really Need ACDL? ACDL is not just technology, it is a bet about your team. What problem it really solves, why a simple model is often stronger, and the central trade-off.
- 04 Data Layer Design Good design is not clever design. The family-tree rule, naming that survives a rewrite, and how to design a node one question at a time.
About this module
Why analytics should never read the page directly, what belongs in the object, whether the Adobe Client Data Layer is worth adopting, and designing for change.
A data layer is an agreement between the people who build a website and the people who measure it. The site publishes its values in a known shape, and analytics reads them without needing to understand how the page works.
This module covers what that agreement looks like in practice, the Adobe Client Data Layer and whether you actually need it, and how to design one that survives a site rewrite. The design part matters most. A data layer built to mirror how the site happens to work today becomes a liability the moment the site changes.
Next module 6. Adobe Launch (Tags)