Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

Part of site was stolen with Omniture pixel

Avatar

Level 2

Hello,

Somebody copied our site to his domain with our Omniture pixel. So now we have his data in our suites. Omniture support advised me to use Vista rules, but I think it will be very long process, and this is critical issue for us because amount of negative data is big. Can anyone advise what to do except Vista, is there any functional or methods to block this hits?

Thanks,

Aleks

1 Accepted Solution

Avatar

Correct answer by
Level 9

Hi Aleks,

Have you looked into the s.abort option to prevent the beacon from firing?

Best,

Brian

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

The s.abort variable

A com­mon ques­tion dur­ing my time in Client­Care (what seems like many years ago!) was, “What do I do if I want to pre­vent a bea­con (i.e., image request) from occur­ring?” There are a few rea­sons why this might be rel­e­vant. Some com­pa­nies have expe­ri­enced instances where some­one has copied their source HTML code, includ­ing their Site­Cat­a­lyst imple­men­ta­tion, and deployed it some­where else with­out chang­ing ref­er­ences to report suite IDs, so that traf­fic to unre­lated sites begins to pol­lute ana­lyt­ics data. Oth­ers have spe­cific cri­te­ria for mea­sure­ment and are only inter­ested in fir­ing off track­ing code if those cri­te­ria are met (such as the pres­ence of a cer­tain cam­paign value or suc­cess event).

With the lat­est ver­sion of Adobe Ana­lyt­ics JavaScript App­Mea­sure­ment code, we have intro­duced a new vari­able called s.abort. When s.abort is set to ‘true’ (s.abort = true), the track­ing bea­con will not fire. This vari­able is designed to be imple­mented inside of the s.doPlugins() func­tion, since this func­tion is among the last to run before a bea­con is fired and thus has the most infor­ma­tion avail­able to it regard­ing vari­ables that have or have not been set, cur­rent state of the page, etc. Here is an exam­ple of a case where the com­pany does not want to fire a bea­con 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 para­me­ter. 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 pre­vents the Site­Cat­a­lyst track­ing code from fir­ing. This will pre­vent any data from being recorded in this instance; had either of those two cri­te­ria been met, the bea­con would have fired and a Page View would have been recorded.

Note that you will need to down­load the lat­est s_code.js file from the Admin Con­sole in order to use s.abort.

View solution in original post

0 Replies

Avatar

Correct answer by
Level 9

Hi Aleks,

Have you looked into the s.abort option to prevent the beacon from firing?

Best,

Brian

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

The s.abort variable

A com­mon ques­tion dur­ing my time in Client­Care (what seems like many years ago!) was, “What do I do if I want to pre­vent a bea­con (i.e., image request) from occur­ring?” There are a few rea­sons why this might be rel­e­vant. Some com­pa­nies have expe­ri­enced instances where some­one has copied their source HTML code, includ­ing their Site­Cat­a­lyst imple­men­ta­tion, and deployed it some­where else with­out chang­ing ref­er­ences to report suite IDs, so that traf­fic to unre­lated sites begins to pol­lute ana­lyt­ics data. Oth­ers have spe­cific cri­te­ria for mea­sure­ment and are only inter­ested in fir­ing off track­ing code if those cri­te­ria are met (such as the pres­ence of a cer­tain cam­paign value or suc­cess event).

With the lat­est ver­sion of Adobe Ana­lyt­ics JavaScript App­Mea­sure­ment code, we have intro­duced a new vari­able called s.abort. When s.abort is set to ‘true’ (s.abort = true), the track­ing bea­con will not fire. This vari­able is designed to be imple­mented inside of the s.doPlugins() func­tion, since this func­tion is among the last to run before a bea­con is fired and thus has the most infor­ma­tion avail­able to it regard­ing vari­ables that have or have not been set, cur­rent state of the page, etc. Here is an exam­ple of a case where the com­pany does not want to fire a bea­con 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 para­me­ter. 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 pre­vents the Site­Cat­a­lyst track­ing code from fir­ing. This will pre­vent any data from being recorded in this instance; had either of those two cri­te­ria been met, the bea­con would have fired and a Page View would have been recorded.

Note that you will need to down­load the lat­est s_code.js file from the Admin Con­sole in order to use s.abort.

Avatar

Level 2

Can you create a segment that excludes the hostname of the incorrect site?