Tealium’s “Universal Data Hub” (UDH) claims to be a central place for acting on real-time customer behaviour data. The promise: Get customer data into the “Hub” from anywhere, enrich it via rules, have it stitched and join it with data from other sources, and then send it server-side to wherever you need it, via connectors or APIs.
The more product data, the more work for developers, the heavier your Data Layer. Tealium’s “Dynamic Data Layer Management” promises to ban at least the developer part forever. The idea is to enrich your Data Layer in real time with data (like “best-price” labels) that is hosted somewhere outside on a CDN. It has huge potential and is something you cannot do with a other Tag Management Systems. But does DDLM live up to its promise? We tested it.
In an E-Commerce company, work revolves around product data. That does not only apply to search filters, bidding strategies and on- and offsite advertisement, but also to data analysis. Do our best-price products really convert better than the rest? Which price ranges are we selling the most in our wine section?
localStorage has long established itself as a wonderfully comfortable way to store data in the user’s browser. Many tracking implementations depend on it.
But it is not the best solution for all cases, as 7-8% of users block it (on our site at least).
The “Marketing Channel” is the main entry point for any analysis on digital campaign performance in today’s Web Analytics world. But how good is a channel if you can only see how much money it earned you, but not how much you spent on it?
Both Google and Adobe Analytics do not make it easy here.
While there is no way to get the cost per channel into Google Analytics apart from the context of the Multi-Channel Funnel Reports,, Adobe offers a somewhat hidden trick. And you can go full circle: Cost->Revenue->Refunds = the real ROAS.