I think technically this is already there. You can select Unique Visitors as the metric, and it will get the unique "instances" during the time period you select, or in this case it will only capture one instance per visitor. Instead of reporting on this as unique visitors, just report on it as unique instances, as it will give you exactly what you need. And note that this is only available as of SC v15.

Re: Better ability to sync SAINT classifications across multiple rsids adamhaining - Adobe Analytics

This is a great idea. I would love to apply a classification to any variable on any report suite. Ideally there would be a configuration for the SAINT classification (via FTP) to either:1. Skip the classifications that do not exist2. Create the classifications automatically if they do not exist It would make it flexible and easy to use without having to go and create a classification on a completely separate screen. For that matter, it would be nice to manage and create classifications from the ...

Re: Tracking New vs Repeat visitors without using cookies adamhaining - Adobe Analytics

I agree with what Ben said, have it something that Adobe Analytics does by default, therefore removing the need to do it with the code. It could even be done better where it will count it the same across all devices where the visitorID variable is implemented.

Option to automatically update core code in Tag Manager adamhaining - Adobe Analytics

In Tag Manager you have to replublish a file for it to publish the latest version of the S code. It would be great to have an option to have it automatically updated when a new version comes out so the newest code can be taken advantage of immediately. Of course there should still be an option to manually upgrade it.

Remove newline and whitespace from values adamhaining - Adobe Analytics

Occassionally data will be sent in where there is a space on the end, a tab somewhere in the value, or even a newline character. This causes a value to appear normal in SiteCatalyst when in reality it is not. If it were consistent, it would be fine, but sometimes it is a matter of how a browser interprets and encodes data. This then causes 2 lines to appear in SiteCatalyst that appear the same. To find this out I have to export as a CSV and then open in a text editor to find the problem. My requ...

Cross Visit Marketing Channels adamhaining - Adobe Analytics

For the marketing channels it would be great to see a cross visit pathing report to see which marketing channels users use and in which order. It's great to have first and last touch, but the multi-touch would be even better. I know this is possible with JavaScript (specifically the crossVisitParticipation and channelManager), but it would be so much more effective to easily update via the web interface, not have to manage both the logic in the admin and the JavaScript code

Page View segment on eVars by eVar instances adamhaining - Adobe Analytics

I've recently come to learn that when building a page view segment on an eVar that persists longer than a page view will include not only the instances where the eVar was set on the page, but also all page where the eVar persisted. I can see an argument for both sides, but I would like to see another option in building the segment where we can either select the peristent eVar (current functionality) or just instances of the eVar. This would make the creation of these segments much more intuitive...

Re: List Variable Expiration and Allocation adamhaining - Adobe Analytics

I can even see this becoming a bit more advnaced or complex in the configuration. Similar to merchandising eVars, it can have trigger to tell it what to persist. So in the example of the internal campaigns, we can set any value(s) we want in the list var, and those would be set for that page view, which would be the impressions. Once the visitor clicks on a banner, we can pass an event with the ID for the one campaign, and that event can trigger SiteCatalyst to only persist that value. So if a u...

List Variable Expiration and Allocation adamhaining - Adobe Analytics

List variables are great, but they are not as user friendly as they can and should be. I was really excited when they first came out, mainly to use them for internal campaigns. I would be able to get impressions and clicks all in one variable. I would set all of the internal campaign impressions with an impression event on one page, and then if the user clicked through one of them, it would take over and receive credit for any downstream conversions. However, the whole "full allocation" is what ...

SiteCatalyst Request Callback Feature adamhaining - Adobe Analytics

Currently, there is no option for a callback to occur after the SiteCatalyst image is placed on the page. It would be great to have an optional function that we can configure, and if it exists, it will be executed after the image is successfully placed on the page. I've got some code right now that can detect when the image is on the page, but it uses timeouts and is possible prone to some error. Not sure what the demand is for this, but it would be great to only execute certain actions after th...

Re: Visitor Stitching Should Not Split a Visit adamhaining - Adobe Analytics

I think that's fine, and that can be a caveat to using this. This feature is awesome in what it does with unique visitor counting and persisting variables that have an expiration greater than a visit across devices, but splitting the visit (and thus visit-based reports) when s.visitorID gets set is a pretty big issue. Whatever can be done to not split the visit would be great.

Re: Visitor Stitching Should Not Split a Visit adamhaining - Adobe Analytics

Ben, you are awesome. I was just talking you up with some of my colleages, letting them know how great this site is and that you are the person to thank for it. Awesome!

Re: Visitor Stitching Should Not Split a Visit adamhaining - Adobe Analytics

One other HUGE point on this is the Traffic Sources reports. If I come into the site without ever having logged in, and then I login, the visit gets split, and anything that happens after login will not give credit to the Traffic Sources reports. The visitor is still considered as the same, so any variable (eVar) that persists longer than a visit will still give credit. However, I want to expire many of these variables after the visit, and this bug with using visitor stitching causes a pretty bi...

Re: SAINT setting to treat empty cells as empty adamhaining - Adobe Analytics

Yeah I like this one, but maybe have it be a setting that the user can turn on (not something that has to be done by Client Care).

Re: Visitor Stitching Should Not Split a Visit adamhaining - Adobe Analytics

That's where I'm not sure what would happen with visitor stitching. I'll have to do some testing to see if setting s.visitorID to multiple values treats them as separate visitors. I still think that the pros outweigh the cons with visitor stitching, but it will result in some inflated visit counts.

Re: Processing Rules: Make Search Keywords variable available adamhaining - Adobe Analytics

This one is huge. The main reason I'd say is that the current settings for the search keywords are rather lacking. Putting this in an eVar will open up many more options. It'd be nice to not have to do a hack to get this by using a processing rule (make the variable that captures this just like an eVar by default), or by using a VISTA rule or some JavaScript.

Re: Visitor Stitching Should Not Split a Visit adamhaining - Adobe Analytics

Eric hit it on the head.

Re: Schedule data feeds through an API adamhaining - Adobe Analytics

In addition to scheduling them, it'd be nice to be able to cancel them at any time, especially through a link in the daily email.

Re: Add context/note columns to report suite admin (make it similar to a traditional variable map) adamhaining - Adobe Analytics

In addition, it can even show back end settings such as pathing, merchandising, delimiters for list props, hierarchies, and list vars (not ability to edit though), etc. Another nice feature would be a change log, so you can click on a variable and see when changes were made to the settings, and when it was enabled. You could even export it to Excel, PDF, Word, etc. to deliver as part of a solution so login credentials are not needed. And as a final piece, a change log for each variable would be ...

Better Numeric / Counter Event Setting adamhaining - Adobe Analytics

A newer feature of events (although not documented in the help section or KB) is that you can give a counter event a value greater than one really easy without having to use the products variable. For example, s.events="event1=5". The only problem is that it cannot have a decimal value, and setting s.products with it just seems silly (although I guess it does work). We should be able to set a decimal value for any event. So s.events="1.564". This would be great for many reasons: 1. For a retail ...

Re: Classifications and Pathing adamhaining - Adobe Analytics

I can see why this would be something difficult to do, especially if it were to show the pathing of grouped items. So maybe there can be a new classification for traffic variables, and the requirement is that the classifications will not be grouped, but simply a way to rename the key. Even if the classification has the same name between 2 items, it would not combine them in the pathing report, but simply show something like: Page 1 > Page 1 The reason for this is to show pathing of friendly name...

Classifications and Pathing adamhaining - Adobe Analytics

When a traffic report has classifications created and uploaded, it would be great to be able to have pathing enabled on the classified data and not just on the key or base data.

Visitor Stitching Should Not Split a Visit adamhaining - Adobe Analytics

SC15 introduced an awesome new feature, visitor stitching. However, when this is used (setting s.visitorID), it will split the visit when a returning visitor logs in on another device. If they then return on that same device I think it's working fine, but that initial login is splitting the visit. This is a big deal and is incorrectly counting visits. I can try create some calculated metric, but it would be complex and I can almost guarantee the numbers wouldn't be accurate. What should happen i...

Re: Expire evars manually (within a server call) adamhaining - Adobe Analytics

One of the settings of an eVar is the expiration. You can set the expiration to an event, and then set that event to manually expire the eVar. Are you wanting to have the eVar expire after a visit by default, but then have an extra flag or variable you can set to expire it without having to use an event? I think this would be great, since there may be multiple scenarios where you would want to expire an eVar, and not just after a visit.

Re: Processing Rules Beta Program adamhaining - Adobe Analytics

Agreed. Maybe even some sort of regex functionality (regular expresions make things really nice and quick to reformat). Lots of great ideas are floating around I'm sure.

Re: Even More SiteCatalyst Variables adamhaining - Adobe Analytics

I'd agree with Tim on this one. Having many different report suites and trying to keep the same variables track the same data across report suites is tricky, and when new report suites are added that need new dimensions, you don't want to / can't use the other variables for consistency's sake. I can't think of any one solution that takes up too many variables (social, video, etc), but it's more of using one here and one there. Also, I wouldn't add 75 of each to get a total of 150, since you can'...

Even More SiteCatalyst Variables adamhaining - Adobe Analytics

The upgrade to 75 custom eVars and props was definitely needed, but now I'm needing even more. An extra 25 would be great, especially with eVars.

Re: Add page URL as default breakdown in data warehouse adamhaining - Adobe Analytics

This would be a HUGE help for troubleshooting and auditing since Data Warehouse can utilize segments. Data Feeds are sometimes too much to handle when you want to slice and dice data, especially when having to do event lookups. Although storing it in a prop and/or eVar isn't difficult, it typically isn't setup when you need this and doing historical reporting on the page URL is nearly impossible.

Tracking videos on Roku adamhaining - Adobe Analytics

I'm working on a solution to track videos on the Roku device. I've got an idea on how to do this, but wanted to know if anyone has done it and what they did. Also, wanted to see if anyone from Adobe Product Management had a library for this in the works.

Videos and sending additional variables adamhaining - Adobe Analytics

Currently if you set Media.trackVars in a video, it will only send data for the first server call from the video, when it starts playing. Any additional calls, such as with the milestones or X number of seconds, will not have the data outlined in the Media.trackVars sent with it. My request is that all variables specified in Media.trackVars and Media.trackEvents are sent with every media request without having to do this using Media.monitor. This would not only make sense, but make implementing ...

Likes given to

User

Count

Likes from

User

Count

Guidelines

Cookie preferences