> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.conversive.ai/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.conversive.ai/_mcp/server.

## Manage Consent Across Every CRM, From One Place

We're excited to introduce the **Configurable Consent Sync** feature, designed to simplify and standardize consent management across multiple CRM platforms.

Consent data is foundational to compliant, trustworthy customer communication. But for teams operating across multiple CRM platforms, keeping that data accurate and synchronized has historically meant fragmented configurations, hardcoded field mappings, and a patchwork of manual workarounds. When consent changes in one system, there's no guarantee it reflects everywhere else, and that gap creates risk.

This release closes that gap. Configurable Consent Sync gives you a single, unified interface to define, manage, and synchronize consent data across all your connected CRM platforms, with no hardcoded dependencies and no platform-by-platform repetition.

## Supported Platforms

* Salesforce
* Zoho CRM
* Zoho Bigin
* HubSpot CRM
* Creatio
* Microsoft Dynamics 365

## What's New

### Enable Consent Sync via Toggle

Activate consent synchronization directly from the Integration page with a single toggle, no backend changes or developer intervention required.

### Configure Consent Mapping

Define exactly which CRM object (Contact, Lead, or Custom Object) and which consent field should be targeted, configured at a granular level per CRM to match your schema precisely.

### Dynamic Consent Sync

Consent updates are synced using record_id, ensuring that changes are applied to the exact corresponding record, not approximated or mismatched.

### Fully Configuration-Driven Approach

All mappings are driven by configuration, eliminating hardcoded field dependencies and making it easy to adapt as your CRM schemas evolve.

## Steps to Configure

1. **Navigate to the Integration Page:** Go to your connected CRM's Integration settings within the platform.
2. **Enable Consent Sync:** Locate the Consent Sync section and toggle it on to activate synchronization for that CRM.
3. **Select a CRM Object:** Choose the relevant object type, that is, Contact, Lead, or a Custom Object, that holds consent data for your use case.
4. **Map the Consent Field:** Select the specific field within that object that represents consent status.
5. **Save the Configuration:** Confirm your mapping. Changes take effect immediately for new consent sync events.
6. **Repeat Per CRM (if needed):** Each connected CRM can be configured independently, giving you full control over how consent is mapped per platform.

## Where this helps

* Teams managing customer consent across multiple CRM instances who need a single source of truth
* Compliance and operations teams who can't afford consent data falling out of sync between systems
* Admins looking to replace brittle, hardcoded field configurations with a flexible, maintainable setup

This feature is available now within the Integration page for all supported CRM platforms. Existing integrations are unaffected unless you explicitly enable and configure Consent Sync.

[**See how it works →**](https://docs.sms-magic.com/share/ITSZVT2MAoRxeOzLRqqp2g)