trevorpaulsen

- I'd be happy to sit down in person and talk through it... - Adobe Analytics

@Jennifer_Kunz wrote: These are the questions that remain AFTER I've spoken to account reps:) (which, in general, as a consultant, I don't have much access to, though a few have kindly met with me and answered some of my questions and helped me understand the different options for purchasing, just not the nitty gritty of how it all works and what you can do if you aren't purchasing AEP-the-CDP). Most of the Adobe folks I talk to have had a hard time conveying the real boundaries of each tool ind...

585

Re: Make 'Previous Page' & 'Next Page' Dimensions in Workspace - Status changed to: Investigating - Adobe Analytics

Love this idea. While this isn't something that's very feasible for us to do in standard Adobe Analytics, it is something we're looking at doing with Customer Journey Analytics using a new feature we're working on called "Derived Dimensions". To learn more about CJA check out this page: CJA Spark Page

1.8K

Re: Metric Filters - Status changed to: Investigating - Adobe Analytics

1.3K

Re: Increase variable character limits for s.pageName and s.prop - Status changed to: Delivered - Adobe Analytics

While this isn't something we can feasibly offer in standard Adobe Analytics, we currently offer this capability in Customer Journey Analytics. You can learn more about Customer Journey Analytics here: CJA Spark Page

289

Re: Segmentation: Bot Traffic Identification & Exclusion Tool - Adobe Analytics

Currently, we have a number of exchange partners who offer sophisticated bot detection capabilities for Adobe Analytics. I'd recommend checking out what our partners have to offer such as this one.

153

Re: Multiple Dimensions columns in Adobe Workspace - Status changed to: Accepted - Adobe Analytics

860

Re: Multiple Dimensions columns in Adobe Workspace - Adobe Analytics

Update here - this idea is awesome, but after some deeper research not very feasible in standard Adobe Analytics today. The good news though is that we're looking into ways we can do this within Customer Journey Analytics and we think we've identified a great way to accomplish this use case via a new feature we're working on called "Derived Dimensions". If you want to learn more about CJA - check out this link: CJA Spark Page

863

Re: [WORKSPACE] Sorting by dimensions - Adobe Analytics

The good news is that we actually now support this in Customer Journey Analytics for all dimensions. The bad news is that for technical reasons this isn't possible in traditional Analytics. For more information on CJA you can check out: CJA Spark Page

419

Re: New Sub-Hit Segment Container - Adobe Analytics

Hi @luekl - unfortunately, this is not currently on our near term roadmap. That said, it is something we're researching for the future. Thanks for your feedback.

13.8K

Re: Workspace:New flow visualization - how users navigate between 2 points - Adobe Analytics

In the works! Should be coming out early this year.

11.1K

Re: Attribution IQ Custom Lookback window - Adobe Analytics

Hey Scott, this is definitely something we're aware of and we're currently working on a better method for more granular control over the lookback window. As a short term workaround for your use case set the reporting date range to start on Dec 31 (as you mentioned), but use a segment to filter the results to just Jan 1 - Jan X (using the orange "Day" dimension as a filter). That'll force the report to use Dec in its lookback window, while still only reporting values that happened in Jan. Perhaps...

5.6K

Re: Workspace:New flow visualization - how users navigate between 2 points - Adobe Analytics

Fantastic feedback - we're looking at improving flow, so your comments couldn't have come at a better time. I'll be sure to take this back to the team.

11.1K

Re: Add regex to Comparison Operators for Segments - Adobe Analytics

Hi, thanks for the suggestion! We actually did an internal POC for this, but it turns out that regex engines were too slow for us to return reports in a timely manner. We'll keep looking at it though, thanks for posting!

4.9K

Re: Attribution IQ & Calculated Metrics - Adobe Analytics

The histogram is based on the instances metric of your dimension rather than the metric itself. It's simply a view of how many touches users have to your dimension in general.

7.3K

Re: Attribution IQ & Calculated Metrics - Adobe Analytics

Thanks for the feedback. For what it's worth, you can reproduce any and every visualization in the Attribution Panel yourself in a blank panel. We made panels such that a user could reconstruct them manually if they wanted to. There's no reason you couldn't look at the same histogram or Venn, etc. that we prepopulate in the panel.Granted not quite as convenient, but still doable with a few extra minutes of time.

7.3K

Re: Stop Structuring Contracts Based (directly) on AA Server Call Volume - Adobe Analytics

I like your idea! Certainly not an easy change by any stretch of the imagination, but I'll take this feedback back to the team. Last question for you - if we charged not only by hit count, but by size of hit (I guess that'd be similar to volume or GB pricing) would that help ease the strange implementation incentives?For example, would you prefer to send over lots of hits that don't have as much data in them vs not as many hits but they have lots of data? We experimented with this idea years ago...

6.7K

Re: Attribution IQ & Calculated Metrics - Adobe Analytics

Great point. The reason for this is because we have no way of knowing how to apply an attribution model from outside of the calculated metric builder. For example, if you had revenue / orders and you applied "Linear" to it - does that mean (linear revenue) / (linear orders) or (linear revenue) / orders or revenue / (linear orders). Adding more metrics, segments, calculations, etc. makes it hard for us to know how to apply the model. Does this make sense?

7.3K

Re: Stop Structuring Contracts Based (directly) on AA Server Call Volume - Adobe Analytics

Very interesting idea/comment.If we did away with billing by server call volume, do you have a suggestion on how we could structure an alternative pricing model that wouldn't have bad incentives?

6.7K

Re: New Sub-Hit Segment Container - Adobe Analytics

Ah gotcha - a segment would include both dogs and cats, a breakdown of "small" by product would only give you "dogs" though. Sub-hit segmentation is a common feature request - I'll pass this along to the team.

20.1K

Re: Visitor Participation for Workspace - Adobe Analytics

I should also mention that Attribution IQ will be available to customers on the new SKUs: Foundation, Select, Prime, and Ultimate. Also fwiw, participation has always been available in calculated metrics which surfaces in Workspace.

8.1K

Re: Visitor Participation for Workspace - Adobe Analytics

This is coming with the release of Attribution IQ this month! Look for it in the UI on the morning of the 20th.

8.1K

Re: Virtual Report Suites To Support Different Currencies - Adobe Analytics

Hi David, the tricky part there is that the currency conversion rate changes every day - keeping track of the historical conversion rates and applying them properly each day isn't as trivial as it sounds!

8.0K

Re: New Sub-Hit Segment Container - Adobe Analytics

I'd recommend looking into merchandising eVars!Merchandising Variables

20.1K

Re: Analysis Workspace Feature Request - Details Table - Adobe Analytics

Thanks Craig! I've already forwarded the email you sent me previously to the team. The problem you've outlined resonates with me.

5.6K

Re: Improve VRS (Clalculated metrics / Activity Map) - Adobe Analytics

Do you mean that the activity map metrics/dimensions do not appear as items in the VRS curation list? Also, those segments duplicates? Did you include all of them in the original VRS?

2.6K

Re: Detection of in-app browsers (eg. Facebook) - Adobe Analytics

This is a great question - would you mind posting a screenshot of the report you're referring to (or something that shows how you'd like the data to appear in AA)?

8.4K

Re: Make Bot rules retroactive - Adobe Analytics

I'd be careful about sticking IP address into a custom variable - however, it could technically work as you've described. Have you tried my suggestion of filtering out Linux, or unknown browsers?Another thing to try is using customer attributes for this (actually passing the cookie ID in as an alias ID using setCustomerID). I've seen some customers do bot analysis offline (or find the bad IP addresses) and classify the bad visitors as bots. This works retroactively as well.

6.0K

Re: Virtual Report Suite - "do not show me this alert anymore" tick box needed - Adobe Analytics

Hi Jakub, thanks for the suggestion! Can you explain your use case a little more deeply? Do you have users that frequently create segments/calc metrics that they aren't able to include in a VRS?

4.3K

Re: Adobe Analytics and ITP - Adobe Analytics

The change should go out this week.

17.4K

Re: Make Bot rules retroactive - Adobe Analytics

Hey Jen, thanks for the suggestion! Have you looked at using a virtual report suite for this? I've found that creating a segment filtering out the "Linux" or "Not Specified" operating systems or if the browser contains "unknown version" usually gets 75% to 80% of bot traffic for most sites.If you need something more serious, you can look at some solutions in our exchange portal:ShieldSquare PerimeterX Bot Defender for Adobe Analytics

6.0K

Likes given to

User

Count

Learn

Documentation

Community

Support

Resources

Adobe account

Adobe