Hello all and happy new year. Just a heads up for a critical issue I had to fix here on Sunday morning.  The vast majority of our sites and properties are unaffected because we're using the WebSDK and all new code, however there are a few places where we have some old legacy AppMeasurement.js stuff,...

Actually, I feel kind of silly because I just thought of a better solution... holiday brain I guess.I could just cram the whole comma separated list of values into a single array element, as in:_experience.analytics.customDimensions.lists.list1.list = [ { value: 'a,b,c,d,e' }]And then map "a.x._expe...

Hello all, It seems that listVars are not automatically mapped to Analytics when ingested from the Adobe Edge. _experience.analytics.customDimensions.lists.list1.list = [ { value: 'a' }, { value: 'b' } ... ] This validates just fine in the dataset, but "list1" in Analytics doesn't get any love. Is t...

Hi @VinayC that is a nice part about using the Processing Rule I described. You don't have to add the eVar into your front end code. Page URL is automatically sent on every beacon, so you can copy that value into an eVar in a new Processing Rule. Here is an example where an eVar (eVar54) called "Pag...

I suppose you can configure the eVar for "Original Value (First)" attribution, and have it expire on Visit.Then in your processing rules, you can map PageURL to that eVar.In theory, the first PageURL value encountered in a visit will be stored and persisted in that eVar until the visit expires 

@pradeep_nextrowAh cool that answers my question about the elusive CORE namespace   The format does match the legacy aam_uuid as well, which is also a 38 character numeric string I wrote some tools to retrieve the ingested batch files from AEM via the API in parquet format and wrote a parser to chec...

Hi gang, I have what I hope is a simple question for someone who has Edge and Konductor inside secrets.We are currently in a RTCDP/AEM implementation project with a team of focused Adobe consultants. As they validate our data sources and our stream of events via the WebSDK, they are seeing hits wher...

Hi @Maple-Michelle1 they are referring to the marketingCloudVisitorId that is sent in the request payload to Target--ensure that matches the "mid" query string parameter in the server call to Analytics. I had an experience a while back with a similar issue (reporting mismatch). After much digging ar...

I suppose you could try passing the array as a stringified object, such as: return { userGroups: JSON.stringify(userGroups) }; And then parse it as an array in the profile script:var userGroups = JSON.parse(mbox.param('userGroups')); 

I believe you can use: referrer.param('some_parameter'); https://github.com/AdobeDocs/target.en/blob/master/help/c-target/c-visitor-profile/variables-profiles-parameters-methods.md