Content-Management-System
Description of Service
The Content Management System (CMS) provides the ability to create & modify the contents on this Website for authorized users. Furthermore it integrates all relevant features like e.g. car configurator, login or forms into the Website.
***Technical information***
ow_aem_jwe : This is the Encrypted token that assures us and our integrated apps that the user that did the login is authorized to view the personal information (Session)
ow_aem_jws : This is the Encrypted token that assures us and our integrated apps that the user that did the login is authorized to view the personal information (Session
ow_aem_loginstate : This a token that assures us that the user that did the login is the correct one (Session)
ow_aem_missingDataConfig : This informs our integrated apps of the login status of the visitor (Session)
scrollHintWasShown : This informs our CMS if all required personal info is provided, and if not asks the user if he wants to complete the user form (Permanent)
***Navigation information***
callback_uri : This cookie allows us to take the end user to the intended webpage after a successful login. (Permanent)
callback_url : This cookie allows us to take the end user to the intended webpage after a successful login. (Permanent)
ow_aem_apiGatewayConfiguration : This informs our integrated apps of the available sources of information (Session)
ow_aem_changeemail : This informs our integrated apps of the URL to point the user in case of a change in email is requested (Session)
ow_aem_ciamLoginUrl : This informs our integrated apps of the URL to point the user, if a login is required (Session)
ow_aem_ciamLogoutUrl : This informs our integrated apps of the URL to point the user if a logout is required (Session)
ow_aem_ciamRegistration : This informs our integrated apps of the URL to point the user if a registration is required (Session)
ow_aem_confirmregistration : This informs our integrated apps of the URL to point the user when confirming the registration entry (Session)
ow_aem_everLoggedIn : This informs our integrated apps if it is the first time the user is on our page, so all login checks that are in place are run. (Permanent)
ow_aem_loginLinkText : This informs our integrated apps of the text to be present on every login button, for consistency (Session)
ow_aem_logoutLinkText : This informs our integrated apps of the text to be present on every logout button, for consistency (Session)
ow_aem_passwordreset : This informs our integrated apps of the URL to point the user when requesting a password reset (Session)
ow_last_application : This informs our integrated apps of the last app used by the user (Session)
ow_last_linkname : This informs our integrated apps of the last visited URL the user has browsed in our platform (Session)
ow_aem_sub : Internal checking and validation code (encripted) (Session)
ow_aem_postLoginCallbackUrl : Redirect Target after login has been triggered. (Session)
ow_aem_postLogoutCallbackUrl : Redirect Target after logout has been triggered. (Session)
***Personal information***
ow_aem_consent : This informs our integrated apps if the user has given his consent for personal data collection, even before the registering process, legal requirement in some parts of the world (Session)
ow_aem_email : This informs our integrated apps of the authorized e-mail for personalization purposes (Session)
ow_aem_firstname : This informs our integrated apps of the user's first name, for personalization purposes (Session)
ow_aem_gender : This informs our integrated apps of the user's gender, for personalization purposes (Session)
ow_aem_lastname : This informs our integrated apps of the user's last name, for personalization purposes (Session)
ow_aem_name : This informs our integrated apps of the user's name, for personalization purposes (Session)
ow_aem_phone : This informs our integrated apps of the user's phone for personalization purposes (Session)
ow_aem_wkoUserData : This provides adititonal informations to our integrated apps for personalization purposes (e.g. the salutation to be used on a specific market with the logged in user) (Session)
ow_aem_wkoUserDataExtended : This provides adititonal informations to our integrated apps for personalization purposes (e.g. the salutation to be used on a specific market with the logged in user) (Session)
ow_aem_roles : This informs our integrated apps if a user has extra permissions to edit some contents (deprecated) (Session)
volume : Volume level that our audio player played the last content (to keep it as the default value for other audio contents) (Permanent)
aem:video:volume: : Volume level that our audio player played the last content (to keep it as the default value for other audio contents) (Permanent)
ow_aem_declarationOfConsent : OneDoC is the global Daimler owned Marketing Permission Platform, where a customer can sign to declare, whether he/she wants to be contacted for marketing purpose. (Session)
ow_aem_dealerContext : The Dealer context is a unique retailer identifier. This identifier is needed to create localized link outs and requests for applications. This ensures that any application shows results filtered for current dealer. (Session)
financeData : This provides adititonal informations to our integrated apps about the user's financial status (e.g. "Customer Type" and "Deposit Amount"). (Session)
cntxt_preferredDealer : This cookie is necessary to get the preferredDealer contextID, to be able to return the customer's preferredDealer (7 days)
UCMS-CNTXT-ID : This cookie is necessary to get the user context contextID, to be able to determine if the user is a private customer or a business customer. (7 days):
ucms.contextToken : This cookie is necessary to get the user context contextID, to be able to determine if the user is a private customer or a business customer, this is used when we can't pass the UCMS-CNTXT-ID. (Session)
cscs-token : This cookie identifies the session of a user so that the functionality of switching between private and business customer profile works. (Session)
ow_aem_customerConsentForProductInformation : Consent status for "Customer consent for product information consent". (Session)
ow_aem_enableDataUsages /ow_aem_dataUsageScopes : OneDoC is the global Daimler owned Marketing Permission Platform, where a customer can sign to declare, whether he/she wants to be contacted for marketing purposes. (Session)
ow_aem_selectedAssociatedVehicle_* : This informs our integrated apps of the last selected vehicle for personalization purposes. (Session)
ow_aem_userAssociatedVehicles : This informs our integrated apps about the user associated vehicles. (Session)
ow_aem_userAssociatedDealers : This informs our integrated apps about the user associated dealers. (Session)
***Redirect Target after login has been triggered.***
swsp:B2XCORE_AUTHENTICATION : This object stores the copy of the JWE and Logged sensitive Profile Data. (Session)
B2XCORE_SESSION : This indicate that browser wasn't close. (Session)
***Search***
aem--contentsearch-fss-session : This cookie is needed to provide the search function properly on every page of our website. (Session)
fss.sessiontoken : This is an anonymous token required to generate statistical data about FSS usage. (4 weeks)
fss.searchHistory : This token is used to store history of search suggestions in the user's browser. This token is suffixed with the market locale. E.g.: fss.searchHistory.de_DE. (Permanent)
***Vans***
ow_vans_last_linkname : This informs our integrated apps of the last visited URL the user has browsed in our platform (Session)
***Google Tag Manager ***
kpi : Stores information about which applications have been interacted by the user to avoid firing Marketing Tags multiple times within an application, thus impacting site performance. Cookie is only set when we have consent for paid media technologies. (Session)
Technologies Used
This list represents all technologies this service uses to collect data. Typical technologies are Cookies and Pixels that are placed in the browser.
-cookies