Tutorial Discussion: Implement Adobe Experience Cloud with Web SDK tutorial

Hi @dwright-adobe ,

Thank you for putting together the tutorial instructions. I have two observations: 

Observation 1: 

I am on the step to setup Audience Manager(AAM). I created the DataSource, Trait, Segment, and finally Destination. When I validate the segment if the setup is working as expected. I find "platform_web_sdk_tutorial" cookie is not set. 

The preview has no payload for the cookie. 

My observation is that, the tutorial step asks to setup "platform_web_sdk_tutorial"  as the cookie where as the cookie name  in the screenshot is "web_sdk_demo". I do see the data flowing into AAM. The screenshot of the segment is shared below but I don't see the cookie being set. 

Observation 2: 

Setup of Experience Platform  -   In the step of "Create a Loyalty schema and ingest sample data" " in addition to the two Field groups we need to add "Person Identifier" to add PersonID. Maybe the dictionary in XDM has changed.

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-target#special-parameters-and-the-data-object. 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.

Hello! We are having an issue that I would like some clarity on. 

We enabled Adobe Target using the Web SDK following Adobe's instructions. (See link below) https://experienceleague.adobe.com/en/docs/platform-learn/implement-web-sdk/applications-setup/setup-target

The implementation does not use any customization (scopes, etc.). We are using the Guided Events option for the Target rule so that it fires at the top of the page. The A4T integration was already done prior to migrating to the Web SDK. A4T was used regularly with the previous implementation worked well. We can see that Server-side Analytics tracking is enabled in the logs and both Analytics and Target are enabled in the Datastream. (reference link below)

https://experienceleague.adobe.com/en/docs/experience-platform/web-sdk/personalization/adobe-target/a4t/server-side

However, no data is collecting in Target or Analytics. Every time we create an activity and test it/set it live - we get the same error: "We are having trouble retrieving data for this report. Please contact Adobe client-care if problem persists." 

We aren't sure what to do. I can see the SDID in the schema - but it isn't mapped to anything. I don't know if this is the problem. (And if it is - I don't know what to map it to. I have searched everywhere for documentation on how to map the fields in the Target fieldsets for the schema - but have come up short.) We have put in a ticket with client care - but are not getting anywhere. 

Any help is greatly appreciated!

Good day!
Is anyone monitoring this channel?  The last post was in 2022.

Are there any specific things to take into consideration for HIPAA compliance when setting up WebSDK on your website? I understand all the data labels in the schema, and how Event Forwarding helps restrict data flow to other sources, but anything specific to ingesting the Web data initially into Edge?

Hello,

Are there any recommendations on how to capture data in objects like device, environment, and place context using data elements? Most of the data I want to capture is not auto-populated.

Thanks

Hey @dwright-adobe ,

I just had a question regarding ingestion of the lumacrmid into the dataset. Once we login to the luma page,we get the lumacrmid which is mapped to the identity map but all other values land into the dataset except the identityMap which is empty. Have I made a mistake because I'm able to see identityMap value in the debugger but it's not flowing into the dataset.

Thanks in advance.
Regards
Sushmita.

hi guys, quick question - what are the advantages (and disadvantages) of implementing the web sdk manually (using alloy.js) vs via the the Web SDK tag extension  ? We use the Ensighten TMS, so probably will go with the manual installation, but I would want to know advantages and disadvantages of each method beforehand.

Thanks,

Franc

Hi, I have an issue when i tried to valide a profile, my primary is false and i dont understand why...
Then when i try to find my profile by my lumacrmid i dont find anything...

Thx in advance !

Hi @dwright-adobe 

Hope you are doing well!

I have few queries as follow regarding AEM migration to Cloud Services.

• Do we need a new implementation of Launch to serve cloud our can our existing instance serve both the current on premises AEM and the new Cloud instance AEM?

• any work necessary at the Launch level (or can aspects and rules be reused)?

• time and direction to dev team as they rebuild components and templates on Cloud (net new)?

• script placement/migration/duplication?

• any audit/refactoring you would suggest doing as the cloud will be a blank slate and we won't have to carry technical debt?

Request you to help me with the above queries.

Thanks in Advance.