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
Related
I am embarking on a POC to replace a Power BI dashboard that can’t do all the visualizations we need with a dash app. One major requirement is to be able to pass multiple filters to the app via url in a manner similar to the Power BI capability.
I have tried to research this and see references to URL callbacks and believe this provides the functionality I will need, but I don’t yet understand dash apps well enough to be sure.
I’m not asking how to, just whether or not it can be done. Thanks!
You can. Use the dcc.Location component (docs), and structure any callbacks that need to listen to the URL to have an Input based on that component. You can even pass multiple things with it, such as "filter_1/3/filter_2/5/filter_3/1" and then .split('/') to break up the string and parse the values.
I'm using the Rally SDK 2 to manipulate user stories from Javascript in a "Custom HTML" application.
I can query a story and retrieve its attributes.
I can update some of the attributes, like the Name of the Iteration for instance.
How can I add a successor to my story?
If I understand well, I should edit the "/HierarchicalRequirement/.../Successors" of my story, but I don't understand how to do that.
Would someone have an example, please?
Unfortunately, I don't have an exact example you can use, but the successors (or predecessors) are 'collections'. As such, you need to 'add' to the collection. There is an explanation of some of this here: https://docs.ca.com/ca-agile-central/saas/apps/2.1/doc/#!/guide/collections_in_v2
Built into the model for the artefact are routines to handle all the details. If you want more details, then you can download the sdk-debug.js file from the Rally server. To get to it, open up the developer tools in your browser and have a look where a custom app would get the sdk.js file from. The debug variant is formatted for humans to read and a very useful source of how to do things at the low levels. The definition of Rally.data.wsapi.ModelFactory has some good tips.
One of the recommendations I make to people starting out writing custom apps, is to use the developer tools in the browser to watch the network traffic that the Rally UI makes - and then work backwards to code.
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.
I am in researh mood and one of the tasks I have in my to do list is:
"Finalize the techonlogy to use for creating a web interface to my existing Client Server application".
My application is very rich and full of features. It makes sense it is has rich client UI, because it is a productivity tool. Many shortcuts, many things without any click. So I am not looking for a full replacement.
My app has some features that would be good to be used also from a web interface.
Some of them:
1) multi user calendar (every item I see in the calendar is linked to something in my app, for example "today 11:00: recall customer 'Dummy ltd'". This is not a simple memo, it is also linked to the customer), so i can see my and others tasks.
2) Confirm some task (yes I did this!)
3) see some report (some graph or some tabular report)
Of course this are not simple outputs, they can contain some logic (for example some calendar items must be readonly, some others can be edited).
This said, I was considering whether doing all this with Google would be a reasonable choice. In this way I don't have to install anything, simply interfacing with google would be enough. I can map my application users to one (or more) google users and use all the google features (calendar, charts, tasks, ....).
May you comment on this? Which are the good/bad points.
Some good points I can forsee:
1) no need to design any UI, just connect to an existing powerful and userfriendly system
2) the applicatino will automatically be compatible with google ("is it possible to export on google?" is a typical question I recieve)
3) google already provides the interface for the points I wrote above (tasks, calendar, charts, ...)
4) no deployment issues. No server hosting. just need to configure the users with some wizard.
Some bad points:
1) Which is the long term support? Will the Google APIs change every month or some of them will be stable for years?
2) How much may I push? How much is it possible to customize? I mean can I write some logic like "this item is readonly", "this item is not"? (afaik in google I can share a calendar with other people, in different ways, but there is no way to make only a part of it readonly. Of course I could do this with a trick, like having 2 calendars, one readonly and the other not. But is it possible to change the default google behaviour like for example in calendar case?)
3) of course I am limited, writing "from scratch" allows me to do everything.
Final note: my app is a Delphi client/server application. The communication will be done from an application server that will interact with the google apis.
As I understand, the API are stable, for example the Calendar API documentation says
Google periodically updates the
Calendar Data API in order to deliver
new features and to repair defects
discovered in previous versions. In
most cases, these changes will be
transparent to API developers.
However, occasionally we need to make
changes that require developers to
modify their existing applications.
So as long as the service exists I would expect only small changes. Services however can disappear from one day to the other (see Google Wave for example) so I would check the requirements of an 'exit strategy', at least a way to export the most critical information.
My application is very rich and full
of features. It makes sense it is has
rich client UI, because it is a
productivity tool
It sounds like Morfik might be a good choice for creating web interface for your application. Once you like it, you might even make the whole application in it. ;-)