01Who this is for
- Founders of SaaS startups, because they need to track how they may process user data.
- Marketing agencies managing multiple client funnels, to record consent for each lead.
- Ecommerce owners collecting orders through embedded order forms, to note legal basis when consent is not explicit.
02Customer consent tracking, explained
HighLevel provides ways to obtain a customer’s permission before handling their personal data. You can embed forms, surveys, webchat widgets, calendars or order forms on any funnel or website and ask the customer to agree. If a contact does not give explicit consent, you can record the legal basis by creating a tag and applying it to the contact manually or through an automation. The tag remains with the contact for future reference.
03How businesses use customer consent tracking
- SaaS startup. Add a form to the onboarding funnel to capture user consent. When a lead does not provide consent, create a tag that represents the legal basis and apply it through an automation so the reason for processing is recorded.
- Marketing agency. Insert surveys into client landing pages to ask for permission. For leads that skip the consent question, the agency creates a tag for the legal basis and manually tags those contacts to keep the documentation.
- Ecommerce store. Place an order form on the checkout page to collect consent on purchase. If a buyer does not tick the consent box, the store adds a legal basis tag to the contact record via a workflow.
04Before you start
- A privacy policy must be displayed at the moment personal data is collected.
05How to set up and use customer consent tracking in HighLevel
Collect consent from customers using HighLevel
- Add a form to a funnel or website.
- Add a survey to a funnel or website.
- Add a webchat widget.
- Add a calendar to a funnel or website.
- Add an order form to a funnel or website.
Track legal basis when consent is not given
- Create a tag that represents the legal basis.
- Apply the tag to contacts manually or by using an automation.
06Settings that matter
- Tag. Identifies the legal reason for processing a contact’s personal data when explicit consent is absent.
07How it connects to the rest of HighLevel
- Explore all contact management capabilities in HighLevel. All Contacts features
- Learn how to remove contacts and their data if needed. Delete contacts
- See pricing options for HighLevel plans. Pricing
Michael's take

I start by adding the privacy policy notice on every form, survey, webchat, calendar and order form.
Then I set up a tag for contacts that do not have explicit consent and apply it manually or with an automation.