Has anyone on Stack implemented two separately controlled Adobe DTM [Dynamic Tag Manager, formerly Satellite Tag Management System] instances on a single site? My team is looking to implement our DTM instance, for delivering 3rd party marketing tags, on a partner site that already has DTM implemented. My concern is that we might run into data duplication, tag collisions or js errors.
I found a post that provides insight around running two separately controled Google Tag Manager instances on the same site [domain], but nothing around Adobe DTM: Two different google tag manager accounts in same domain
Any help/direction/suggestions would be appreciated.
Art
DTM is not designed to have two instances on the same page. You will encounter issues with duplicate calls, namespace collisions etc..
I would recommend creating a new "container" within the company just for the third-party marketing tags. This way, those tags can be managed independent of the existing implementation on the site. To implement the new container, simply add the container embed code to the header of the site. The _satellite call at the bottom of the page only needs to be fired once, regardless of the number of containers.
Related
While anlalysing some aem component, I saw
trackingFeature="core-components:image:v2"
property in cq_dialog > .context.xml. What is the use of trackingFeature="core-components:image:v2" ?
This was added across AEM Core Components a couple of years back. The purpose of the change was to align the components with Coral UI tracking functionality. See the Coral UI 3 docs for more information.
Judging by the comments on a related GitHub issue, Adobe use this API to provide some analytics as part of the opt-in aggregated usage statistics
Quoting from the docs:
You can help improve Adobe Marketing Cloud by sending Adobe statistics about how you interact with AEM. This information does not contain any data about your company’s site visitors and will only be used to help Adobe deliver, support and improve your user experience.
You can opt into usage statistics collection by using either the Touch UI or the Web Console.
It's likely that the component you're looking at is a proxy component that extends one of the Core Components.
How hard would it be to create a website that lets people create their own pages on them?
Like a company creating a custom page on my site only with a drag and drop system provided by my website (of course they would need to create an account).
What frameworks would I need to use?
I tried searching the web but didn't find anything. I found craft.js but I don't know if I can implement it like that.
Thank you all in advance.
Such a project would be very complex and cannot simply be "coded down". Here are the main reasons:
You need an infrastructure where and how your users can save their websites. Does every user just have one page or several (limited or unlimited)?
Drag and Drop requires some JavaScript interactions and a set of predefined web components like buttons, input fields, labels or images. You would have to define abstract components that could be individually filled with user content.
If you ask your users to register before creating websites, you must respect the "General Data Protection Regulation" (applies for the European Union).
If you want to make money with your project you'll have to consider several legal aspects depending on the country where you live.
In short, there are many reasons why homepage kits are not an easy thing to program.
We have web application that renders dynamic content. We want to manage our content copy changes via separate managed system where developer does not get involved in writing copy and just leave place holder and later on copy writer adds copy.
Per my knowledge, any CMS takes control most of front end and leaves developer to just do design and layout level control.
I am looking for some CMS that does not take control page structure but instead it runs as a thin layer before page rendering and replace the place holders with content.
To give an example, https://localizejs.com/ simply do localization with a JS on client, I can use that but I guess SEO will an issue since content is replaced with Javascript which most search engine won't execute.
I think what you are looking for is called a headless CMS. That means it is a back-end interface for users to manage their content, but there is no front-end to render it - just APIs to access the content. You can call those APIs from your application.
A few examples I've used or looked at in the past:
Directus
Blackstar
There's also a lot of momentum around using Drupal as a headless CMS.
We have some quite-specific requirements for our app that a CMS may help us with, and were hoping that someone may know of a CMS that matches these requirements (it's quite a laborous task to download each CMS and verify this manually).
We want a CMS to allow users to create and manage articles, but storing the articles in plain-text only. All of the CMSs that we have looked at so far are geared towards creating HTML pages. We want the CMS to manage workflow (approval process), and tracking of history.
The requirements for plain text only is that the intent is to allow business people to generate content which we are going to display in our Silverlight application - we don't want to go down the route of hosting and displaying arbitrary HTML in the app as we want the styling to be seamless with our app, amongst other reasons.
We would also want to allow the user to be able to link to media stored on the server, but not to external sites (i.e. HTML with no formatting, or some other way of specifying article links), and the third requirement is the ability to tag articles and search on articles.
Does anyone know of any non-HTML targetted CMS systems that may match these requirements?
I would expect several CMS systems to allow this, but eZ Publish stores content as plain XML. And you have a way of allowing certain tags if you wish; and explicitly prevent for example external links. You then have options for how to present that content according the templates you choose to use.
You also have control via a /layout/set/myLayout directive.
You could for example retrieve the content as a plain xml feed or a print layout or whatever custom format you choose at the time. With appropriate headers.
http://doc.ez.no/eZ-Publish/Technical-manual/3.10/Reference/Modules/layout/(language)/eng-GB
vs.
http://doc.ez.no/layout/set/print/eZ-Publish/Technical-manual/3.10/Reference/Modules/layout/(language)/eng-GB
You could define a layout such as /layout/set/xml/....
Workflow as in content approval processes, versioning, tagging and search are standard.
You can give Statamic a try.
http://statamic.com/
Not sure if you can disallow external links, though.
I have a customer who runs an event ticket sales site. The site uses several APIs that interface with ticket sales companies. Users view ticket/seat availability for a specific event in the form of a Google Map that plots seat availaiblity on the venue image for the event.
The site was written using ASP.NET 3.5 and deployed to the customer's server without source code. Some changes were made by a previous developer by de-compiliing the existing DLL and making subsequent changes. Thus, the original source code is not usable and not available.
My customer is interested in URL routing as an enhancment and use of "friendly" URLs instead of the long query string for each event.
What are some good benefits of using ASP.NET MVC2 for the redevelopment of the site? Besides URL Routing, what other improvements can we site in a non-technical way?
Thanks much for your help!!
http://weblogs.asp.net/scottgu/archive/2007/10/14/asp-net-mvc-framework.aspx
Key Point In My Opinion:
It will enable you to easily maintain separation of concerns in your applications, as well as facilitate clean testing and TDD.
Hi you can read all in this article http://weblogs.asp.net/shijuvarghese/archive/2008/07/09/asp-net-mvc-vs-asp-net-web-form.aspx