I would like to be able to script Workspaces using Javascript. An API
would be awesome.Example: when user drags changes Dimension in one
table, listener gets triggered. Javascript code attached to that
listener then updates other tables in the Workspace.Example of things I
would change programmatically:- Dimensions / Metrics / Segmentation -
add, remove, change, break downs (add, remove, change)- Date ranges-
Show / hide panels- Replace text
Hi All,My feeling is that we're talking about two fundamentally
different approaches here. Both have their merits and use cases.I'd like
to help you further, bobagrand, but I have to admit that I haven't yet
worked with decorated HTML at all. I guess the question is how to access
all the data in the decorated HTML inside your Launch Rules and
Actions.Sounds to me like a blog article I need to write once I worked
it out...
It would be great if we could enable/disable, create, and edit Alerts
via API.Enable/disable would help customers keep them relevant and work
around the "have to delete 12 meaningless Alerts every morning"
effect.Create/edit on top of that would allow better integration with
Enterprise systems.
Hi Stew,We're pretty much thinking exactly along the same lines here. I
also started writing such an Extension, with a "before/after" config,
plus a "delete existing doPlugins"/ "keep existing doPlugins" switch on
top.I didn't think about the loop, or the call type, mainly because
neither does the original doPlugins. But good point!If you ask me: put
your Extension live!Cheers,Jan
The Analytics Extension should provide a Trigger that would be
equivalent to the call to doPlugins.Goal of that is to get rid of any
customisation in an Analytics deployment. I would want to use a Rule to
replicate the behaviour and possibilities of doPlugins.
I would like to be able to track Referrers without the query string
using Processing Rules. Since I can't split a value, I want to
concatenate "Referring Domain" and "Referring Path".Unfortunately, the
latter doesn't exist.Example: Visitor comes from
http://www.site.com/some/page.html?cid=trcd001&sec=1234. I want to be
able to pass "www.site.com/some/page.html" into a variable.Thanks!Jan
(inspired by urs.boller)
I suggest having a button in the Processing Rules manager, that when
clicked generates documentation for all existing Processing
Rules.Rationale: Processing Rules are managed separately from tags, and
they sometimes receive somewhat less attention. They do have the ability
to significantly change tracked data, so documentation is crucial.Adding
some "auto-doc" for Processing Rules would alleviate that need.
It would be incredibly cool to have an API for Workspace.Main use cases
would be:- create Analytics Workspace Projects automatically- manage AW
Projects (bulk changes like "use different segment" or "replace metric X
by metric Y in all projects")The icing on the cake would be for the API
to also deliver usage statistics for the individual AW Projects.
