What is the purpose of the VisitorIdentification control? - analytics

My Sitecore starterkit website contains the following control in the head of each layout. Can someone explain what it's purpose is and whether or not it's needed? I could not find any information on it on the Sitecore SDN...
<sc:VisitorIdentification id="VisitorIdentification" runat="server" />
Control's output:
<link href="/layouts/System/VisitorIdentification.aspx" rel="stylesheet" type="text/css" />
Contents of stylesheet:
.sc_visitor {
}

See Analytics Configuration reference, paragraph 4.1.5 "The VisitorIdentification Web control".
Just in case the link about becomes obsolete:
The VisitorIdentification Web control helps the Sitecore analytics engine identify robots. The
VisitorIdentification Web control generates an HTML <link> element that references an empty CSS
resource. The Sitecore analytics engine uses this request to help differentiate robots from actual users.
For more information about automatic robot detection, see the section Automatic Robot Detection.
Important
To assist the analytics engine in robot identification, include the VisitorIdentification Web control in all of
your layouts. For example:
<sc:VisitorIdentification runat="server" />

It is used for OMS/DMS. You can kind of compare it to the Google Analytics script. If you don't use Sitecore DMS, you can delete it

Related

Where to put user configuration fields for a custom component in Salesforce

I've built a custom lightning component that is embedded in Record pages, but I can't figure out from documentation how to setup a configuration area for the User to put their data for the component. Can somebody point me in the right directions ?
From the documentation:
Use a design resource to control which attributes are exposed to builder tools like the Lightning App Builder, Community Builder, or Cloud Flow Designer. A design resource lives in the same folder as your .cmp resource, and describes the design-time behavior of the Lightning component—information that visual tools need to display the component in a page or app.
Here's the example given in on that page:
<design:component label="Hello World">
<design:attribute name="subject" label="Subject" description="Name of the person you want to greet" />
<design:attribute name="greeting" label="Greeting" />
</design:component>
By following these instructions, users will be able to configure the input data within Lightning App Builder.

How to modify HTMLElement in index.html before page gets returned to requestor

Based on my custom URL parameters I process, I am trying to modify dynamically a meta tag I have id'ed in index.html like so:
<meta name="og:image" content="http://example.com/someurl.jpg" id="ogImage"/>
The code below in my home.ts seems to be working
document.getElementById('ogImage').setAttribute("content", Media.ImageURL) ;
I can verify it is via the browser dev console/elements.
However, when I view from facebook via their ojbect graph debugger at
https://developers.facebook.com/tools/debug/og/object/
It appears to see the default
http://example.com/someurl.jpg
as if the index.html is shipped before my home.ts gets chance to make the update.
Perhaps, my understanding is flawed and there is better way to do this.
Thank you.
Note1: initially, I was thinking I had to make some angular binding between index.html and one of my services but I could not locate any sample code, the closest I came to was this post
How can I update meta tags in AngularJS?
But I don't know how to apply it for my ionic2/3 code, so I opted for the document.get approach.
Note2: the ultimate goal here is to share a link into a social media (web or app) like facebook, a messenger like viber/skype, etc... and have it resolve to meaningful images, title, description to drive the visit back to the site via browser, or app if the user clicking on the link is on a mobile device with my app version of the site installed on his device.
Note3: if you decide to point me to ionic deeplinking please provide code to match above, because I could not understand how to apply to my case.
If you are trying to implement dynamic open graph meta tags values in your pages, you will need a server-side scripting language like php. Such a script will run on the server, update the pages as needed, then the pages will be served to the requesting site or application.
client-side scripting (ie. JavaScript) is usually ignored when a site or app is merely visiting your site/link for the purpose of extracting (aka scrapping, parsing html) information such as the one provided by the open graph meta tags (og:title, og:description og:image...).

What's the workflow for developing a web page for Kik Messenger

I'm looking at what's required to develop a web page for the Kik Messenger in-app browser and I'm confused as to how the development workflow is supposed to work.
The API Docs say that "To launch your webpage in Kik simply open the sidebar and type in the URL to your webpage.", which would be fine except for the fact that the "sidebar" no longer exists in the current version of the app and it no longer seems to be possible to enter an arbitrary URL(*).
* EDIT: It looks like you can open an arbitrary URL in the browser by entering it into chat and then tapping on it.
Given these restrictions, how do folks test their web pages with the app? Do you have to just use the Chrome Extension until deployment?
Related question: How do you make Kik aware of your web page? Some of the other questions on this site imply that you have to wait for their web crawler to index it. Is that the case? If so, is exactly how this works documented anywhere? I feel like I've missed a doc link along the way.
In December they removed the NEW Apps tab in the Discovery Section as well as the option to access arbitrary URLs. (as you pointed out) For testing I usually use the Chrome extension or access my testserver via an URL from a chat.
But since the NEW tab is currently removed, it is not very feasible to release new Kik Apps at the moment, since people would only be able to discover your App by using the Search function and getting into top 100 would be very unlikly this way. I contacted Kik if the removal of the NEW tab was a permanent change, to which I got the response that they are currently revamping their platform and new solutions on the way for the stuff they are moving.
So if u are currently working on a Kik App I would recommend waiting with releasing it until possible future updates of the Kik Browser are released.
As for your other question to make the crawler find you app, you simply have to add some Meta tags into your header:
<meta name="description" content="app description">
<link rel="kik-icon" href="your image")">
<link rel="canonical" href="your domain">
<script src="http://cdn.kik.com/kik/2.0.5/kik.js"></script>

IE document compatibility in iFrame

I have a web application that is used in an iframe by a web portal (SAP enterprise portal). The portal responds with header x-ua-compatible IE=EmulateIE7. This messes up my application which uses AngularJS. I tried following in my application but it does not work. How can I tell IE to use standard mode with my application?
Note changing the portal is not an option at this time.
<meta http-equiv="X-UA-Compatible" content="Edge"/>
What do you mean by "Note changing the portal is not an option at this time."?
the best option is use header
in the page with angular application
othewise you could use the Iview DocumentObjectModel this iview has the property to define with way you want this page gets rendered
you could choose between
IE7Emulated
standards with it's edge mode for IE

Media Queries in DotNetNuke, mobile enablement

I am starting a new project which requires content managment and have decided to use dotnetnuke which I have never used before and a concern of mine is the use of media queries for mobile devices.
Can I use media queries in a dotnetnuke skin and does anyone have any examples / tutorials of this in use? I have looked everywhere and cant find any information of dotnetnuke utilizing media queries.
Thanks
There's a free skin available on the DotNetNuke Store that demonstrates some mobile skinning concepts. But, ultimately, you should be able to include media queries in your skin's stylesheet without doing anything special. Is there something specific that you're running up against?
You'll probably want to include a viewport <meta> tag, which you can do like this:
<%# Register TagPrefix="dnn" TagName="Meta" Src="~/Admin/Skins/Meta.ascx" %>
<dnn:Meta runat="server" Name="viewport" Content="initial-scale=1.0,width=device-width" />

Resources