This article explains the end-to-end process of creating a Campaign in Salesforce, creating an Event in Azavista, and synchronizing Contacts between both systems. It also mentions External ID as the identifier, which in this context refers to the Salesforce Record ID stored in Azavista.
1. Create a Campaign in Salesforce
-
Log in to Salesforce.
-
Navigate to Campaigns.
-
Click New.
-
Enter required details:
-
Campaign Name
-
Type
-
Status
-
Start and End Date
-
-
Click Save.
The Campaign will act as the parent record for synced participants (Campaign Members).
2. Create an Event in Azavista
-
Log in to Azavista.
-
Go to Events → Create Event.
-
Complete required event details.
-
Save the event.
If bi-directional sync is enabled, the Event may also be created automatically from Salesforce using a configured Event Template.
3. Link Campaign and Event
-
Ensure the Salesforce Campaign is connected to the Azavista Event via the integration settings.
-
The integration uses the Salesforce Record ID (External ID) to track and match records.
-
Users cannot change which field is used as the identifier.
4. Add Contacts to the Salesforce Campaign
-
Open the Campaign in Salesforce.
-
Click Add Contacts.
-
Select existing Contacts or create new ones.
-
Save to create Campaign Members.
These Campaign Members are synced as Participants in Azavista. The system matches records using Salesforce Record ID; email is only used if no ID exists.
5. Run Synchronization
-
Trigger manual sync (if available), or
-
Wait for scheduled automatic sync.
During synchronization:
-
Existing Contacts with Salesforce IDs are matched and updated.
-
New Contacts without IDs are matched by email fallback or created as new Participants.
-
Duplicate prevention depends on clean data; the system does not merge duplicates automatically.
Validation Checklist
Confirm the Event exists in both Salesforce and Azavista.
Verify Campaign Members appear as Participants in Azavista.
Check sync logs for errors.
Ensure Salesforce Record IDs are correctly stored in Azavista (External ID).
Best Practices
-
Maintain clean, unique Contact records in Salesforce.
-
Test with a small group of Contacts before large-scale sync.
-
Understand that identifier logic is fixed; users cannot choose alternative fields.
This version reflects the system-defined identifier hierarchy: Salesforce Record ID (primary) → Email (fallback for Contacts only), and clarifies that External ID in this context is the stored Salesforce ID, not a configurable custom field.