Review application-wide click attribution when introducing parent tags

Source facts

Microsoft cautions that introducing parentDataTag on an application’s HTML element makes the Click Analytics SDK look for parent tags throughout that application, not only at the edited element. An explicit data-parentid or prefixed parentid attribute takes precedence over parentDataTag. For the HEART workbook integration, the documentation says parentDataTag must be declared in the application’s other parts for HEART events to be logged or detected. Microsoft Learn.

Applicability

Use this scope review when adding parent attribution to existing click collection. Consider components that were not edited, shared navigation and dynamically rendered controls, rather than assessing only the first tagged button.

DSE recommendation

Treat the first parent-tag introduction as an application-wide instrumentation change and test attribution outside the edited component. Define the intended parent identifier for representative controls and identify explicit parentid overrides. If HEART is used, include its event requirements in that review. Keep parent identifiers stable and free of sensitive content through the application’s own telemetry design decisions.

Verification

Compare recorded parentId values before and after the approved change across both edited and unchanged components. Include a control with an explicit parentid and one that relies on parent discovery. Confirm the expected attribution and inspect missing or unexpected parents before using the data for comparisons. Preserve the tested component list so a later shared-layout change triggers a targeted review instead of silently changing the meaning of click groups.

Official references

Microsoft Learn: Click Analytics parent attribution. Source reviewed September 9, 2026.