04-02-2021
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report
@markusb54298925 I was able to investigate this better after I got the URL. What I observed is that when I go to a product page I get the entity values along with other parameters. Then when I go back or to another page without the same parameters, that the adobe target still has these persisting parameter values. So if that is the issue I have a solid understanding now of what is going on.
I then thought through some possible options. I tested these both by using developer tools to intercept the Launch script on your site with a local one, when I say below I created a rule, I mean I coded it in the cloned Launch script on my local.
Option1 - Create a separate rule and have it execute only on pages where pageData.page.pageType == product, I called in AT - Product page. Updated the existing rule(non-product page) to execute only when pageData.page.pageType != product. I observed on product pages the correct rule(product page) executing with the expected Target parameters. I then navigated away from a product page to a category page. The non-product page Adobe Target rule fired, and still the parameters from the product page persisted and were sent in. This is a gap/defect in my mind.
Option 2 - I cleared the launch script I had before and started with a fresh copy of the current one. I updated the current condition that looks for a bot detection flag and added additional if else statement. I am referencing it below. As you can see I am using targetPageParams to set the product entity data when on a product pageType, and when not I clear this information and start fresh. The other parameters are still being set via the out of the box Launch option. This is what I originally recommended and while it works well, I believe I better understand now why this would be more work for the team because we don't always have these values so you would have to create logic to check for different page types possibly.
if(pageData.page.pageType == "product"){
_satellite.logger.log('AT: Product Page');
targetPageParams = function() {
return {
"entity.id" : _satellite.getVar('productIdCurrent'),
"entity.name": _satellite.getVar('target_pname'),
"entity.brand": _satellite.getVar('target_pbrand'),
"entity.catLevel1": _satellite.getVar('productCat1'),
"entity.catLevel2": _satellite.getVar('productCat2'),
"entity.catLevel3": _satellite.getVar('productCat3')
};
};
return true;
}
targetPageParams = function() {
return {
};
};
return true;
}
My Recommendation -
I think option 2 is a possible option still in the interim while Adobe can prioritize a new feature. It might require some work right now but it can close the gap with your current issue which is impacting the recommendation engines understanding of what is actually being viewed and conversion. I would follow up with client care, post this issue as well in the the AEP - Launch community room and I would also open an issue in the github project for Launch, it looks like it is monitored, link below.
https://github.com/AdobeDocs/launch.en
Hope this helps!