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.
Related
We building personalization feature and use AEM targeting engine to deliver personalization content. However, I see that in admin section of the AEM Segmentation, there is any attribute called "Impresssions" which I believe is stats on how many times the customized content was shown to user.
Assuming that, how does AEM get to know the statistics? Is it something AEM takes care of automatically or I have code or configure something explicit. The reason why I ask is, I see the snippet like below in kernal.js file.
if (window.CQ_trackTeasersStats && n.trackingURL) {
h(M, n.trackingURL)
}
I noticed that n.trackingURL is null in my case.
Any help shall be appreciated. And also should I looking for impression statistics in author env or publish env?
AEM Campaign use a OOTB or custom Impressions service to calculate the Impressions.
There are two option in AEM to calculate the impressions
Yes, This something AEM can take care automatically
for you but it will not give you a correct picture as every instance will be having a separate copy so you have to write some code to collect all values and push it back to all environment.
You also have an option of using your Adobe Sitecatalyst to
calculate an impression which gives you a more accurate count of
impressions. for this sitecatalyst expose their rest service so that
you can update the impressions on run time.
n.trackingURL is null because you have not configured the sitecatalyst account for this environment.
Read docs Or
Implementations instruction:
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.
Lets say my web server app is in drupal or wordpress, or even code igniter, how would one get about integrating a comment system? TSpecifically what I am trying to find out is if anyone was able to find a successful approach that would save some time as opposed to me going down the road of tying myself to a specific CMS content system.
Just throwing in some considerations here (by no means complete):
Are users also accessing your content (and its comment system) via the website?
If so, you'll want to have a comment interface that is available on the website too, and the easiest choice may be to use the comment system natively supplied by your CMS / through plugins.
If on the other hand your users will only be using the iOS app(s) for commenting (via a native interface) or you'll be heavily customizing the website anyway, using a comment system independent from your CMS might be an option.
How will the content be accessed from the app?
Via a simple web view? Or will the app download via an API provided by your CMS and display it in a native UI? If you are using an API provided by your CMS, you will have the same issue with your content as with your comments when moving CMSes.
You could add an intermediate layer that abstracts from the specific CMS API.
Or if you don't really plan on moving CMSes but want to prepare for that event nevertheless, you could simply implement a no-frills "version check" to ask the server for the CMS kind / version it is using, and if it doesn't match what your app expects, ask the users to update. This isn't the prettiest user experience, but it might be sufficient depending on what you're actually planning.
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
We are in the early stage of overhauling a multi-brand website built using a custom developed java mvc framework to enable web 2.0 features. Built-in features we are looking at are: i18n, sso, content search and indexing, personalization, mashup support, ajax support, rich media content storage and management support, friendly to search engine optimizations, bookmarkable URLs, support for social networking sites, support for page composition and decoration using templates.
A combination of these features are supported by many portal and cms software.
Any insights will be very helpful in using a portal/cms combination to address this requirements!
This is a follow-up on this post focusing on the portal/cms angle
we are developing the same sort of thing, we are using Umbraco, open source, by far the best opensource we have come across
Joomla comes to mind. The ability to skin and implement templates is a core strength of the product. You can create channels of content as well as enable varying levels of user customization via roles.
Another nice feature is that you can export your changes to your template. that way you can port your changes easily from QA to a customer site.
Finally, there is a very active community of extension developers with customizations, as well as numerous template designers.
If you require a Portal that does integrate with your CRM such as Salesforce and yet allows you to build a Mobile-Optimized branded portal for Customers, Partners or any other groups of users you can check out Magentrix:
www.magentrix.com