|
facebook
|
Is used to Enable ad delivery or retargeting
|
90
days
|
HTTP
|
Meta
|
|
__fb_chat_plugin
|
Is needed to store and track interactions (marketing/tracking).
|
persistent
|
HTTP
|
Meta
|
|
_js_datr
|
Is needed to save user settings.
|
2
years
|
HTTP
|
Meta
|
|
_fbc
|
Is needed to save the last visit (marketing/tracking).
|
2
years
|
HTTP
|
Meta
|
|
fbm
|
Is needed to store account data (marketing/tracking).
|
1
year
|
HTTP
|
Meta
|
|
xs
|
Is needed to store a unique session ID (marketing/tracking).
|
1
year
|
HTTP
|
Meta
|
|
wd
|
Is needed to log the screen resolution.
|
1
week
|
HTTP
|
Meta
|
|
fr
|
Is needed to serve ads and measure and improve their relevance.
|
3
months
|
HTTP
|
Meta
|
|
act
|
Is needed to store logged in users (marketing/tracking).
|
90
days
|
HTTP
|
Meta
|
|
_fbp
|
Is needed to store and track visits to various websites (marketing/tracking).
|
3
months
|
HTTP
|
Meta
|
|
datr
|
Is needed to identify the browser for security and website integrity purposes, including account
recovery and identification of potentially compromised accounts.
|
2
years
|
HTTP
|
Meta
|
|
dpr
|
Is used for analysis purposes. Technical parameters are logged (e.g. aspect ratio and dimensions
of the screen) so that Facebook apps can be displayed correctly.
|
1
week
|
HTTP
|
Meta
|
|
sb
|
Is needed to store browser details and security information of the Facebook account.
|
2
years
|
HTTP
|
Meta
|
|
dbln
|
Is needed to store browser details and security information of the Facebook account.
|
2
years
|
HTTP
|
Meta
|
|
spin
|
Is needed for promotional purposes and social campaign reporting.
|
session
|
HTTP
|
Meta
|
|
presence
|
Contains the "chat" status of logged in users.
|
1
month
|
HTTP
|
Meta
|
|
cppo
|
Is needed for statistical purposes.
|
90
days
|
HTTP
|
Meta
|
|
locale
|
Is needed to save the language settings.
|
session
|
HTTP
|
Meta
|
|
pl
|
Required for Facebook Pixel.
|
2
years
|
HTTP
|
Meta
|
|
lu
|
Required for Facebook Pixel.
|
2
years
|
HTTP
|
Meta
|
|
c_user
|
Required for Facebook Pixel.
|
3
months
|
HTTP
|
Meta
|
|
bcookie
|
Is needed to store browser data (marketing/tracking).
|
2
years
|
HTTP
|
LinkedIn
|
|
li_oatml
|
Is needed to identify LinkedIn members outside of LinkedIn for advertising and analytics
purposes.
|
1
month
|
HTTP
|
LinkedIn
|
|
BizographicsOptOut
|
Is needed to save privacy settings.
|
10
years
|
HTTP
|
LinkedIn
|
|
li_sugr
|
Is needed to store browser data (marketing/tracking).
|
3
months
|
HTTP
|
LinkedIn
|
|
UserMatchHistory
|
Is needed to provide advertising or retargeting (marketing/tracking).
|
30
days
|
HTTP
|
LinkedIn
|
|
linkedin_oauth_
|
Is needed to provide cross-page functionality.
|
session
|
HTTP
|
LinkedIn
|
|
lidc
|
Is needed to store performed actions on the website (marketing/tracking).
|
1
day
|
HTTP
|
LinkedIn
|
|
bscookie
|
Is needed to store performed actions on the website (marketing/tracking).
|
2
years
|
HTTP
|
LinkedIn
|
|
X-LI-IDC
|
Is needed to provide cross-page functionality (marketing/tracking).
|
session
|
HTTP
|
LinkedIn
|
|
AnalyticsSyncHistory
|
Stores the time when the user was synchronized with the "lms_analytics" cookie.
|
30
days
|
HTTP
|
LinkedIn
|
|
lms_ads
|
Is needed to identify LinkedIn members outside of LinkedIn.
|
30
days
|
HTTP
|
LinkedIn
|
|
lms_analytics
|
Is needed to identify LinkedIn members for analytics purposes.
|
30
days
|
HTTP
|
LinkedIn
|
|
li_fat_id
|
Required for indirect member identification used for conversion tracking, retargeting and
analytics.
|
30
days
|
HTTP
|
LinkedIn
|
|
U
|
Is needed to identify the browser.
|
3
months
|
HTTP
|
LinkedIn
|
|
_guid
|
Is needed to identify a LinkedIn member for advertising via Google Ads.
|
90
days
|
HTTP
|
LinkedIn
|
![[Translate to English:] Eine visuelle Übersicht der XR-Roadmap der TU Wien mit sechs zentralen Schritten zur Integration von Extended Reality (XR) in die Lehre: (1) Content-Identifikation – Auswahl relevanter Lehrinhalte und Technologien; (2) Content-Erstellung – Entwicklung von 3D-Modellen und deren Umsetzung in XR-Inhalte; (3) Implementierung – Integration der XR-Inhalte in Plattformen wie TUWEL, MR Lab und Davis Lab; (4) Schulung – Ausbildung von Lehrenden, Studierenden und Support-Personal im Umgang mit XR-Technologie; (5) Unterstützung – Begleitung und Motivation während der ersten Umsetzungen; (6) Buchungssystem – Organisation des Zugangs zu XR-Ressourcen über MR Lab und Davis Lab.](/fileadmin/_processed_/f/8/csm_roadmap__3__40d94f2af8.png)
