I also have a Mac. I keep Parallels with Windows 7 and Excel on it for
the sole purpose of being able to use ReportBuilder. Love love love this
"Omniture Idea"
The event-based rule for "Element in viewport" is an awesome feature.
The problem is that it only runs once per HTML page view. As sites
migrate to SPA the need for a setting to capture each time an element
appears in the viewport is becoming more necessary. Perhaps an option to
set a maximum number of times the rule can fire per HTML page view,
between 1 and infinite. An option to limit the rule from firing more
than once per unique HTML element would also be a slick addition. As in,
if you hav...
Users (non-admins) in DTM cannot see the embed script that is associated
with each property. Brands with dozens of DTM properties often provide
User-only access to agencies and consultancies. But there's no way to
confirm that a particular property matches up with the embed code on a
particular site. Users should be able to see (not edit) what the embed
code is on all DTM properties.
Similar to:
http://ideas.omniture.com/t5/Idea-Exchange-for-Adobe/Full-RegEx-for-report-filtering/idi-p/14352
I'd love to have full regex in Adobe: Reports/Analytics and Workspace.
But at the moment, we only have Contains or Does Not Contain. Expanding
Workspace to at least Reports/Analytics filter features would be a great
step!
I love how you can easily filter the Dimensions menu in Analysis
Workspace by variable names for props and eVars. For example, type
"eVar1" into your Dimensions or Report menu (Reports & Analytics or
Analysis Workspace) and you'll see a list of eVar reports that have
"eVar1" in them (eVar1, eVar10-eVar19, etc).The same thing happens for
props: search "prop1" and you'll see all reports/dimensions that have
"prop1" in them (prop1, prop10-prop19).However, if you search for
"event1", nothing is retu...
The closest thing that AW has to this feature right now is by:1 - set
your dates to expand from the beginning of the first date comparison to
the end of the second date. (for example, if you're comparing December
to January, set your date to December 1-January 31.2 - Pull in the
metric you want to compare. In our example, use Month as your dimension
rather than using the default: Day3 - Use the built-in Time dimensions
to "segment" each metric. (For example, pull the "Month" Time dimension
above...
Although the Advanced > Special Characters feature of Filters in Repotrs
& Analytics is nice, it'd be awesome to have full RegEx capabilities.
Analytics Workspace only has Contains/Does Not Contain which is even
more limited. An example where I need RegEx for Report Filtering:I'm
trying to filter my Page URL eVar report to list only items with a
colon, two characters that aren't colons, then a colon. In RegEx, that'd
be super-easy to create. But not possible with Reports & Analytics
"Advanced" f...
Hi Daavq - Not sure if you're still having this issue, but my bet is
that you're using the Library Managed code for your s_code. Is that
correct? If so, try moving it to Custom Code and
setting:s.linkTrackVars="None";s.linkTrackEvents="None";That *should*
clear your variables from the Exit/Download links on the page. Hope it
works! Let me know if not.
Agreed with Mark - it's great to see there are so many options! Also
great to hear that an even tighter integration between these
technologies is already in the works.
That's fair - good to know that the mboxCreate solution works. Out of
curiosity, why does DTM use update instead of create? Is there a missing
functionality or something with create?
Thanks Mike - I agree that's another option. Unfortunately it's not a
very elegant one (inject code via jQuery would be my first move). I'd
much rather Adobe just get DTM to use the right function.
Thanks Rahul. That is the way I'm deploying mboxes.The client I'm
deploying mboxes on has a significant difference between DOM Ready and
Window Onload - up to 15 seconds depending on the page.I've reached out
to ClientCare and it seems that the issue I'm dealing with is more the
significant delay caused by DTM using the mboxUpdate() method instead of
the mboxCreate() method. The issue is that mboxUpdate() waits to load
content on the page until window.onload. mboxCreate() would load the
content ...
Has anyone else seen pretty significant delays and content flicker on
mboxes that are injected on a page using DTM versus mboxes that are
hard-coded on the page? I have a client with literal seconds differences
between mbox loads and have definitely seen some flicker (gah!). Would
love to know if anyone has any sneaky work-around out there.
Today, DTM deploys mboxes around elements on the page using the
mboxUpdate function. This works very well - it erases the opportunity
for content flicker:- DTM hides the element with code in the - DTM calls
mboxUpdate- mboxUpdate waits until window.onload to update the content
Unfortunately, some clients have very large windows of time between DOM
Ready and window.onload It'd be interesting to add to DTM's interface to
have the choice to deploy mboxes using either mboxCreate or mboxUpdate.
Using...
Let's face it - bots are getting smarter. Bot Filtering needs to get
smarter too. Bots are getting better at changing user-agents, IP
addresses, domains and more in between visits. Bots are now even adding
delays between page views to look more like a normal visitor. And don't
forget, they're running JavaScript too. Adobe needs to expand Bot
Filtering to use look-alike modelling to discover visits with abnormally
high page views.Similar to this Idea:
http://ideas.omniture.com/t5/Idea-Exchange-fo...
There is so much opportunity for improvement with bot filtering in
Adobe, and the IAB filters are way too much of a black box. Here's a
related "idea" that I posted about just yesterday: Adding Bot Name as a
dimension in Data Warehouse:
http://ideas.omniture.com/t5/Idea-Exchange-for-Adobe/Add-Bot-Name-as-an-available-Dimensio
n-in-Data-Warehouse/idi-p/14043
