I set up a web property with a couple of rules in Adobe Dynamic Tag Manager. I'm using the DTM Debugger Chrome extension, I'm able to verify that satellite.js is picking up on the fact that the rule conditions are being met and that a request is being sent off to my Adobe DTM instance:
SATELLITE: Rule "Callout Click" fired.
SATELLITE: Adobe Analytics: tracked link using: linkTrackVars="eVar29,prop20,events"; linkTrackEvents="event26"
However, the event isn't showing up in my Adobe Analytics report suite and no errors are being thrown in either the Adobe SiteCatalyst interface nor the DTM interface.
I'm having a pretty hard time trying to figure out how to debug the problem from here.
What does the pipeline look like after a DTM rule is fired off on the front-end?
Are there any common things to look for when DTM seems to be working but SiteCatalyst doesn't show the props/events/evars/whatever on the report suite?
Where is the supporting documentation for Adobe Analytics/SiteCatalyst?
It looks like you can see your DTM rules successfully fire using the console but can you also confirm that an Adobe Analytics image request has been sent?
The easiest way to determine this is to use the network tab and filter on "/b/ss". These are specific values you'd expect to see coming from the image request. You will want to look for this when / if your rule fires successfully.
Once you have a successful image request you can troubleshoot the rule or Adobe Analytics config if you don't see data in the UI.
Hope this helps.
Mark
Related
This is a scenario for which i need to check the feasibility.
Suppose I have 2 different analytics tools. Let say Adobe Sitecatalyst and Mixpanel. To work with DTM these tools need to be integrated with DTM.
After integration, specific rules will be created. Question is -
Can we create 1 rule, and use it to send data to different tools simultaneously or we need to create different rules.
Answer is yes. You can create a single rule and customize the Adobe Analytics section to send whatever you need (using eVars, props, events, etc.). You can also create a third-party JavaScript tag (as part of the same rule) and customize the pixel for Mixpanel.
DTM is really one big JavaScript editor. If you can create JS tag, DTM can execute it.
Hope this helps.
Mark
I'm trying to find out if the Adobe Analytics click map plugin fails because it is ancient und apparently not maintained, or if I need to change something in my (not up to date, but not quite as ancient - H.27 ) s_code.
Now the instructions say "requires IE6 or FF3", so there is a good chance the plugin has died of old age without Adobe taking notice.
But then the documentation says
The Page ID (ClickMap) and Object ID (ClickMap) variables must be
present within a given image request after you click on at least one
link. These variables are also known as the pid and oid variables.
Generally, if s.trackInlineStats is set to true, these will
automatically populate
and while s.trackInlineStats is set to true I do not see a "pid" or "oid" parameter in the server calls. So my question is: Are there any other changes I need to make to the s_code to get the thing working, or is this broken and won't work no matter what I do ?
The error I'm getting is "invalid address" and a description of what an url is supposed to look like. I'm using Firefox (albeit not Version 3 but the lastest version) and I am logged in to the Adobe account connected to that page.
I've come across several scenarios where it broke AA tracking. Weirdness that involved things like the plugin appending "undefined" to certain various url params in the AA request, some of them causing Adobe servers to reject the hit (for example, one case was it appended "undefined" to currencyCode value and if you do not have a valid currency code value, Adobe rejects the entire hit).
I've gone to Adobe ClientCare several times over ClickMap shenanigans and eventually I was told (by Adobe) to not use the plugin, because it's always been buggy, and they basically stopped supporting it a long time ago.
As #sky pointed out, Adobe recently released their new ActivityMap reports and plugin, but it does require you to upgrade to AppMeasurement 1.6+
I am developing an application using Salesforce1 Lightning Component Framework. I have used HighCharts to display some data in graphical format. While submitted for security review for AppExchange Publishing, the HighCharts resource script file was flagged to be having security issues.
Comment from security review team:
"These libraries register event handlers and modify the DOM outside of
the lightning renderer lifecycle. This can cause undefined behavior
and breaks security policy."
When asked about this issue a suggestion given from security team is to unregister all events added by the HighCharts in unrender(). Any suggestion on possible ways to find out the registered window or document events would be much appreciated.
Note: All HighCharts invocation is done from Renderer only.
I'm using DTM to deploy Adobe Analytics on a very small single page application and are still relatively new to DTM as a company with no one having prior experience. We have custom code set up so that we can clear the variables after the tracking links have been called. We have not set up outbound links. We have set up events to fire a s.tl() call from custom code, not the adobe analytics section, when exit links are clicked. However, for some reason this is sending an fid instead of an AID to our report suite. We've added the visitor ID code in the section of the tool where we placed all the s_code and not in the custom page code area of the s_code if that matters.
Thanks,
Mike
Why not add the Visitor ID Service tool in DTM?
This configuration will automatically request the AID and deploy it correctly. With this implementation you won't need to touch the s_code / app measurement file.
Hope this helps.
Is it possible to use Adobe DTM (aka Satellite Tag Manager) to set basic Omniture/Adobe Analytics variables, like pageName, so we don't need to place this code on the page?
You will need to load the "Analytics" tool to DTM to begin setting up Adobe Analytics variables. The nice thing about DTM is you do not need to migrate all of your analytics code to DTM all at once, you can migrate in steps as long as you tell DTM analytics code already exists on the page.
There are great videos here (under Dynamic Tag Management) which walk you through the setup of DTM and the configuration of the Analytics tool. https://outv.omniture.com/
One of the biggest benefits of DTM is to be able to do this in a very easy-to-do manner. You can create data elements to define the different pieces of data, and then use those data elements to populate the SiteCatalyst variables in rules. It greatly simplifies an implementation and is much faster than having to add code to each page. Plus it removes the need for developers having to put props, eVars, and events on a page. They just put a data layer (preferably in JSON) with all of the data you want to send to SiteCatalyst. The structure of the data layer is unimportant, and they can use any naming format they want.