This makes it difficult to easily find the associated cif component in a similar fashion as wcm core components. Further, the @id field seems wrong when injected into the data layer. The data layer might have:
"component": {
{
"product-7fc286dec9": {
"xdm:currencyCode": "USD",
"xdm:categories": [ ... ],
"xdm:SKU": "VT11",
"xdm:assets": [ ... ],
"xdm:listPrice": 68,
"dc:description": "<p>The Valeria Tank features two layers of possibility. The loose fit flatters without impacting comfort and the tiered material hangs beautifully. Wear alone or add a belt for a little more definition. </p><p>Features:</p><ul><li>Scoop neck</li><li>Sleeveless</li><li>Sits below the hips</li><li>Two layers</li><li>Machine wash, tumble dry low</li></ul>",
"dc:title": "Valeria Two-Layer Tank",
"@type": "venia/components/commerce/product",
"parentId": "page-f9dfabef95"
}
}
}
Where there is eventInfo.path and the path can quickly be injected to get the associated component. adobeDataLayer.getState(event.message.eventInfo.path)
User Story
Currently the WCM core components have a standard for ACDL onClick events to be something like:
Or
But for some reason the cif:addToCart and cif:addToWishList use something like:
This makes it difficult to easily find the associated cif component in a similar fashion as wcm core components. Further, the
@id
field seems wrong when injected into the data layer. The data layer might have:but then the cif:addToCart event will output:
In an ideal world (in line with wcm core components) the expected behavior should be:
Where there is
eventInfo.path
and the path can quickly be injected to get the associated component.adobeDataLayer.getState(event.message.eventInfo.path)