Within the integration between Salesforce and Azavista, records are not configurable in terms of identifier selection.

The integration uses a fixed, system-defined matching hierarchy. Users cannot configure or choose which fields act as unique identifiers.

Contacts

Contacts are identified using a strict priority model:

1. Salesforce Record ID (Primary Identifier)

• The Salesforce Record ID is the authoritative identifier.
• It is stored in Azavista (visible in the Inspect tab).
• If the Record ID exists, matching is strictly ID-based.
• The existing record is updated.
• Email is not evaluated in this case.

2. Email (Fallback Only)

Email is used only when:

• No Salesforce Record ID has yet been stored.

In this scenario:

• The system attempts to match by Email.
• If a matching email is found, the Salesforce ID is stored and used going forward.
• If no match is found, a new record is created.

External ID – Clarification

In the context of this integration:

“External ID” refers to the Salesforce Record ID stored inside Azavista.

It does not refer to:

• A configurable Salesforce Custom External ID field
• A user-defined identifier
• A selectable matching option

The integration does not allow configuration of alternative External ID fields for matching.

Organisations (Accounts)

Organisations are identified by:

• Salesforce Account Record ID

Matching is based on this ID once established.
There is no configurable option to match by:

• Custom External ID fields
• Account Name

Account Name is not used as a guaranteed unique identifier for synchronization.

Participants / Campaign Members

Participation records are identified by:

• Their Salesforce Record ID
• System-managed linkage between Contact ID and Event ID

This ensures that:

• A Contact can participate in multiple events
• Participation records remain distinct
• Referential integrity is maintained

There is no composite matching configuration available to users.

Events

Events (including Campaign Events created via the integration) are identified by:

• The relevant Salesforce Record ID

There is no configurable alternative identifier.

Best Practice

Because identifier logic is fixed and not configurable:

• Maintain clean, duplicate-free Contact data (especially Email).
• Avoid creating multiple Contacts with identical email addresses.
• Do not manipulate Salesforce Record IDs.
• Review data quality before enabling synchronization.

Summary

Record identification in the Salesforce–Azavista integration follows a fixed hierarchy:

1. Salesforce Record ID (Primary and authoritative identifier)
2. Email (Contacts only, fallback when no ID exists)
3. Otherwise → new record creation