Exclude Hits by User Id

[hasini_abeywick]

Is there a way to exclude the hits related to a user by a specific parameter sent to Omniture, like the user-id? What I understood from the documentation is that this is not possible though processing rules. Is it?

Excluding by the IP address or by cookie would not help this case because we cannot make sure this user would log in using the same workstation all the time.

Any thought is much appreciated.

[Kaushalendra · Accepted solution]

Hi Hasini,

You are correct, Hits cannot be excluded using Processing rules. However, you can get a VISTA rule implemented for your specific requirement to exclude hits by specific User IDs.

Below is an article with detailed information on VISTA rules:

https://marketing.adobe.com/resources/help/en_US/reference/VISTA.html

~Kaushal

[brian_au]

I would also recommend looking at the the s.abort function: http://webanalyticsfordevelopers.com/2013/09/03/the-s-abort-flag/

http://blogs.adobe.com/digitalmarketing/analytics/a-new-lens-on-customer-behavior-time-prior-to-even...

>>>

The s.abort variable

A common question during my time in ClientCare (what seems like many years ago!) was, “What do I do if I want to prevent a beacon (i.e., image request) from occurring?” There are a few reasons why this might be relevant. Some companies have experienced instances where someone has copied their source HTML code, including their SiteCatalyst implementation, and deployed it somewhere else without changing references to report suite IDs, so that traffic to unrelated sites begins to pollute analytics data. Others have specific criteria for measurement and are only interested in firing off tracking code if those criteria are met (such as the presence of a certain campaign value or success event).

With the latest version of Adobe Analytics JavaScript AppMeasurement code, we have introduced a new variable called s.abort. When s.abort is set to ‘true’ (s.abort = true), the tracking beacon will not fire. This variable is designed to be implemented inside of the s.doPlugins() function, since this function is among the last to run before a beacon is fired and thus has the most information available to it regarding variables that have or have not been set, current state of the page, etc. Here is an example of a case where the company does not want to fire a beacon and count a page view if both s.campaign and s.events are not set:

s.doPlugins = function(s) {
s.campaign = s.getQueryParam("cid");
if ((!s.campaign) && (!s.events)) {
s.abort = true;
}
};

First, they attempt to set s.campaign using the “cid” query string parameter. Then, if it turns out that “cid” did not exist, and there was no value for s.events, they set s.abort = true and this prevents the SiteCatalyst tracking code from firing. This will prevent any data from being recorded in this instance; had either of those two criteria been met, the beacon would have fired and a Page View would have been recorded.

Note that you will need to download the latest s_code.js file from the Admin Console in order to use s.abort.

Best,

Brian

[hasini_abeywick]

Thanks a lot!

I will check the option of VISTA rules.