Cookies
Last updated: 7 October 2026
This page explains what the TenderLead public site currently does for analytics, whether it intentionally relies on non-essential cookies, and where technical provider behaviour may still apply.
Your analytics choice
Checking your saved choice.
You can withdraw permission for optional analytics or make a new choice at any time. Withdrawing stops optional analytics on this page and subsequent page loads, and removes Google Analytics cookies that this site can access. The page reloads to stop scripts already loaded. Reload other already-open TenderLead tabs to apply the choice there too. Information previously sent to a provider cannot be recalled.
Current public-site analytics
The public site and the signed-in app load /analytics.js. It loads Plausible Analytics, Ahrefs Web Analytics and Google Analytics 4 (measurement ID G-B70RM3QXBZ) only after a visitor allows analytics in the consent prompt. Declining loads none of them. The setup measures page views on the main funnel and supporting pages. With consent, TenderLead counts preview-auth starts by entry page and sign-in method without storing email addresses, company details or full referring URLs. With analytics consent and verified sign-in, TenderLead also saves the first tagged entry page, source and medium against your account, with the consent version and recording time, to compare profile completion, trial starts, positive tender ratings and paid access by channel. Historical or non-consented sources remain unknown. Plausible also receives a small number of TenderLead-local conversion events, including preview setup views, fixed setup-blocker choices, preview requests, sign-in link requests, checkout-start clicks and activation-detail submissions after payment.
- The current tracking setup is for lightweight site measurement, not ad retargeting.
- The setup no longer depends on a cross-brand tracking endpoint.
- Plausible and Ahrefs Web Analytics are intended to work without a marketing or advertising cookie stack.
- Google Analytics is treated as optional analytics and is not loaded until consent is granted.
- If the analytics model becomes broader later, this page should change with it.
Cookies and technical provider behaviour
Google Analytics may set analytics cookies only after consent is granted. Cloudflare's web analytics beacon has been observed loading before a visitor makes a choice. It is outside the TenderLead analytics controls above. Hosting, auth, or anti-abuse providers may also set technical cookies or challenge tokens in some circumstances.
- Security or bot-protection tools may set technical cookies if suspicious traffic is detected.
- If you use sign-in or OAuth routes, necessary session-related cookies may apply for that flow.
- Those technical behaviours are different from ad-tech profiling.
What is not part of the current setup
- No current claim that the site is running a retargeting or ad-pixel stack.
- No current claim that public-site analytics are being used to build advertising audiences.
- The consent prompt controls optional Google Analytics, Plausible and Ahrefs loading, not authenticated app session cookies or Cloudflare's beacon.
Related pages
For waitlist data, see Privacy. For site-level use terms, see Terms. For scoring inputs and public-source boundaries, see Source quality. For the public-site accessibility target, see Accessibility.