adobe / adobe/adobe-client-data-layer
Product String attribute and User Object not picked up in ACDL
- Dominant language
- JavaScript
- Stars
- 122
- Forks
- 28
- PR merge metrics
- No merged PRs in 30d
Description
Client has implemented ACDL on their dev site, and in the products object - one attribute of "actualPrice" is not retrieved in the adobeDataLayer.getState(). The rest of the product attributes return and are working. There is also a node of "user" that does not return yet is set correctly.
### Expected Behaviour - All product attributes should be picked up and "user" object should be picked up
### Actual Behaviour - Product string is missing "actualPrice" and "user" object completely missing in data layer output
### Reproduce Scenario (including but not limited to)
anytime a user views a product while logged in
#### Steps to Reproduce
Login to the client's dev site using following credentials:
Login: [tom.mintun@wescodist.com](mailto:tom.mintun@wescodist.com)
Password: Wesc0Password!
dev site URL: https://dev.eecol.com/content/eecol/ca/en/products/product-page.html/eecol-ltl-ledbar34-40k.html?page=1
Note: if you are not logged in, prices will not display and you will not be able to replicate the "actualPrice" issue described above. Navigate to a Product details page. In the console, view the adobeDataLayer object and note the user object and actualPrice are present and set correctly. Now view the adobeDataLayer.getState() object and note the actualPrice does not have a value and user object is missing.
#### Platform and Version
Launch, ACDL extension version 2.0.3
#### Sample Code that illustrates the problem
#### Logs taken while reproducing problem
Contributor guide
Research direction
Start at the adobeDataLayer.getState() entry point and reproduce the discrepancy on a product detail page using the reported ACDL 2.0.3 setup. Compare the product data and user object in adobeDataLayer with the getState() result. Done means actualPrice and the user object are both retained in the getState() output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100