Tutorial Discussion: Implement Adobe Experience Cloud with Web SDK tutorial
Hi Daniel!
I double checked and the report suite is the same in the datastream and the activity (good thing to know).
Yes - the implementation has two rules. The "target rule" has the guided events/request personalization and the analytics rule has guided events/collect analytics. When I go to a page where an activity is running - I see two event calls. The first one is the decisioning proposition fetch. It looks like this:
The second event is the web.webPageDetails.pageViews event and it looks like this:
I do not see the scope details getting passed in the second call.
Hello again. I have another question that we are having problems getting help with. We have followed the instructions for updating the Target profile according to the documentation here: https://experienceleague.adobe.com/en/docs/platform-learn/implement-web-sdk/applications-setup/setup.... Here are the steps I took:
1. Verified that the data elements I needed for the profile were already created.
2. Created a data element called data.content with the following custom code:
var data = {
__adobe: {
target: {
"profile.utmCampaign": _satellite.getVar("UTM Campaign"),
"profile.utmSource": _satellite.getVar("UTM Source"),
"profile.utmMedium": _satellite.getVar("UTM Medium"),
"profile.siteSection": _satellite.getVar("siteSectionCookie"),
"profile.storeFront": _satellite.getVar("storeFront")
}
}
}
return data;
3. Added %data.content% to the Target rule:
4. Published the library.
It has been weeks - but the only profile attribute that shows up in the Target UI is the siteSection - because it is keyed off a cookie. (I understand why the storeFront variable isn't working - as it is part of the data layer and this variable is not yet available on the page. I tried to solve for this by putting the data.content element in the analytics page view rule - but still get all the same results.) And even when I try to use that attribute - the audiences don't work.
Secondly - I would like to delay saving the records until after the content paint. So I have tried to add "save": false to the end of my custom code in the data element - but it doesn't work. In the documentation it states: "After the content has been visualized, send the proper payload (including the eventToken and stateToken) for the corresponding attributes to be recorded." So I have sent a custom code event after the first send event with the following code (according to the documentation):
alloy("sendEvent", {
"renderDecisions": true,
"data": {
"__adobe": {
"target": {
"profile.utmCampaign": _satellite.getVar("UTM Campaign"),
"profile.utmSource": _satellite.getVar("UTM Source"),
"profile.utmMedium": _satellite.getVar("UTM Medium"),
"profile.siteSection": _satellite.getVar("siteSectionCookie"),
"profile.storeFront": _satellite.getVar("storeFront")
}
}
}
});
I can see this additional event in the debugger - but I still am not getting attributes in the Target UI and the siteSection attribute does not work when used for segmentation.
**I will note that I am using a staging URL in Target - and have quit pushing the changes to the rules up to prod. I have never had problems with testing profile attributes in a lower environment. And none of the documentation for the Web SDK says that rules have to be promoted to production in order to test.
Related Conversations
