Zintara integration consent and data mapping: keep permission evidence distinct

Define the decision

A lead status or positive reply is not a universal permission record. Different systems can use similar labels for different purposes. Record what each field means, its source and who is allowed to change it.

Work through the procedure

1. List the business purpose and minimum data needed by each consumer.
2. Map source identifiers and timestamps where available.
3. Define precedence for opt-outs and conflicting states.
4. Keep unknown permission evidence marked unknown.
5. Test a later exclusion arriving after a contact was already exported.

Worked example

The following is a synthetic example for this procedure, not a customer result or performance benchmark.

Source A: contact exists
Source B: recipient requested no further outreach
Merge decision: the exclusion must not be overwritten by the mere existence of a record
Audit note: preserve the source and time of the request

Read the result

The map should distinguish facts from workflow labels. A CRM checkbox created during import cannot retroactively supply evidence that was absent in the source.

Check before moving on

1. Review who can access transferred message or contact data.
2. Test conflicting updates in both arrival orders.

Limits and next action

This is an operational mapping procedure, not legal advice or a claim that Zintara supplies a complete consent-management system. Obtain appropriate review for the actual jurisdiction and purpose.

Source: Zintara implementation and product context