Last Updated: October 14, 2026
Unless otherwise expressly stated, terms in this Cookie Policy have the same meaning as defined in the Privacy Policy.
This Cookie Policy supplements the information contained in the Privacy Policy and describes how [insert legal entity name of Vertus/PYXiS Group business unit] use cookies and related technologies while providing the Services. This Cookie Policy explains what cookies and related technologies are, why we use them, and how you can manage your preferences when you visit our Sites.
Cookies are small text files that are placed on your device by websites that you visit. They are widely used in order to make websites work, or work more efficiently, as well as to provide information to the owners of the site.
We may use related technologies such as web beacons, pixels, embedded scripts, or other logging technologies.
We use cookies and related technologies for the following purposes:
These cookies are necessary for the website to function and cannot be switched off on our Sites such as setting your privacy preferences and for security and network management. You may set your browser to block these cookies, but some parts of the Sites may not work.
| Name of Cookie | Purpose | Typical Duration |
|---|---|---|
| webflow-session | Used for backend form management, processing submissions safely, anti-spam tokens, and keeping interactive native animations functioning seamlessly across pages. | Deleted when the browser session ends. |
| fs-consentConsent Pro | Stores the visitor's cookie consent choices (which categories were accepted or rejected) so the cookie banner does not reappear on every page and the choices are respected across the Sites. | 1 Year |
| __cf_bm / __cfruidCloudflare, including the HubSpot booking calendar | Used for bot management and security to protect the site and the embedded HubSpot booking calendar from malicious traffic. These cookies are set by Cloudflare, the network provider used by our site and by HubSpot. They are needed for the calendar to load and for visitors to book a demo. | __cf_bm: 30 Minutes; __cfruid: deleted when the browser session ends. |
These cookies allow us to count visits and traffics sources so we can measure and improve the performance of our Sites. They let us know which pages are the most and least popular and see how visitors move around our Sites. If you do not allow these cookies, we will not be able to measure performance of our Sites or use the information to improve our Sites.
| Name of Cookie | Purpose | Typical Duration |
|---|---|---|
| _gaGoogle Analytics | Distinguishes unique users and tracks overall site usage statistics. | 2 Years |
| _ga_<container-id>Google Analytics | Used by Google Analytics 4 to persist session state and count sessions and page views for our Sites. | 2 Years |
| YSCYouTube | Registers a unique ID to keep statistics of what videos from YouTube the user has seen. | Deleted when the browser session ends. |
| _Secure-YNIDGoogle | Tracks video player statistics and remembers user playback preferences | 6 Months |
| GPSYouTube | Registers a unique ID on mobile devices to enable tracking based on geographical location. | 30 Minutes |
| _clckClarity | Persists a unique Microsoft Clarity user ID and specific site preferences. It ensures that subsequent visits by the same user on that specific site are attributed to the exact same user ID. | 1 Year |
| _clskClarity | Connects and groups multiple consecutive page views by a single user into a unified session recording snippet. | 1 Day |
| _cltkClarity | Acts as a security token used by Microsoft Clarity for Diagnostic and Cross-Site Request Forgery (CSRF) protection during sessions | Session |
| SMMicrosoft Clarity | Used by Microsoft to synchronize the MUID identifier across Microsoft domains so that Clarity analytics can recognize the same browser. | Session |
| MUIDMicrosoft Clarity | Identifies unique web browsers visiting Microsoft services. Used by Microsoft Clarity for site analytics and telemetry. | 1 Year |
These cookies are used to measure the effectiveness of our advertising and to show you more relevant ads on other websites and platforms. They may be set by us or by third parties whose services we have added to our pages, such as advertising and social media partners. If you do not allow these cookies, you will still see ads, but they may be less relevant to you.
| Name of Cookie | Purpose | Typical Duration |
|---|---|---|
| _fbpMeta/Facebook Pixel | Used by Facebook to deliver advertisement products and track ad conversions. | 3 Months |
| li_sugr / UserMatchHistoryLinkedIn | Used to track visitors so that more relevant ads can be presented based on professional profiles. | 3 Months |
| VISITOR_INFO1_LIVE (and/or __Secure-YNID)YouTube | Tries to estimate the users' bandwidth on pages with integrated YouTube videos. It is also used to serve targeted advertisements based on viewing history. | 6 months |
| VISITOR_PRIVACY_METADATAYouTube | This third-party persistent cookie is set by YouTube in connection with embedded YouTube video players and iframe APIs on external websites. Its primary function is to securely log and store a visitor's cookie consent choice and privacy state (such as a base64-encoded string containing region data and consent preferences). This ensures that YouTube respects the user's specific privacy choices (like opting out of personalized tracking or targeted ads) across subsequent page loads and embedded media on that domain. | 6 months |
| __Secure-ROLLOUT_TOKENGoogle | This cookie is used by YouTube to manage the phased rollout, testing, and experimentation of new features. It helps Google control which interface variations, video player modifications, or new features are displayed to specific users. | 6 Months |
| __hstcHubSpot | The main cookie used by HubSpot to track website visitors. | 6 Months |
| hubspotutkHubSpot | Keeps track of a visitor's identity. It passes an opaque GUID (Globally Unique Identifier) to HubSpot upon form submission to assist in deduplicating contact records. | 6 Months |
| __hssrcHubSpot | Set whenever HubSpot modifies a session cookie to determine if the visitor has restarted their browser. If this cookie is absent when managing cookies, it indicates a brand-new session. | Expires when browser is closed. |
| __hmplHubSpot | Primarily used by HubSpot to handle and track custom marketing or communication platform routing details | Session or up to 6 months |
| HUBLYTICS_EVENTS_53HubSpot | Temporarily caches product and behavioral analytics tracking events generated by HubSpot internally before they are transmitted back over the network to the server. | Persistent or conditional on user consent configuration |
| __hsscHubSpot | Keeps track of sessions. Used to determine whether HubSpot should increment the session number and timestamps in the __hstc cookie. | 30 Minutes |
| messagesUtkHubSpot | Used by the HubSpot chat tool to recognize visitors who chat with us, so previous conversations can be retained. | 6 Months |
| _gcl_auGoogle Ads | Used by Google Ads to store and track conversions from ad clicks. | 90 Days |
| _gcl_lsGoogle Ads | Stored in the browser's local storage by Google Ads to retain ad-click information for conversion measurement. | Persistent in local storage until cleared |
| _rdt_uuidReddit Pixel | Used by Reddit to recognize visitors who arrive from Reddit ads, measure ad conversions and build advertising audiences. | 90 Days |
| li_adsIdLinkedIn Insight Tag | Stored in the browser's local storage by LinkedIn to attribute conversions to LinkedIn ads. | Persistent in local storage until cleared |
| bcookie / lidc / AnalyticsSyncHistoryLinkedIn | Set on LinkedIn domains by the LinkedIn Insight Tag to identify browsers, route requests and sync visitor data for LinkedIn ad conversion tracking and audiences. | bcookie: 1 Year; lidc: 1 Day; AnalyticsSyncHistory: 30 Days |
| snowplowOutQueue_ct_js-tracker_post2.expiresGartner Digital Markets / G2 conversion tracking, via Snowplow | Companions the event queue by simulating cookie-like expiration within the browser's local storage. It ensures older, stale events that failed to send over an extended period are cleared out predictably. | Programmatically set to match the tracker's standard session/cookie timeout configuration (typically mirrors a 30-minute window or a custom configured duration) |
| snowplowOutQueue_ct_js-tracker_post2Gartner Digital Markets / G2 conversion tracking, via Snowplow | Acts as a local browser cache to hold Snowplow Analytics events that haven't been successfully dispatched to the data pipeline yet. This prevents tracking data from being lost when a user navigates away from a page quickly. | Persistent in local storage until event cache is cleared |
You may change and manage your cookie preferences in a few ways.
In the cookie preference center: You can visit the cookie preference center in the footer and updating your preferences there.
Most web browsers allow you some control of most cookies through browser settings. To find out more about cookies, including how to see what cookies have been set, visit www.aboutcookies.org or www.allaboutcookies.org. For more information on how to control your cookies on your web browser, refer to the following pages on popular web browsers: Google Chrome, Microsoft Edge, Mozilla Firefox, Opera, and Apple Safari.
Please note that if you choose to block all cookies (including essential ones), our Sites may not function correctly.
We may update this Cookie Policy from time to time to reflect changes in our practices or for other operational or legal reasons.
If you have any questions about our use of cookies, please contact us via email at connect@tracxsystems.com.
Book a 30-minute demo. We'll show you exactly how Tracx handles your freight type, not the generic walkthrough every other vendor will give you. Bring your current pain points and we'll show you where they go away.
