Analyze the data › Activity Map
Module 18 of 21 Analyze the data
Activity Map
What they clicked
4 sections about 29 min
- 01 Activity Map Overview Page reports count arrivals and cannot tell you which button people pressed. What Activity Map records, and why the overlay is not the useful part.
- 02 Implementation and Setup How Adobe works out a link name, what to do when that name is useless, and the elements it silently refuses to track at all.
- 03 Using Activity Map The overlay on the live page and the dimensions in Workspace answer different questions. Which to reach for, and what Live mode cannot do.
- 04 Activity Map Best Practices What this data answers honestly, where it misleads, what single page apps do to it, and why a Web SDK migration should be planned around it.
About this module
Activity Map shows you what people actually clicked, and where on the page they clicked it. Setting it up, reading it, and its blind spots.
Page reports tell you people arrived. They cannot tell you which of the four buttons on that page anybody pressed.
Activity Map answers that. This module covers how Adobe works out a link's name, what to do when that name turns out to be useless, and the two quite different ways of reading the data: an overlay on the live page, and dimensions inside Workspace. It ends with where this data misleads, because click reports flatter pages that are simply busy, and single page applications complicate them further.
Next module 19. Solution Design Reference (SDR)