We need to pull an unlimited number of rows using the Reporting API but
to do so we have to set the source to data warehouse. But when using
data warehouse, you cannot retrieve the current day's data. We would
like to see the ability to retrieve unlimited rows of data that also
include data from today up to the time the report ran.
Here is what I did, and hopefully it will work for you. I created a new
data element and set the type to custom script. In the editor I added
the getPreviousValue() and split() plugin code and then called
getPreviousValue() with the current page name, returning the return
value. I use this data element on all page views to fill in a prop and
an eVar with the previous page name.
We need the ability to create an alert at the dimension level, which we
were able to do with the old "top 1000 items" functionality in the
legacy alerts. The alert should fire if any single item in a dimension
reached a certain threshold.
We run an ETL process with a scheduled Data Warehouse report as input.
When the format of this report changes between CSV and ZIP from one
month to the next, it breaks our ETL process. I would like to see an
option to choose the format of the Data Warehouse report so that it is
consistent every time it runs.
Hi Pankaj!The selector that I was using was just
"[digitaldata-feature]". Adding the option didn't work, but it did give
me some ideas to try. I had the attribute added to several different
types of fields, so I broke up my one rule into separate rules using the
different elements (a and input), but used the id of the select to look
for changes to the dropdown. Setting up the rule on the change of the
select instead of the click of the option works for all browsers I
tried.Thanks for the ideas!C...
I have an application where I want to track the selection of an item in
a dropdown. I've asked the dev team to add a custom data attribute to
each of the tags. Here is an example of one: OtherI have an EBR
set up to look for the click of the digitaldata-feature attribute. The
rule fires perfectly in IE and Firefox but it does not fire at all in
Chrome. I've tried the EBR with the "Apply event handler directly to the
element" both on and off but the rule will not fire in Chrome either
way. Any i...
Ah that is good to know. In my particular situation, the image request
is sent from a container app on an iOS device. I wonder if the switch to
POST happens the same on mobile? I'll have to check it out!
Overall I like it, especially having the menus moved to the top. One
issue I keep having is in Reports. I have access to many report suites
and use the search feature to find and select report suites all the
time. Since the update the search feature does not work well. Many times
the characters I type in do not match any of the report suites returned.
It can sometimes help if I put in an extra space after my search term.
It is frustrating.
I'm trying to understand why AppMeasurement places list variables high
up in the image request. In s_code, list variables were included near
the bottom so that if the list variables became very long it was less
likely to truncate other variables in the image request. This is not
true in AppMeasurement and I am seeing other props and eVars not being
captured when the list variable is very long. Is there anything I can do
to help in this situation?Thanks,Christy
Thank you! Just wanting to make sure I understand. So instead of turning
on s.trackOffline=true, I could set s.timestamp instead so all image
requests would be timestamped and continue to set s.visitorID? Could I
do this with a timestamp optional report suite or would I have to use a
timestamp hits only report suite? I would like to continue to use my
current report suite if possible for continuity of data.
I support a mobile application that uses the AppMeasurement library for
track offline usage as well. To do so I would need to set the report
suite to Timestamps Optional and set s.trackOffline=true in the code.
BUT I use s.visitorID to track my visitors since everyone must
authenticate to use the app. According to the documentation I cannot
send timestamped usage (s.trackOffline=true) and set s.visitorID. What
I am trying to implement the W3C standard for a data layer but have run
into a snag. Looks like arrays are not allowed in the path for a JS
object in a data element. For example, this only returns an empty string
in a data element but returns the expected value in the
should be doing differently?
Thanks Rahul. I am only using one analytics tool in my web property. But
like the original poster, I am also setting the tracker variable name to
"s" which is the same object as the inline analytics code. My thought
was that I was supplementing the existing tracking, but it looks as if I
can only add event based rules in this situation and cannot supplement
or change the page load image requests sent by the inline analytics