You will want to double-check and make sure the users not only have
access to the report suites listed, but that they also have access to
each dimension and metric they are trying to pull in via Report builder.
Also, it may be helpful to re-login to the client after permissions have
been updated. If you still see problems with permission errors, then I
would definitely recommend reaching out to Client Care to get an
incident logged for this issue.
If you cannot accommodate any additional delay in your form.submit()
call, then you will not be able to send the data in on this call via
standard means. One potential workaround for this issue is to implement
redirect tracking at the link level. Even though it was originally
intended for use on mobile sites, it could potentially solve your
If you are creating the request from a traffic variable, you can request
that Yearly Unique Visitors be activated for it and create a single
request of daily granularity with that metric, but that metric value is
calculated on the calendar year.
You can create customized rolling date range expressions (i.e.
"cy+9m-1d") that should cover what you want to achieve except when you
enter the new calendar year. Or you can simply extend what @Gigazelle is
saying, create a column with the start and end dates for each of your
requests, like so:A1: 09/30/2013A2: =TODAY()-7A3: =TODAY()-6... and so
on until you have completed your date formulations for the past week.
Then, you would create seven requests that would all reference cell A1
as the star...
Sorry for the multiple responses, but I have found a workaround as the
issues seems to be a problem with the select specific filter and
capitalization between the web and the API. If you go into the top items
filter and apply a contains search of "toronto", the correct value will
return. This applies to any geo-segmentation report right now.
[img]geoseg cities workaround.PNG[/img]
Strange, there is a bug that is causing this at the API level. I would
contact Client Care and open a ticket to get this addressed. Provide
them the details and report builder logs, and they should have
everything they need to escalate this to engineering.
The only thing I see different between your two reports is the sort
metric in reports & analytics is set to revenue instead of visits. I
would try removing the revenue metric from that report view or add it to
the report builder request to see what you get.
Hi there, Product Manager for report builder, here.I am running report
builder version 4.7.34 and pulled a simple geo-segmentation cities
report for yesterday in both reports & analytics as well as report
builder (See attached screenshot). It looks like everything matches to
me. I would check to make sure you are not comparing to instances, which
is a default metric used by geo-segmentation reports in reports &
analytics. Thanks.[img]geoseg cities.PNG[/img]
With every release, the report builder team strives to bring more
features and value to analyst and marketing workflows in excel.
This time with Analytics 1.4, we introduced two major new features
with the latest version: Anomaly Detection and Real-time reporting.
On top of all this, the scheduling workflow is improving with
proactive notifications to the sender when a scheduled workbook
fails to deliver.
Hello Hans,I would love to help you, but unfortunately my position at
Adobe was eliminated. Please reach out to Anthony Morelli
(email@example.com) to continue this conversation. I wish you the best
and hope Adobe can resolve this issue for you soon.Regards,Eric Hansen
Hi Hans,Happy to look at this. I see that this issue is being addressed
by the API team in the next major release of their Reporting API,
expected to come out early next year. I verified that the fix is
Hi Hans,Product Manager for report builder here. There have been some
issues around video that were being addressed at an API level, but I
would be happy to take a look at the issue of concern to see if I can
help push it along any further. Do you have a Client Care ticket number
I can reference?Thanks,Eric HansenProduct Manager
Hi Aparna,This issue can happen when cells that are a part of a report
builder request are deleted or drastically modified so that report
builder cannot parse the input or output locations in excel. If you edit
the affected requests, you can re-specify the input and output locations
and that should correct the problem.Thanks,Eric HansenProduct Manager,
This sounds like an implementation change might be responsible for the
jump in discrepancy. I would also audit the technology used to access
your site to determine potential differences in sources of traffic (i.e.
That is an interesting idea that you may want to post on the Idea
Exchange if you haven't already. Alternatively, you can leverage the
flexibility of anomaly detection in report builder to visualize only the
data points (in your case weekdays) that are relevant to your needs.
As a follow-up to this post, report builder can automatically convert
ExcelClient created data blocks, so if you have a copy of the delivered
report as it was scheduled from ExcelClient v13.5, you can easily
upgrade to a report builder scheduled workbook.
The latest version of the Clickmap plugin is 2.3.26. If the version
installed is different from this, try clearing your browser cache and
download the plug-in again. As an alternative trick, you can change the
sc.omniture.com or sc2.omniture.com to sitecatalyst.omniture.com or
sitecatalyst2.omniture.com respectively on the download page for the
visitor click map plug-in, and that should circumvent any caching issues
you might see.
Hello Annette,The latest version that was released last night (version
2.3.26) was tested and confirmed working on all the latest versions of
Firefox. I am running it right now on Firefox 26 without any problems.
If you can confirm you have installed version 2.3.26 of Clickmap on
Firefox and still experience problems loading the tool, then please open
a ticket with Client Care ASAP so we can address the issue.Thanks,Eric
Hi Tam,Yes, we are also aware of this issue, but please feel free to
file a ticket with ClientCare so we can appropriately document the
customers affected and impacted by this issue for IE 11
Hi David,You are correct that we are still working on this issue. It
remains our top priority for the visitor click map team. We are making
progress on identifying a fix for this issue, but we do not expect a fix
to be released until January at the earliest.Thanks,Eric
Hi Cunn Yong,Here's the latest situation on this issue: We are currently
working with Mozilla to discover a solution to the environmental issue
in their later versions of Firefox, but no fix timeline has been
established at this point. We are continuously working on this issue as
my click map team's top priority.Thank you,Eric
Product Manager for visitor click map, here. I can confirm there are
bugs on more recent versions of the browsers due to security changes.
While we are exploring various options to address the challenge here, it
is unfortunately a difficult problem to solve due to all the moving
parts and different groups involved in causing these display issues.
Older versions of Firefox and Internet Explorer should still function
with the latest version of visitor click map, but fixing browser