CamBuildr Connect Sync extends the power of CamBuildr Connect by enabling automatic data synchronization between connected CamBuildr instances — such as between a central organization (“Mothership”) and its regional chapters. This feature allows you to build a unified, transparent database while keeping local operations autonomous.
Note: This feature is not enabled by default. Please contact our team to set it up for your organization.
What You Can Do with Connect Sync?
Synchronize supporters across chapters automatically
Unify consent and tagging data across all levels
Collect and centralize actions, such as petitions, event signups, or volunteering
Mirror supporter records in both directions (bi-directionally)
Aggregate donations from all instances into a single view
Control what gets synced using custom criteria (tags, ZIP codes, audiences, etc.)
What Gets Synchronized?
Once configured, the following information can be automatically synced between two connected CamBuildr instances:
Basic Person Data
Name, email, phone number, ZIP, address, gender
Custom Fields
Only those explicitly selected during the setup
Tags & Consents
Including whether a tag requires propagation when removed
Active Actions
Including petitions, signups, or any campaign interaction
Donations
Only if syncing is configured to include financial data (“ALWAYS” mode)
Each sync is based on a CamBuildr-to-CamBuildr Connection, which can be configured for each direction (Host → Chapter and Chapter → Host).
Sync Criteria
You can define when a contact should be synchronized using one of the following criteria:
Always: All eligible people will be synced
ZIP-Code Match: Only people from specific regions
Tag Match: Only people with certain tags
Target Audience Membership: People who are part of a predefined segment
Never: No automatic sync takes place
Once a person is synced in either direction, updates or actions for that person will always be mirrored, even if they no longer meet the original criteria.
How the Sync Works
Initial Sync
When a person is created or updated and meets the sync criteria, they are pushed to the other CamBuildr instance.
Tag/Consent Update
When a tag (or consentable tag) is added or removed, it is synced accordingly. If the tag has is_propagating_detachment set to true, removals will also sync.
New Actions
Interactions like signing a petition or RSVPing to an event are logged as “CamBuildr Connect Actions” with clear origin information.
Unsubscribe Handling
If a user unsubscribes, this is mirrored in the connected CamBuildrs.
Donations
Synced only if explicitly enabled. Donations appear in the other system, complete with a mapped “donated” action.
Changes triggered by another sync do not re-trigger a sync back. This avoids infinite loops.
How It Looks in the UI
Person Profile: You’ll see which other CamBuildr the person is synced with, and when the last sync occurred.
Actions: Marked with a CamBuildr Connect icon and source name.
Segmentation: You can filter by synced chapters and their actions while creating target audiences.
Connections Overview: Shows which connections have active sync enabled.
Setup Requirements
To activate CamBuildr Connect Sync, we will need the following from you:
Mothership (Host) CamBuildr instance
At least Chapter CamBuildr instance
List of tags and consents to sync
List of custom fields to sync
Sync criterion (e.g., tag, ZIP, always, etc.)
Want to Enable This?
Reach out to us via the in-app chat or email us at [email protected]. Our team will guide you through activating and configuring CamBuildr Connect Sync based on your organizational needs.