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

Jennifer_Kunz
Jennifer_Kunz
Offline

Badges

Badges
25

Accepted Solutions

Accepted Solutions
0

Likes Received

Likes Received
331

Posts

Posts
88

Discussions

Discussions
77

Questions

Questions
11

Ideas

Ideas
52

Blog Posts

Blog Posts
16
Top badges earned by Jennifer_Kunz
Customize the badges you want to showcase on your profile
Make dev and staging libraries default to upstream - Adobe Experience Platform Data Collection 06-03-2019
Currently, if there is no library assigned to a dev or staging environment, it 404s. This can (reasonably) bother developers and break analytics testing on dev/staging/QA servers.Ideally, if an environment does NOT have a library currently on it, it would just use whatever is currently upstream in prod.

Views

9.2K

Likes

17

Replies

4
Re: Make the data element field wider (Analytics Extension) - Adobe Experience Platform Data Collection 28-02-2019
This is also true for on the Data Element creation page:

Views

7.8K

Likes

0

Replies

0
Re: Toggle for Custom VRS Components auto inclusion/exclusion - Adobe Analytics 04-02-2019
jen.lasser Alas, I have some followup- I'm doing a training on Wednesday and have given a training account the same sorts of access/rights that my users will have, so we see the same things. And now I see that without fuller rights to Virtual Report Suite admin, I don't even GET the "add new component" tick box-This is what our users-in-training will all see when I have them create a new calculated metric. It's icky enough, I'm going to give up on using the VRS for now:(

Views

16.0K

Likes

0

Replies

0
Re: Toggle for Custom VRS Components auto inclusion/exclusion - Adobe Analytics 04-02-2019
Note this is related to/a duplicate of Have components addition in Virtual Report Suites be "exclude only" .

Views

16.0K

Likes

0

Replies

0
Re: evars and props best practices - Adobe Analytics 04-02-2019
I'd say duplicating things in an eVar AND a prop used to be a common (even a best) practice but agree with Gigazelle​ that it isn't needed as much anymore, because Adobe is continually removing barriers that used to exist between "traffic" and "conversion" information. Because they aren't needed to get around those barriers any more, I'd say I actually prefer things NOT to be duplicated- having multiple dimensions with the same name can be really confusing to users.As already mentioned, eVars ca...

Views

8.0K

Likes

4

Replies

0
Re: Toggle for Custom VRS Components auto inclusion/exclusion - Adobe Analytics 18-01-2019
Thanks for looking into this and responding, Jen! That "component may not appear" message does help a bit, though the messaging is a bit weird (something more along the lines of "would you like to include this component in the VRS? Yes/No" would be much clearer, and if I'm in a VRS it should default to "included", since the assumption is I created the thing because I want to use it here) but I still feel like for bigger orgs particularly, it's going to be a mess to maintain.

Views

16.0K

Likes

0

Replies

0
Re: Toggle for Custom VRS Components auto inclusion/exclusion - Adobe Analytics 17-01-2019
Yes, this is a really big issue for anyone using a Virtual Report Suite to "curate" their components. If I create a new segment, not only do I need to do the standard sharing to make it accessible to my peers, I have to also go into the VRS editor and make sure that segment is on the "include" side. It seems I have to do this even if I DON'T want to share that segment and just use it myself within the VRS.

Views

16.0K

Likes

0

Replies

0
Re: Have beacon URL update on Single Page Apps - Adobe Analytics 15-01-2019
On another note, this also impacts getQueryParam functionality- I believe s(.Util.)getQueryParam takes advantage of s.pageURL, so unless you're updating s.pageURL currently, you might inflate tracking on query params.

Views

8.0K

Likes

0

Replies

0
Allow for nested conditions in Launch rules - Adobe Experience Platform Data Collection 09-01-2019
In addition to the need for an "OR" operator (Allow for "OR" conditions in rules ), being able to nest conditions would be very powerful. For instance, I just did this custom code condition for a client:This would allow us to move out of custom code conditions, and possibly reduce redundant rules folks might resort to make.

Views

4.8K

Likes

27

Replies

2
Allow for "OR" conditions in rules - Adobe Experience Platform Data Collection 09-01-2019
Currently, multiple conditions seem to always take an "AND" operator- for anything "OR", I go to custom code. It would be very helpful to be able to use "OR" conditions.For instance, if I needed to have a condition like "if the pagename is 'home' OR the page type is "product details", I would have to resort to a custom code condition, or creating multiple rules.

Views

12.5K

Likes

43

Replies

7