Privacy rules
HubSecure only loads analytics after the visitor accepts analytics cookies. Events are aggregate and do not include form contents, names, emails, company names or message text.
Provider
| Primary provider | Plausible |
| Domain | hubsecure.ai |
| Consent key | hs_cookie_consent |
| Runtime helper | window.hsTrack(eventName, props) |
| Future tag manager stream | window.dataLayer |
Tracked events
| Event | Trigger |
|---|
| Page Ready | Page load after scripts are ready. |
| Demo CTA Click | Any link to the demo page. |
| Start Free CTA Click | Any link to onboarding. |
| Pricing CTA Click | Any link to pricing. |
| Blog Search | Debounced blog search input with result count. |
| Blog Filter Click | Blog category chip click. |
| Blog Card Click | Article card click from the blog index. |
| Form Submit Attempt / Success / Error | Demo and contact forms. |
| Newsletter Submit Attempt / Success / Error | Newsletter popup form. |
| Template Print Click | Printable resource template button. |
| Outbound Link Click | External link click. |
Operating rules
- Do not send raw form values to analytics.
- Keep event property values short and non-sensitive.
- Do not add advertising pixels without updating the cookie banner and cookie policy.
- Treat analytics as SEO and product feedback, not user profiling.