Centralized Consent ManagementIntegrated with SAP, CRM and ERP systems

Manage consent records from your group’s SAP, Salesforce, CRM/xCRM and ERP applications in one place. Track data from dozens of companies by company and brand, and connect to İYS through its API.

Tosyalı HoldingTosyalı HoldingSAP integration case study →
Video in Turkish
SAP
Salesforce
Dynamics 365
API

Consent management across group companies

Within a holding company, consent records are stored in separate CRM and ERP systems, websites, stores and call centers. We connect these systems through APIs so the group can manage its consent database centrally. Each record keeps its company, brand and source information.

  • Company and brand records

    Each consent record is stored with the company, brand and source system it belongs to.

  • Data transfer between applications

    Records from CRM, xCRM, ERP and custom applications are transferred to the central database through APIs.

  • Central monitoring

    Consent status, İYS transfer results and updates sent to source systems can be checked in one place.

How consent data moves between systems

Companies and data sources

  • Holding and group companies
  • SAP, ERP and CRM/xCRM
  • Web, mobile, stores and call centers

Central consent database

Company and brand · consent status · record history

Connected applications

  • SAP, Salesforce and other CRM/ERP
  • Marketing and communication apps
  • İYS API
Records are transferred with their company, brand and source information. Destination applications are selected according to the scope of consent and available API connections.

CRM, xCRM and ERP connections

We integrate SAP, Salesforce, Microsoft Dynamics 365 and custom applications through APIs. Group companies can use different software. Consent records in each system are matched to the central database, and updates are sent to the relevant applications.

Integration scope is planned around the product and version in use, available API access, data fields and business workflows.

SAP consent data integration

We match customer and communication records in SAP with the central consent database. Consent changes, opt-outs and transfer results are sent to the relevant systems through the connections agreed for the project.

  • Map source records and data fields
  • Transfer consent and opt-out updates
  • Return processing results to source systems
  • Compare and reconcile records

İYS API integration

Use the API of İYS, Türkiye’s Message Management System, to transfer commercial communication opt-ins and opt-outs for the relevant company and brand. Match consent changes and processing results from İYS to central records and return updates to your CRM and ERP applications.

  • Transfer opt-ins and opt-outs

    Send consent changes from source applications to İYS for the relevant brand.

  • Return updates and results

    Bring consent changes from İYS and transfer results back to the relevant source systems.

  • Track errors and reconcile records

    Monitor pending or failed transfers and track differences between source records and İYS results.

Consent and transaction tracking

Company and brand records

Consent records are stored with their company, brand and source-system information.

CRM, xCRM and ERP integration

Data is transferred between SAP, Salesforce and other enterprise applications through APIs.

Consent and opt-out tracking

Track which applications have received consent and opt-out updates.

Transfer and error monitoring

Transfers are tracked by status: successful, pending or failed.

Reconciliation and reporting

Records in source and destination systems are compared. Differences and processing results are reported.

Processing history

The record’s source, processing time and transfer result are kept in its history.

Setup and integration

We first review the group companies, their applications and existing consent records. We then define company and brand mappings, API connections and data transfer rules.

  1. Review existing systems

    Review group companies, brands and consent records in CRM/xCRM, ERP and other applications.

  2. Map data fields

    Define field mappings, update directions and control points.

  3. Connect APIs

    Establish data exchange between source and destination systems.

  4. Validate and launch

    Verify transfer, consent, opt-out and reconciliation scenarios.

Frequently asked questions

How are different companies within a group handled?

Companies, brands and data sources are mapped at the start of the project. Records retain the context of the company and brand for which consent was collected, and transfer rules are defined accordingly. Central management does not treat every company’s records as a single shared permission.

Can Salesforce and other CRM systems connect alongside SAP?

Yes. Systems such as SAP, Salesforce and Microsoft Dynamics 365, CRM/xCRM solutions and custom applications can be integrated through APIs. The product version, available API access and data structure determine the scope of each integration.

What does the İYS API integration cover?

The project defines opt-in and opt-out transfers for the relevant company and brand, retrieval of consent changes from İYS, return of processing results to source systems, and reconciliation workflows. API access and the methods to be used are verified during setup.

Discuss your consent management project

We can review your applications and İYS connection to define the scope of your integration.

Contact us
Ulaşcan Özbas

Ulaşcan Özbas

Senior Software Development Specialist | SaaS Platforms, Backend Architecture and İYS Systems