Adobe Analytics visitor ID firing incorrectly on exit link using DTM - adobe-analytics

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.

Related

Reverse engineering website : cannot find the form inputs in the post request

I need to interact with an external website I don't own. This external website requires credentials that I have. My goal is to add a user but the external website does not offer an external API. It looks like they are using Vaadin.
So to add a new user I need to manually fill in a form. Yet I have been searching for the route the "form" takes to post the input I give but could not find any.
Here is my issue : when I look at the HTML source code in browser I cannot see any form tag. The buttons have all the same id "button". When I fill in the form and look at the network tab in the developer tools, in the "parameters" section I cannot see the inputs I just gave although the POST request does appear. The cookies tab does not show the inputs either.
Consequently my questions are : why can't I find the inputs in the POST request and where can they be ?
Please note : this external website is a medical site so I prefer not share the url and they don't offer a mobile app, so there is no mobile API I could reverse engineer.
Any help appreciated :-)
Not stating the Vaadin version makes that a tad harder give an exact
answer, but at the core both the Vaadin 8 and 10+ behave the same way.
And the short answer to your question is: without another entry-point,
like an API, this can not simply be done using just some POST-Request.
Vaadin is not simply a html-form/request/response-html based framework;
it holds the scenegraph on the serverside in a session. All
communication is done via a single endpoint to the server and state
changes only are communicated back to the client.
For what you are after, your best bet is to use test automation
frameworks like selenium, geb, cypress, ...

Debugging issues with Adobe DTM rules not being captured in Adobe SiteCatalyst report suites?

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

Is it possible to use 1 DTM rule to send data to multiple integrated tools

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

Can I use Adobe's (Satellite) Dynamic Tag Manager to set basic Adobe Analytics (Omniture) vars?

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.

Tracking users' clicks and page visits in Rails

I would like to monitor users' page visits and clicks in my Rails app to make recommendations. My questions are:
Is there a Rails gem for this, or Google Analytics is the standard? If latter is true, then how should I link a page visit to a particular user profile?
It is typical in Rails to have a section in application.html.erb, which is shared for all pages. If I add Google Analytics pageview tracking code to in application.html.erb, will it be able to track all individual pages?
There are other ways, but the vast majority probably use Google Analytics. Several gems exist that help you integrate with GA to get at the data. See here: https://www.ruby-toolbox.com/categories/Web_Analytics.
Based on your first question, it seems you may want more insight than GA can provide. I've used ClickTale (http://www.clicktale.com) and Woopra (http://www.woopra.com) before, to good effect. This article lists several other alternatives, too - notice the high marks for Clicky: http://imimpact.com/web-stats-alternatives-to-google-analytics/.
Google Analytics (and almost all of these others) will take care of your second question automatically whenever the user loads a new page, since it keyed by URL. That means that, although you put the GA script code in a single place, each unique page is tracked individually.
If you have AJAX requests that change that page without changing the URL, you'll need to dig in to the GA script API. Essentially you'll need to push a new url (possibly with a # in it) whenever you want to track an AJAX-driven link/button click. See here: http://davidwalsh.name/ajax-analytics
I am biased, but I would recommend checking out impressionist, if you need to integrate the page views into the app in real-time. With analytics you will always have some lag time and you are also relying on an external dependency. Impressionist is good if you need this kind of control, but if you are just looking for simple metrics and don't need to pull them into the app, then analytics is probably the way to go.
Check out Ahoy, at https://github.com/ankane/ahoy. With just a few lines of code in your app, you can track page views and tie them to user accounts.
You can further customize Ahoy to track custom events, both the client (with JavaScript) and server.
Ahoy does not depend on any third-party services.

Resources