A lightweight tracking setup, not an ad-tech stack.

How the public site is set up today.

CompeteDesk currently uses lightweight website analytics and event tracking to understand page views, sample-brief usage, guide usage, CTA clicks, and request-form activity. The current setup is intended to measure demand, search-facing performance, and site usefulness without turning the site into a retargeting surface.

What analytics are in use.

• The site loads Plausible analytics for high-level CompeteDesk traffic measurement.
• The site loads Google Analytics 4 for public page-view and safe event measurement. GA4 is configured with IP anonymisation enabled, Google signals disabled, and ad personalisation signals disabled.
• The site also loads Ahrefs Web Analytics as a lightweight supplemental measurement layer for SEO and traffic analysis.
• The public pages also send a small set of first-party CompeteDesk event signals to the CompeteDesk tracking endpoint, such as page path, referring host, CTA clicks, sample-brief views, guide clicks, checkout CTA clicks, and successful enquiry events.
• That internal event log is intended for CompeteDesk only. It is not a shared portfolio collector for SHVL, TenderLead, or other brands.
• Search Console and Bing Webmaster are used separately for search-query and indexing data; they are not in-page marketing trackers.
• The current setup is meant to stay content-light. It is for site and offer measurement, not for cross-site profiling.

Where technical provider behaviour may still apply.

CompeteDesk does not currently intend to rely on advertising or retargeting cookies for the public site. However, hosting, security, or anti-abuse providers may still set strictly necessary technical cookies or challenge tokens in some circumstances, especially if suspicious traffic protection is triggered.

Those technical controls are separate from marketing tracking and may be required to keep forms and public pages available.

What is not part of the current setup.

• No ad-network retargeting pixels.
• No cross-site behavioural profiling for advertising.
• No shared portfolio event collector sitting behind CompeteDesk.
• No current public-site claim that you are being dropped into a broad cookie-marketing funnel.

If the tracking model changes, this page should too.

If CompeteDesk later adds materially different analytics, testing tools, advertising pixels, or consent logic, this notice should be updated so the public description stays accurate.