Lightweight analytics, not a marketing-cookie stack.
Last updated: 28 April 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.
Current public-site analytics
The current public site loads /analytics.js, which boots both Plausible Analytics and Ahrefs Web Analytics for TenderLead. It can also load Google Analytics 4 for measurement ID G-B7ORM3QXBZ, but only after a visitor allows analytics in the consent prompt. The setup measures page views on the main funnel and supporting pages, and Plausible still receives a small number of TenderLead-local conversion events such as waitlist joins, 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
TenderLead does not currently intend to rely on a broad set of non-essential tracking cookies on the public acquisition surface. Google Analytics may set analytics cookies only after consent is granted. Hosting, auth, or anti-abuse providers may still set strictly necessary 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 is for optional Google Analytics loading, not for authenticated app session cookies.
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.