Anyone else not seeing Traffic (i.e. s.prop) classifications appearing in Analysis Workspace? I see Custom Conversion (i.e. s.eVar) ones for our different variables, but for some reason s.prop ones don't show up as an option. We created the classifications several days ago, and the s.prop has values...

I think that this checkbox has more to do with making the segment available to other products in the Experience Cloud (e.g. Target), and less to do with the segment being made available in other report suites. To share segments to a wider audience, you'll need to go to Components > Segments, select ...

The main issue is that Date Ranges use today's date as the end date. For example, I have segments for "Last week", "Last month", and "Last Year". Because these are built in Date Ranges, the end is always today. If I change the panel date range from the default (This month) to December 2019, applying...

My understanding is that "current" will always refer to the day, week, month, quarter, year associated with today's date. This means that it will likely be impossible to allow a user to select a date and then have all the comparison data update to be relative to that selected date. It's a bummer for...

I don't think that the traffic can be removed, but it can be filtered out using segments and a virtual report suite. How accurate the segments are depends on your implementation, since excluding all visits from South Korea may not be as ideal as excluding visits from particular IP addresses (you'd n...

If your account access level allows you to submit a support ticket, I'd recommend sending this issue to support. Adobe staff look at the forums, but they may not catch this particular issue: namely, that preview dates are not matching the date conditions in the Date Range Builder.

You could capture the IP address in a variable and then look for IP addresses accessing your site at unexpected rates. Most of the time you'll see bursts of traffic from particular IP ranges. Unfortunately, this is as far as you can get from within Adobe Analytics, and you'll need to see who the IP ...

The user will also want to make sure that Paid Search Detection has been setup properly.

You can probably create an s.event for this, with the variable triggered when the button is clicked. This will allow you to create a segment in which the s.event exists after a transaction, and another segment in which the s.event does not exist after a transaction.

Rather than using "dog.com", make sure to use ".dog.com". The former would, for example, consider the domain "hotdog.com" as internal as well, which is probably not what the user wants.