Features of the HubSpot ads tool help you better engage with your contacts while maintaining their privacy.
Please note: while these features are in HubSpot, your legal team is the best resource to give you compliance advice for your specific situation.
When you install a pixel using HubSpot, it will be added to all pages with the HubSpot tracking code installed. If you've set up a privacy policy banner, visitors to these pages will also be prompted to confirm they accept your privacy and consent settings. If you require visitors to opt into cookie tracking, pixels will not use cookies until the visitor confirms their consent.
If you want to allow users to edit or revoke their consent, you will need to work with a developer to implement that functionality using the HubSpot Tracking Code API. Learn more about implementing additional consent status and cookie removal functions in the developers documentation.
Please note: you can only install one pixel per ad network through HubSpot. If you need to install multiple pixels per network, you can use the Google Tag Manager. Pixels installed through the Google Tag Manager will not be automatically prompted with a privacy policy banner.
When you create contact list audiences in HubSpot, contacts from your lists are periodically synced to the corresponding ad network. The ad network then attempts to match these contacts to users on their network.
Each ad network requires different data to match a HubSpot contact to a user on their network. HubSpot encrypts and sends a contact's properties to the associated ad network, but ad networks can only use encrypted contact properties for matching purposes. Ad networks cannot use the data that HubSpot sends to augment the info they have for the corresponding user on their network.
HubSpot will encrypt and send different contact properties based on each network's requirements.
When you perform a GDPR compliant delete of a contact, HubSpot also deletes that contact from any syncing contact list audiences. HubSpot also sends a request to delete that contact from any syncing contact list audiences on the ad network itself. Successful deletion is subject to the ad network being able to match the encrypted contact information to a user in the respective audiences. Since this process ensures that your ad campaigns do not target GDPR-deleted contacts, it will also ensure you stay CCPA-compliant.
You can add a consent to contact field to your Facebook and LinkedIn lead generation ads. Any consent fields from these ads will now sync over to HubSpot as a new contact property. These properties will be labeled with [Ad Network] Consent before the property name. You can use these properties to create a list of contacts who have given you consent to be contacted.
To add a consent field when creating a new Facebook form or LinkedIn lead gen form in HubSpot:
You can add a consent field when creating a lead form in LinkedIn within the Lead details and custom questions step:
Once the consent field is added to a Facebook or LinkedIn form, this field will start syncing for all lead ad forms. If you already created a lead generation ad before adding the consent field, and this ad was already syncing with HubSpot, any new leads that come in through this existing ad will now sync the consent field with HubSpot. However, any leads that were created before the consent field was added to your lead ads will not have that field sync.