How to manage tracking consent (GDPR) per channel in Webmecanik Automation?

Compliance with the General Data Protection Regulation (GDPR) requires obtaining strict, free, and explicit consent for tracking user behavior (such as email opens or link clicks).

To meet this obligation, Webmecanik Automation provides advanced tools allowing you to separate the authorization to send a message from the authorization to track it. This system complements the historic global unsubscription tool ("Do not contact").

Here is an overview of the different tools available to orchestrate this consent.

1. Initial activation in the Global Configuration

Any tracking consent management begins with its activation at your instance level.

• Where is it located? In the Tracking Settings of your Configuration menu.

• What is the effect? A main GDPR switch enables granular consent by channel (Email, SMS). As long as this option is not activated, tracking behavior remains standard. Once activated, it unlocks all the features described below.

2. Transparent collection via forms

To legally collect consent from your new contacts, your forms adapt.

• Multi-target consent field: You can integrate a single or multiple checkboxes into your forms.

• Double validation: This field allows the contact to simultaneously (or separately) accept the receipt of your communications and the tracking of their interactions (clicks for SMS, opens and clicks for emails).

3. Visibility and traceability on the contact profile

You maintain full visibility and proof of compliance regarding your contacts' choices at any time from their profile.

• "Do not track" badges: If a contact refuses tracking on a channel, a specific badge (e.g., Do not track: EMAIL) appears on their profile. This means you can continue to write to them if their subscription is active, but no behavioral data will be collected.

• Automatic log generation (History): As soon as an unsubscription or a withdrawal of tracking consent occurs, Webmecanik Automation instantly creates a dedicated log entry in the History tab of the contact profile. As shown in image_3b73d5.jpg, you will find a specific event of type "Do not contact" indicating the relevant channel (Email, SMS) as well as the explicit reason (e.g., "The contact has withdrawn their tracking consent on this channel").

• Preference Center: Your contacts can adjust their choices independently at any time. The contact preference center includes a dedicated column to check or uncheck tracking consent, channel by channel.

4. Targeting in Segments

Your databases become smarter thanks to native filters related to tracking.

• Specific filters: When creating a segment, you have access to new filtering criteria such as « Tracking consent refused - Email » or « Tracking consent refused - SMS ».

• Utility: This allows you to adapt your marketing strategies by separating "tracked" contacts from "non-tracked" contacts to scrupulously respect their privacy preferences.

5. Automation in Campaigns

Updating a contact's status can also be automated at the heart of your scenarios.

• Dedicated campaign action: The campaign builder includes an event allowing you to update the tracking consent status on the fly.

• Utility: For instance, you can choose to automatically update the consent of a group of contacts following a specific action or a precise user journey.