How to restrict tracking calls from domains other than you own?

Avatar

Avatar
Level 1
zahid15001577
Level 1

Likes

0 likes

Total Posts

5 posts

Correct reply

0 solutions
View profile

Avatar
Level 1
zahid15001577
Level 1

Likes

0 likes

Total Posts

5 posts

Correct reply

0 solutions
View profile
zahid15001577
Level 1

03-12-2020

Since Adobe Analytics has front-end implementation, anyone can copy your tracking script or entire page source and use it on their domain. How to prevent tracking calls made from domain other than you own. May be something like not considering those calls so as to save tracking call cost and keep the data clean?

Thank you,

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Shape 25
MVP
Andrey_Osadchuk
MVP

Likes

537 likes

Total Posts

968 posts

Correct reply

263 solutions
Top badges earned
Shape 25
Bedrock
Coach
Boost 500
Affirm 250
View profile

Avatar
Shape 25
MVP
Andrey_Osadchuk
MVP

Likes

537 likes

Total Posts

968 posts

Correct reply

263 solutions
Top badges earned
Shape 25
Bedrock
Coach
Boost 500
Affirm 250
View profile
Andrey_Osadchuk
MVP

03-12-2020

As an option you may want to populate a variable with a page URL (or hostname) and then configure a VISTA rule to filter the beacons from undesired websites. However, this will unlikely bring you a positive ROI if the key objective is to reduce the number of server calls as VISTA setup is not free, and I am not sure if filtered server calls are not counted...

If you would like to get rid of the data from undesired websites, consider creating a segment and a virtual report suite with it.

 

Best wishes,
Andrey Osadchuk | Inspect Launch Implementation, Automate Classifications & Data Sources, Essential Bookmarks

Answers (3)

Answers (3)

Avatar

Avatar
Affirm 100
Employee
ishans52004352
Employee

Likes

154 likes

Total Posts

324 posts

Correct reply

104 solutions
Top badges earned
Affirm 100
Give Back 10
Give Back 5
Give Back 3
Give Back
View profile

Avatar
Affirm 100
Employee
ishans52004352
Employee

Likes

154 likes

Total Posts

324 posts

Correct reply

104 solutions
Top badges earned
Affirm 100
Give Back 10
Give Back 5
Give Back 3
Give Back
View profile
ishans52004352
Employee

04-12-2020

You may also want to opt for server side implementation to mitigate such concerns.

Avatar

Avatar
Affirm 50
MVP
evolytics_brian
MVP

Likes

80 likes

Total Posts

170 posts

Correct reply

54 solutions
Top badges earned
Affirm 50
Applaud 25
Establish
Seeker
Give Back
View profile

Avatar
Affirm 50
MVP
evolytics_brian
MVP

Likes

80 likes

Total Posts

170 posts

Correct reply

54 solutions
Top badges earned
Affirm 50
Applaud 25
Establish
Seeker
Give Back
View profile
evolytics_brian
MVP

03-12-2020

I'd go with something like this...

function checkValidDomains(host) {
  var validDomains = ['x.example.com', 'y.example.com'];
  if (!(validDomains.indexOf(host) > -1)) {
    s.abort = true;
  }
}

s.doPlugins = function (s) {
  checkValidDomains(document.location.hostname);
};

If you don't already have doPlugins set up in Launch (or your AppMeasurement.js library), it's easy to do, and if someone happens to copy and use your analytics script verbatim, you'd be covered on ALL analytics calls. No need for rule-specific conditions or anything more complicated.

Avatar

Avatar
Seeker
Level 3
jkm-disco
Level 3

Likes

24 likes

Total Posts

130 posts

Correct reply

15 solutions
Top badges earned
Seeker
Contributor
Shape 1
Give Back
Affirm 10
View profile

Avatar
Seeker
Level 3
jkm-disco
Level 3

Likes

24 likes

Total Posts

130 posts

Correct reply

15 solutions
Top badges earned
Seeker
Contributor
Shape 1
Give Back
Affirm 10
View profile
jkm-disco
Level 3

03-12-2020

Piggy-backing off of @Andrey_Osadchuk 's answer, you could also set up your beacons to only fire on conditional events. In particular, create a condition within each rule that the domain meets the specific criteria.

 

The only drawback would be that if someone were that highly motivated to commit fraud, they could just send a ton a requests directly to Adobe's tracking server. Ultimately, you may want to look into what laws your country has to protect against fraud. For example, this would be very easy to prosecute under the United State's Computer Fraud and Abuse Act.