Cookie policy

At ford-mobility.eu, we use technologies like cookies, pixels, and local storage to make our websites easier to use and to tailor content to be more relevant for you. This guide is designed to explain, as clearly as possible, what cookies are; the purpose of those used on our website; and what options you have to control or delete them – if you decide you want to.

What is a cookie?

Almost every website uses cookie technology. A cookie is a small file that saves Internet settings. It gets downloaded through a browser during the first visit to a website. When you next return to the site using the same device, the browser may check to see if a related cookie is present (i.e. containing the site name) and use the data inside the cookie to send back to the site.

This allows sites to recognise that the browser has visited before and, in some cases, vary the content shown to reflect that.

You can find more information about cookies at:

What Cookies do we use?

The cookies used on our website have been categorised below.

Category 1 – ‘Strictly Necessary’ Cookies

These cookies are essential in order to enable you to move around the website and use its features, such as accessing secure areas of the website. Without these cookies services you have asked for, like online account management functionality, cannot be provided.

  • _boomr_akamaiXhrRetry
    This cookie is necessary for the Akamai cache function. A cache is used by the website to optimize the response time between the visitor and the website. The cache is usually stored on the visitor’s browser.
  • AKA_A2
    This cookie is necessary for the Akamai cache function. A cache is used by the website to optimize the response time between the visitor and the website. The cache is usually stored on the visitor’s browser.  This cookie is used for Akamais advanced acceleration feature, which enables DNS Prefetch and HTTP2 Push.
  • BA
    This cookie is necessary for the Akamai cache function. A cache is used by the website to optimize the response time between the visitor and the website. The cache is usually stored on the visitor’s browser. The users bandwidth results are stored within this cookie to help ensure the bandwidth test isn't repeated for the same user repeatedly for the Akamai cache functionality 
  • RT
    This cookie is necessary for the Akamai cache function. A cache is used by the website to optimize the response time between the visitor and the website. The cache is usually stored on the visitor’s browser. This cookie contains information on the users session to support Akamais cache functionality 
  • ak_bmsc
    This cookie is used by Akamai to optimize site security by distinguishing between humans and bots
  • bm_sv
    This cookie is necessary for the Akamai cache function. A cache is used by the website to optimize the response time between the visitor and the website. The cache is usually stored on the visitor’s browser. The users bandwidth results are stored within this cookie to help ensure the bandwidth test isn't repeated for the same user repeatedly for the Akamai cache functionality 
  • unsupported-browsers-overlay-counter
    Used by Ford to determine whether to show the unsupported browser overlay when a user has visited the site with an unsupported browser
  • guxacc-cookiedisclaimer
    Used to store if a user has previously seen the Cookie Disclaimer bannee which contains legal information that describes to user what actions are performed with the use of cookies on the Ford website
  • CookieConsent
    Used to store a users cookie opt-in settings. This is neccesary for thr websites GDPR compliance
  • guxfoe-cookiedisclaimer
    Used to store if a user has previously seen the Cookie Disclaimer bannee which contains legal information that describes to user what actions are performed with the use of cookies on the Ford website
  • acc-unsupported-browsers-overlay-counter
    Used by Ford to determine whether to show the unsupported browser overlay when a user has visited the site with an unsupported browser
  • cookie-configuration
    Used to store a users cookie opt-in settings. This is neccesary for thr websites GDPR compliance

Category 2 – ‘Performance’ Cookies

These cookies collect information about how visitors use a website, for instance which pages visitors go to most often, and if they get error messages from web pages. These cookies don’t collect information that identifies a visitor. All information these cookies collect is aggregated and therefore anonymous. It is only used to improve how a website works.

  • s_cc
    Used to determine if cookies are enabled for anonymous Adobe Analytics performance monitoring
  • s_cp_pers
    Used to collect & persist the details of the last email campaign a user clicked through to the site from for Adobe Analytics performance monitoring
  • s_fid
    Sets an anonymous fall-back unique visitor ID for the user where the Adobe s_vi cookie cannot be set due to 3rd party restrictions for Adobe Analytics performance monitoring
  • s_p_s_prop8
    Used to collect & persist the traffic source type which referred the user for Adobe Analytics performance monitoring
  • s_p13_pers
    Used to collect & persist internal campaign codes from internal links within the website for Adobe Analytics Peformance monitoring
  • s_sq
    Used to collect information about the links clicked on by users for anonymous Adobe Analytics performance monitoring
  • s_suite
    Used to collect the Adobe report suite ID relating to the site that the user is viewing
  • s_vi_*
    Sets an anonymous visitor ID with date & time stamp to identify unique visitors for Adobe Analytics performance monitoring
  • v_starting
    Used to indicate the start of a visit to capture where the user came from
  • s_p30_pers
    Used to collect & persist the details of the last Ford campaign a user clicked through to the site from for Adobe Analytics performance monitoring
  • s_p17_pers
    Used to collect & persist the details of the last display campaign a user clicked through to the site from for Adobe Analytics performance monitoring
  • AMCV_*AdobeOrg
    Used to identify a unique visitor ID that can be used by Adobe Experience Cloud services
  • AMCVS_*AdobeOrg
    Used as a flag indicating that the session has been initialised for use in Adobe Experience Cloud services
  • s_ecid
    Used to store a copy of the Adobe Experience Cloud ID to allow persistent ID tracking in the 1st-party state and is used as a reference ID if the AMCV cookie has expired
  • dtCookie
  • Tracks visit across multiple requests for Dynatrace performance monitoring 
  • dtLatC
    Measures server latency for Dynatrace performance monitoring 
  • dtPC
    Used by Dynatrace to identify proper endpoints and ideal location for performance montoring
  • dtSa
    Used to store contextual information of user actions to persist across pages for Dynatrace performance monitoring
  • ruxitagent_*_Store (e.g. ruxitagent_c1248d9aea60111f_Store)
  • Used by Dynatrace to cache the last monitor beacon response, which contains the configuration for the real user monitoring JavaScript library for Dynatrace. It doesn't store any user-related data in localStorage
  • rxec
    Used by Dynatrace to manage the availability and performance of the site and the impact on user experience in the form of deep transaction tracing, synthetic monitoring, real user monitoring, and network monitoring.
  • rxlatency
    Measures server latency for Dynatrace performance monitoring 
  • rxpc
    Used by Dynatrace to identify proper endpoints and ideal location for performance montoring
  • rxsession
    Tracks visit across multiple requests for Dynatrace performance monitoring
  • rxvisitid
    Sets a unique visit ID for the session for Dynatrace performance monitoring 
  • rxVisitor
    Sets a unique visitor ID for the user for Dynatrace performance monitoring to identify the visitor to correlate sessions
  • rxvt
    Stores timestamps for Dynatrace performance monitoring to identify when sessions start & end
  • ruxitagentjs_*_Store  (e.g. ruxitagentjs_c1248d9aea60111f_Store)
    Used by Dynatrace to cache the last monitor beacon response, which contains the configuration for the real user monitoring JavaScript library for Dynatrace. It doesn't store any user-related data in localStorage
  • dtDisabled
    Used by Dynatrace to manage the availability and performance of the site and the impact on user experience in the form of deep transaction tracing, synthetic monitoring, real user monitoring, and network monitoring.
  • dtsrVID
    Used by Dynatrace to manage the availability and performance of the site and the impact on user experience in the form of deep transaction tracing, synthetic monitoring, real user monitoring, and network monitoring.
  • dtsrE
    Used by Dynatrace to manage the availability and performance of the site and the impact on user experience in the form of deep transaction tracing, synthetic monitoring, real user monitoring, and network monitoring.
  • dtsrTID
    Used by Dynatrace to manage the availability and performance of the site and the impact on user experience in the form of deep transaction tracing, synthetic monitoring, real user monitoring, and network monitoring.
  • internalNavigationID
    Stores a random ID which ensures that a user can be uniquely identified as a guest or logged -in user. Functions such as "Items last viewed " or retention of the logged -in state are connected with this cookie.

Category 3 – ‘Functionality’ Cookies

These cookies allow the website to remember choices you make (such as your user name, language or the region you are in) and provide enhanced, more personal features. For instance, a website may be able to provide you with local weather reports or traffic news by storing in a cookie the region in which you are currently located. These cookies can also be used to remember changes you have made to text size, fonts and other parts of web pages that you can customise. They may also be used to provide services you have asked for such as watching a video or commenting on a blog. The information these cookies collect may be anonymised and they cannot track your browsing activity on other websites.

Category 4 – ‘Targeting/advertising’ Cookies

These cookies are used to deliver adverts more relevant to you and your interests. They are also used to limit the number of times you see an advertisement as well as help measure the effectiveness of the advertising campaign. They are usually placed by advertising networks with the website operator’s permission. They remember that you have visited a website and this information is shared with other organisations such as advertisers. Quite often targeting or advertising cookies will be linked to site functionality provided by the other organisation.

  • _dp
    Used to determine if Audience Manager can set other cookies in the demdex.net domain in a third-party context 
  • aam_uuid
    Used to assign a unique ID to a device so that Audience Manger can perform basic functions such as visitor identification, ID synchronization, segmentation, modelling and reporting for targeting purposes
  • AAMC_fordeu_0
    Used to set region flag for Adobe Audience Manager
  • demdex
    Used to assign a unique ID to a site visitor so that Audience Manger can perform basic functions such as visitor identification, ID synchronization, segmentation, modelling and reporting for targeting purposes
  • dextp
    Records the last time Audience Manager made a data synchronization call with data provider ID & timestamp for targeting purposes
  • dpm
    Used to record that a call from Adobe Audience Manager or the ID service is passing in data for synchronization or requesting an ID for targeting purposes.
  • dst
    This is set by Audience Manager when there is an error sending data to a destination in the targeting workflow
  • ev_sync_dd
    Third-party, ad exchange-specific cookie that syncs a users Adobe Experience Cloud ID with the partner ad exchange. It's created for new visitors and sends a synchronization request when it has expired.
  • ev_sync_nx
    Third-party, ad exchange-specific cookie that syncs a users Adobe Experience Cloud ID with the partner ad exchange. It's created for new visitors and sends a synchronization request when it has expired.
  • ev_sync_ix
    Third-party, ad exchange-specific cookie that syncs a users Adobe Experience Cloud ID with the partner ad exchange. It's created for new visitors and sends a synchronization request when it has expired.
  • ev_sync_ax
    Third-party, ad exchange-specific cookie that syncs a users Adobe Experience Cloud ID with the partner ad exchange. It's created for new visitors and sends a synchronization request when it has expired.
  • ev_sync_bk
    Third-party, ad exchange-specific cookie that syncs a users Adobe Experience Cloud ID with the partner ad exchange. It's created for new visitors and sends a synchronization request when it has expired.
  • ev_sync_fs
    Third-party, ad exchange-specific cookie that syncs a users Adobe Experience Cloud ID with the partner ad exchange. It's created for new visitors and sends a synchronization request when it has expired.
  • ev_sync_ox
    Third-party, ad exchange-specific cookie that syncs a users Adobe Experience Cloud ID with the partner ad exchange. It's created for new visitors and sends a synchronization request when it has expired.
  • ev_sync_pm
    Third-party, ad exchange-specific cookie that syncs a users Adobe Experience Cloud ID with the partner ad exchange. It's created for new visitors and sends a synchronization request when it has expired.
  • ev_sync_tm
    Third-party, ad exchange-specific cookie that syncs a users Adobe Experience Cloud ID with the partner ad exchange. It's created for new visitors and sends a synchronization request when it has expired.
  • ev_sync_yh
    Third-party, ad exchange-specific cookie that syncs a users Adobe Experience Cloud ID with the partner ad exchange. It's created for new visitors and sends a synchronization request when it has expired.
  • ev_sync_rc
    Third-party, ad exchange-specific cookie that syncs a users Adobe Experience Cloud ID with the partner ad exchange. It's created for new visitors and sends a synchronization request when it has expired.
  • everest_g_v2
    This cookie is used by Adobe and carries out information about how the end user uses the website and any advertising that the end user may have seen before visiting the said website. 
  • everest_session_v2
    This cookie is used by Adobe and carries out information about how the end user uses the website and any advertising that the end user may have seen before visiting the said website.
  • gglck
    Used by Adobe for targeted ads and to document efficacy of each individual ad.

Web Beacons

Some of our Web pages may contain electronic images known as Web Beacons (sometimes known as clear gifs) that allow us to count the number of users who have visited these pages.

Web Beacons collect only limited information, these include a cookie number; the time and date of a page view, and a description of the page where the Web Beacon resides.

We may also carry Web Beacons that are placed by third party advertisers. These Beacons do not carry any personally identifiable information and are only used to track the level of effectiveness of a particular campaign.

Controlling and deleting cookies

If you want to change how a browser uses cookies, including blocking or deleting cookies from the ford-mobility.eu (or any other website in fact) you can do so by changing the browser settings.

To control cookies, most browsers allow you to either accept or reject all cookies, only accept certain types of cookies, or prompt you each time a site wishes to save a cookie. It’s also easy to delete cookies that are already saved on your device by a browser.

The processes for controlling and deleting cookies vary depending on which browser you use. To find out how to do so with a particular browser, you can use the Help function within it or alternatively you can visit https://www.aboutcookies.org which explains, step-by-step, how to control and delete cookies in most browsers.

Tracking Policy

At ford-mobility.eu we use Adobe Analytics to track anonymous usage information. We collect information about how visitors interact with our site.

We do not track any personal information. For example, if you opt-in for an email contact that action will be logged, but your email address will not.

Collected data can be used to help us improve our website and to deliver the best tailored experience.