Adobe Tags data elements: enterprise best practices

The end-to-end flow

Five design rules

1. Standardise the data layer — one structure and naming convention for every team.
2. Create reusable data elements — page name, user ID, product ID, transaction value.
3. Add validation and defaults — handle null, undefined and invalid values.
4. Govern — document owner, source, type, definition and usage.
5. Control change — approvals, versioning and QA.

Safe defaults

var value = window.digitalData && digitalData.user && digitalData.user.name;
return value != null && value !== "" ? value : "Unknown";

Single-page apps

There is no full page load, so listen for route changes or application events. Update the data layer before triggering the rule:

window.digitalData.page.pageInfo.pageName = "Product Details";
_satellite.track("productView");

When the data layer changes

Renaming product.id to product.productId silently breaks every data element that reads the old path. Treat data-layer changes as releases with a contract, and test data elements before deploying.