analytics - Cross-domain user tracking without 3rd party cookies? -


how cross-domain web tracking services implemented (e.g., behavioral advertising), majority of people browsing 3rd party cookies disabled?

more explicitly, how third party tracking service recognize 2 requests different domains coming same person?

some options come mind:

  • maybe iframe-based, embedding tracking page third-party tracking service various sites. included tracking page should able set first party cookies tracking domain (?). if included page unique each tracked page, should possible match request website iframe embedded into?!
  • ip + user agent based (unreliable)
  • browser fingerprinting , clock skew measurements (i hope not in common use today)
  • cookie handover, is, append session id paremeter links between various pages. visited page can set own cookie same id referring page. problem is, not work if second page not visited clicking 1 one of prepared links.
  • using non-traditional cookies, such flash cookies. maybe of these monsters don't honor same-origin policy?

so, how being done?

edit: noticed disabling 3rd party cookies prevent creation of new cookies, existing ones still readily sent third party domain. hence, 1 somehow redirect user 3rd party tracking service, sets first-party cookie, later read web bug. interesting.

it depends on service behavioral advertising it's still being done using third party cookies. people don't block them works enough useful. enabled default in major browsers , not many people mess around settings. last time saw statistic on number less 5% can vary considerably depending on demographics of users you're looking at. in work see lower numbers of cookie rejection rates.

tracking inexact science anyway there multiple things can disrupt linking of people web visits (such common trend of people using multiple devices , browsers).

my personal opinion on subject think you're getting @ online advertising industry needs careful in area because public opinion on subject appears confused , lead rejection of more necessary privacy reasons.


Comments

Popular posts from this blog

c# - how to write client side events functions for the combobox items -

exception - Python, pyPdf OCR error: pyPdf.utils.PdfReadError: EOF marker not found -