As a marketer, I see actions on buttons components in content pages tracked by Analytics Cloud

• Type: Story
• Status: Closed
• Priority: Minor
• Resolution: Completed
• Affects Version/s: None
• Fix Version/s: 7.2.10 DXP FP2, 7.2.10.1 DXP SP1, 7.2.X, Master
• Component/s: Pages > A/B Testing for Content Pages
• Labels:
  • ab-test-ac-scope
  • fc_19_09
  • liferay-dxp-72-sp1
  • liferay-fixpack-dxp-2-7210
• Branch Version/s:
  7.2.x
• Backported to Branch:
  Committed
• Epic/Theme:
  • AB_Testing
• Epic Link: tango-ab-testing
• Sprint: TANGO| SP_19 | Sep04-Sep18
• Git Pull Request: https://github.com/brianchandotcom/liferay-portal/pull/78127

Motivation

Analytics Cloud tracks click events only on clickable elements with an id attribute. Therefore, in order to make button components in content pages traceable, they require an id attribute.

Technical Requirements

The id must:

• Be unique in the page
• Do not change across requests
• Do not change across published-draft status
• Do not change across staging-live status

Acceptance Criteria

Button components markup contains id attribute.

• Given a Content Page with a component button
• When the button's markup is inspected
• Then the id is present

Analytics Cloud sends the button id as part of the click event

• Given a Content Page with a component button and Analytics Enabled
• When a click is performed on the button
• Then the Analytics request payload contains the click event and the button id (requires inspecting the network traffic)