Initially, I was seeing Segment C > Segment A + Segment B. I went back
to the project the next day, and Segment C < Segment A + Segment B. I
can't explain why this happened, but am glad that this resolved itself.
I've tried Segment C as both a visit container with the Segment A and
Segment B hit containers inside (using OR), as well as a hit container
with the Segment A and Segment B hit containers inside (using OR). The
visit container approach results in a slightly greater visit count.
Hoping the community can help me out with a segment that I'm trying to
build. I have two segments, Segment A and Segment B. These segments use
hit containers. When I create a third segment, Segment C, that says
"either Segment A or Segment B" and apply all segments to the visits
metric, the number that appears for Segment C is greater than the sum of
Segments A and B. This shouldn't be possible. Any ideas as to what is
going on? EDIT: Both Segment A and Segment B use hit containers, and
both req...
This will work as long as you leave the "Include Unspecified (None)"
option checked in the Analysis Workspace table. If you uncheck it and
the eVar is not set on every call (i.e. there isn't a value set in 100%
of visits) then the Total and Grand Total values will be different.
Adobe uses the "Total" as the denominator rather than the Grand Total,
so you'll wind up only comparing an eVar value to the total visits with
the eVar value.
If you are building this in Analysis Workspace, by default metrics
included in a Table show both numbers and percentages. If you hide the
Unspecified value, the percentages appear should show you the Percentage
of visits with this error. What it won't do, however, is show this in a
different column. If you want a separate column called "Percentage of
visits with this error", you could create a calculated metric that only
includes visits and is called "Percentage of visits with this error".
Once ...
While I agree that Ad Hoc is superior to Analysis Workspace when it
comes to speed and certain functionality, you'll need to plan to not be
able to use it anymore. It's EOL is March 2021. Some Ad Hoc
functionality, such as being able to export large numbers of rows, has
recently been added to Analysis Workspace.
You're going to have to head to Stack Overflow for this. You're going to
have to sift through everything that happens in the console when an
auto-translator is used, and this is going to vary between browsers. I
recommend
https://stackoverflow.com/questions/62998768/detecting-auto-translation-event-in-microsoft-edge
as a jumping off point.
Unfortunately I cannot provide the actual key values, but "Widget
Makers, Inc." is a made-up value that has a similar format (i.e. commas
and periods) that is currently not working in the classification file
uploads. Nothing has been altered in the first four header rows of the
classification template, and v:2.1 was the default version value. Note
that the values being used to classify the key do not contain any
special characters.
I am having trouble classifying keys for an s.eVar that contain special
characters. For example, a key may look like this: Widget Makers, Inc.
I've made sure that the classification template file uses "v:2.1" and
not "v:2.0", as indicated in
https://docs.adobe.com/content/help/en/analytics/components/classifications/faq.html,
but still get a message that the classifications are not uploaded. I've
tried placing quotation marks around the keys, but this also has had no
effect. Any suggestions from...
While that is a possibility, stakeholders received scheduled reports
(PDFs) with the graphs also empty. That is unlikely to be caused by a
browser extension.
Most of the line graphs in my Analysis Workspace projects are now blank,
though the underlying data is there and tables don't seem to be
impacted. Refreshing the project doesn't fix this issue. Has anyone else
experienced this? I'd like to know if this is a known issue that Adobe
is working on fixing, or if this is outside of Adobe's control and I
need to update hundreds of charts.
The recent Adobe Analytics UI update changed how the site navigation
menu options function. Previously, clicking on a menu category (e.g.
Tools) would direct you to a page showing all items available in that
menu, and hovering your mouse over the menu category would results in a
list of options being displayed. Now clicking on the menu item opens the
list, but does not take you to the category main page. This adjustment
hasn't negatively impacted my experience with the site. The change that
has ...
That's an interesting approach. I had already created classifications
for price groupings (e.g. $250, $500, etc. increments), and with prices
up to $100,000 I may increased create these calculated metrics by group.
Not quite the ideal, but it's worth experimenting with. Hopefully Adobe
figures out a replacement for numeric classifications.
My client captures price in an s.eVar, and I am trying to figure out if
there is a way to use the captured value in mathematical operations
within Adobe Analytics. I can export the data and treat the text string
as a number using Python or other programming approaches, but would like
to be able to handle this within Adobe because I could include
calculations in Workspace. Since numeric classifications have been
removed, I'm not sure if what I want is even possible. Does anyone have
a recommendat...
I'm running into the same issue, and I have all admin permissions. It is
possible that this is an issue with the latest release of Report
Builder, as another computer I have is running an older version of
Report Builder and isn't having any problems.
Have you created classifications for the Product variable? I've found
that this has been a big help when it comes to handling dimensions with
a ton of values, such as Campaigns. For example, let's say that the 300
products you referred to are "T-shirts". You could create a
classification called "Product Category", and use "T-shirts" as one of
the values when you upload the classifications. This will allow you to
create a segment that will limit the Analysis Workspace table to only
show "T-shirts...
One way to pass visitor IDs between properties is appendVisitorIDsTo
(https://docs.adobe.com/content/help/en/id-service/using/id-service-api/methods/appendvisitorid.html).
Note that you can either store this in a variable (e.g. an s.eVar), or
could try to set the ID being passed as the ID for the second
application.
Has anyone else run into problems with the "Verify Your Identity"
feature when trying to log into Ad Hoc? I've cleared all temporary files
from Java, but for some reason Adobe won't accept the verification code
that they send to my phone/email. As soon as the last digit of the six
digit code has been typed in, the numbers all reset. I've put in a
support ticket, but they weren't able to figure it out. Hoping that
someone from the forums has a solution.
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. Edit: the s.prop classifications appear in Ad Hoc,
just not Analysis Workspace. All product permissions have been granted,
and I have full admin rights.
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 one or more segments via the checkbox, click the
"Share" icon at the top of the page, and then choose the
individuals/groups/all option. I did not receive an email about a 75
segment limit, and don't ...
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 the aforementioned date segments doesn't shift everything
back a month. What probably needs to happen is Adobe would need to add a
relative option to the Date Range Builder interface. Currently, you ...
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 sure, and I've wound up creating reports in Tableau to
allow for choose-your-own-adventure date range comparisons.
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 need to be capturing the IP address in a variable, as
this isn't an out-of-the-box option). If you haven't created a virtual
report suite already, you can get some decent information at
https://docs.ad...
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 address belongs to via the different lookup tools
available online.
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.
The reason I'd avoid using a bot rule is that the traffic isn't actually
from a bot. Instead, it's from someone looking at an ad on Snapchat and
the destination URL for that ad loading in the background. You may wind
up advertising on Snapchat in the future without the pre-load function
activated, and would likely want to know if people are actually clicking
on the ad and landing on your site. If you label the traffic as a bot
you wouldn't see those visits. The reason I excluded the Snapchat
use...
