Hello,What are the reasons the Segmentation service (both is build and in sharing attributes for Destinations) thinks there's no data in a dataset column?  The Dataset & Schema are enabled for Profile and segmentation can see data in other columns. I'm using the OOTB Loyalty Fieldgroup with no modif...

Hello, We are trying to convert some Adobe Target segments to RTCDP and trying to figure out URL based segmentation where the visitor only qualifies when they are on a specific page - but only while on the page - not if they visited the page during some point in the past.  For example, they should q...

Thanks everyone, I figured it out which was in-line with the responses above.  While the solution was related to the out-of-the-box personalAddress attribute from the Standard fieldgroup being NULL, this value was always null when we set this up back in October and it worked just fine then.  I copie...

Hello, I am testing my previously working Journey and while the test profile enters and exists the journey successfully, the email fails due to a "No Email Address Found in Profile" Error.  The confusion is AJO did in fact find the profile because the messageFeedback event exists in the Events tab (...

But the same cname works just fine with at.js.  But the new ECID every page load seems like a WebSDK bug - using a cname shouldn't cause a new one every page.

Yes, domains are the same; it was getting a new ECID on every page. I think I found the issue, using a cname in the WebSDK in Launch is is causing it to get a new ECID each page.  When I reverted back to the default edge.adobedc.net domain, the ECID stopped changing page-to-page and the Profile scri...

Thanks, still doesn't work across pages; the Profile Script value is only returned on the page in which it was set.  Here's how anyone can test it. Create a monitoring campaign that doesn't do anything but push a console log.  This is so we can see the response tokens (which the profile script is a ...

No, in the Experience platform Web SDK entries....there are a number of posts in this forum indicating the same behavior.  Double entries per page view, having to click multiple times in the Post Body to see the data (when previously all of the data appeared automatically), etc.

Everyone seems to be having this issue since the latest debugger release.  No word from Adobe confirming the issue nor a notice of rolling back/fixing.

Hello, After a Purchase event, we'd like to update the visitor's "Loyalty Points" by taking the existing value in the Profile and adding the Purchase amount to it.  For example, if the existing Loyalty Points value in the Person dataset is "100" and they purchase something for "59.99", we want to wr...