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

aaronc10
aaronc10
Offline

Badges

Badges
8

Accepted Solutions

Accepted Solutions
1

Likes Received

Likes Received
3

Posts

Posts
7

Discussions

Discussions
0

Questions

Questions
7

Ideas

Ideas
0

Blog Posts

Blog Posts
0
Top badges earned by aaronc10
Customize the badges you want to showcase on your profile
Marketing channels not exhaustively filtering tracking code - Adobe Analytics 03-09-2018
Hi!Here's our problem: When we breakdown the "Natural Search" dimension by Tracking Code, there are still rows other than Undefined even when the "Paid Search" rule set is above it. For example, even when the filters are set to scoop for tracking code containing "sem" in Paid Search (order above that of Natural Search), there are still tracking code rows with sem in Natural Search.You can see from the first picture that most the 'sem'-containing tracking code is correctly bucketed as Paid Search...

Views

609

Likes

0

Replies

0
Re: Data elements in SPA when next page JSON is undefined - Adobe Experience Platform Data Collection 03-05-2018
Thanks Jantzen. Not a big deal since we can just assign digitalData directly to props/evars. Thanks again.

Views

1.2K

Like

1

Replies

0
Re: Data elements in SPA when next page JSON is undefined - Adobe Experience Platform Data Collection 29-04-2018
aseelund​, tried but still doesn't work.

Views

1.2K

Likes

0

Replies

0
Re: Data elements in SPA when next page JSON is undefined - Adobe Experience Platform Data Collection 11-04-2018
Thanks for replying Jantzen. Unfortunately our test servers are in an internal environment.I am not sure why the code doesn't work. To test it, I called _satellite.setVar('DE abc') first in a page where digitalData.abc has a value. I then navigated to a page where digitalData.abc is not populated and called _satellite.setVar('DE abc'). The return result was still the value of digitalData.abc. I then navigated to another page where digitalData.abc has a different value (say value B), called _sate...

Views

1.2K

Likes

0

Replies

0
Re: Best Practices: Tracking search terms and avoiding extra server calls - Adobe Experience Platform Data Collection 09-04-2018
IMHO, best practice is to have those variables (search terms, number of results, etc) in the data layer of your search results page. Then you set them accordingly in your s.t() call on the search results page. Using this approach, you remove the need for the s.tl() call.If you can't do the data layer, you can create a rule to store values in data elements/sessionstorage. On your search results page, call and set those values together with the s.t() call. This is more messy but ensures that you o...

Views

1.3K

Likes

0

Replies

0
Data elements in SPA when next page JSON is undefined - Adobe Experience Platform Data Collection 09-04-2018
We are running into issues where a JSON is undefined in a subsequent page by design.Suppose a data layer in an SPA:Page 1: digitalData.abc returns "label X"Page 2: digitalData.abc returns undefinedThe data element (DE) that maps to it would:Page 1: DE returns "label X" !Page 2: DE returns "label X"What's the best way, if it's possible, to make the DE return undefined in page 2?I tried converting the DE to custom code (below). Doesn't work.if(digitalData.abc == undefined){ return undefined;}else ...

Views

3.4K

Likes

2

Replies

9
Likes from