ActiveCampaign
How to configure ActiveCampaign at different risk levels and map it in the Consenter Manager.
This work is licensed under CC BY-SA 4.0
Typical processing purposes: Support marketing analytics, Receive personalised marketing offers
Overview
This guide explains how to implement different privacy configurations for ActiveCampaign site tracking and how to reflect them in the Consenter Manager.
- Configure the third-party service.
- Map the selected configuration in the Consenter Manager.
- Update your privacy policy to reflect the actual implementation.
The configurations are comparative examples, not guarantees of legal compliance. Verify that the guide matches your product edition, implementation, and current provider documentation.
At a glance
Scope. ActiveCampaign forms and the Site Tracking code. ActiveCampaign, LLC is a US company.
What the service does in this scope. Site Tracking uses first-party cookies to track visits to every page with the tracking code; contacts are identified after submitting an ActiveCampaign form (with redirect to a tracked page) or via vgo('setEmail', …). For consent, ActiveCampaign instructs changing vgo('setTrackByDefault', true) to false and calling vgo('process', 'allowTracking') after the visitor agrees.
Configurations included.
| Configuration | Summary |
|---|---|
| Configuration A — Medium risk | Forms only; Site Tracking not installed. |
| Configuration B — Higher risk | Site Tracking with setTrackByDefault(false); allowTracking after Consenter consent; contacts identified. |
Default behaviour. The standard snippet contains setTrackByDefault(true); this is not suitable for EU visitors without prior consent.
Step 1 — Configure ActiveCampaign
| # | Configuration area | Where to configure it | Configuration A — Medium risk | Configuration B — Higher risk |
|---|---|---|---|---|
| 1 | Processing purposes | Operator decision | Receive marketing offers (form) | Support marketing analytics; Receive personalised marketing offers |
| 2 | Site Tracking | Website > Site Tracking; snippet | Off | On |
| 3 | Track by default | vgo('setTrackByDefault', …) | — | false |
| 4 | Consent signal | vgo('process', 'allowTracking') on Consenter consent | — | Yes |
| 5 | Contact identification | Form redirect / vgo('setEmail', …) | — | Yes |
Step 2 — Map the configuration in the Consenter Manager
Processing location. ActiveCampaign is a US enterprise subject to the US CLOUD Act; list the United States.
| Consenter Manager field | Configuration A — Medium risk | Configuration B — Higher risk |
|---|---|---|
| Processing purposes | Receive marketing offers | Support marketing analytics, Receive personalised marketing offers |
| Tracking method | No tracking | First party tracking (cross-session) |
| Identifier | Direct identifier (on submission) | Device identifiers, Direct identifier |
| Data categories | User-provided data, direct identifier | Browsing and interaction data, Device identifiers, User-provided data, direct identifier, Users' profiles, Privacy choices |
| Legal role of data recipient | Processor | Processor |
| Personalisation model | No personalisation | Profile based |
| Maximum storage duration | Per contact retention | Per cookie inspection |
| Processing location | United States | United States |
How is this guide?
Shape Consenter Together
Consenter is built on an open and participatory process that grows through community collaboration. Whether you share feedback, improve the documentation, or contribute to the Risk Configuration Guides or Technical Integration Guides, your expertise helps make Consenter more privacy-friendly, interoperable, and useful for everyone—including your own users and services: Get finally your benefits and control the risks when sharing personal data.
Need Help?
Last updated on