Set up your bannerConfigure Your ToolsMarketing Automation and CRM

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.

  1. Configure the third-party service.
  2. Map the selected configuration in the Consenter Manager.
  3. 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.

ConfigurationSummary
Configuration A — Medium riskForms only; Site Tracking not installed.
Configuration B — Higher riskSite 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 areaWhere to configure itConfiguration A — Medium riskConfiguration B — Higher risk
1Processing purposesOperator decisionReceive marketing offers (form)Support marketing analytics; Receive personalised marketing offers
2Site TrackingWebsite > Site Tracking; snippetOffOn
3Track by defaultvgo('setTrackByDefault', …)—false
4Consent signalvgo('process', 'allowTracking') on Consenter consent—Yes
5Contact identificationForm 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 fieldConfiguration A — Medium riskConfiguration B — Higher risk
Processing purposesReceive marketing offersSupport marketing analytics, Receive personalised marketing offers
Tracking methodNo trackingFirst party tracking (cross-session)
IdentifierDirect identifier (on submission)Device identifiers, Direct identifier
Data categoriesUser-provided data, direct identifierBrowsing and interaction data, Device identifiers, User-provided data, direct identifier, Users' profiles, Privacy choices
Legal role of data recipientProcessorProcessor
Personalisation modelNo personalisationProfile based
Maximum storage durationPer contact retentionPer cookie inspection
Processing locationUnited StatesUnited 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

On this page