Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

jgrubbs
jgrubbs
Online

Badges

Badges
20

Accepted Solutions

Accepted Solutions
8

Likes Received

Likes Received
21

Posts

Posts
37

Discussions

Discussions
2

Questions

Questions
35

Ideas

Ideas
0

Blog Posts

Blog Posts
0
Top badges earned by jgrubbs
Customize the badges you want to showcase on your profile
Re: How to setup a dimension - Entry Page URL? - Adobe Analytics 25-12-2021
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

Views

499

Like

1

Replies

3
Re: "CORE" namespace in XDM identityMap - Adobe Experience Platform Data Collection 21-12-2021
@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 check all the records. Konductor is indeed setting the ECID namespace in the records as I expected it would. However, it was those handful of records with "CORE" that were a mystery... until now I wish deta...

Views

226

Like

1

Replies

0
"CORE" namespace in XDM identityMap - Adobe Experience Platform Data Collection 17-12-2021
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 where the xdm.identityMap is missing the ECID namespace, but instead has a namespace called "CORE" which does have what appears to be a legit ECID set in the id field. It is a 38 character numeric express...

Views

245

Likes

0

Replies

2
Re: analytics for target and a page report not matching up - Adobe Target 16-12-2021
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 around I found it was in fact due to an intermittent sdid problem. In our implementation, we originally used the default at.js behavior which has viewsEnabled set to true. This effectively generates 2 m...

Views

233

Like

1

Replies

0
Re: Target page params as array - Adobe Target 10-12-2021
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'));

Views

332

Likes

2

Replies

1
Re: Profile Script : Get Param value from referringURL - Adobe Target 06-12-2021
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

Views

141

Likes

2

Replies

0
Re: Unintended extra pageviews using WebSDK - Adobe Experience Platform Data Collection 06-12-2021
Here is the recommended short term solution, intended to be used as part of the alloy onBeforeEventSend callback. I've just implemented something based on this and it has alleviated the extra pageviews for now, throwing the "phantom" hits into the Custom Links reporthttps://gist.github.com/jfkhoury/b390688267854c75d75245ed0c12253b

Views

471

Like

1

Replies

2
Re: Unintended extra pageviews using WebSDK - Adobe Experience Platform Data Collection 06-12-2021
Hi there... Yeah I did confirm it was the Target calls generating the extra pageviews. I tried setting tinkering with the pagename, both by ensuring that xdm.web.webPageDetails.name was undefined and even setting up a processing rule to delete Pagename, neither of which was successful unfortunately. I tried setting xdm.web.webPageDetails.pageViews.value to 0 and even -1, both of which failed as well. I've been in contact with Adobe and our CSM, and have been informed that a fix is in the works. ...

Views

482

Likes

2

Replies

4
Unintended extra pageviews using WebSDK - Adobe Experience Platform Data Collection 02-12-2021
Hello gang... We've been running with the WebSDK for a bit now and all has seemed just fine. We've been impressed with the performance as well as the relative ease of implementation. Note that we use the NPM module directly, incorporated into our front-end build process. Throughout testing as well as live data in Analytics nothing has seemed amiss. However in looking at our raw Data Feeds out of Analytics, there are extra "phantom" hits that are being treated as pageviews. There are few if any a...

Views

517

Likes

2

Replies

7