Skip to content
APIANT
API ReferenceAPI Appsv11

Sync Timing and Reliability

How donors are matched and synced to ActiveCampaign contacts, how DonorPerfect flags become tags, and why any automation that fires on contact creation or update needs a delay or tag-recheck step.

Overview

CRMConnect runs two scheduled automations for this pairing, keeping ActiveCampaign's contacts and deals current with DonorPerfect.

SyncWhat it doesDirectionRuns
Donor syncA new or updated DonorPerfect donor creates or updates the matching ActiveCampaign contact (fields + tags)DonorPerfect → ActiveCampaignEvery 5 minutes
Gift syncA new or updated DonorPerfect gift creates or updates the matching ActiveCampaign deal, linked to the donor's contactDonorPerfect → ActiveCampaignEvery 15 minutes (Gifts Pipeline add-on only)

There is no write-back direction here — ActiveCampaign doesn't push changes back into DonorPerfect.

How a donor is matched and synced

For every donor processed, the sync:

  1. Looks up the DonorPerfect donor to find a matching contact in ActiveCampaign, by email.
  2. If no ActiveCampaign contact exists yet: creates the contact and subscribes it to the configured ActiveCampaign list.
  3. If a contact already exists: reads its current tags and does a quick field update.
  4. Only after step 2 or 3 completes, the sync computes the DonorPerfect-flag-derived tags and adds/removes them on the ActiveCampaign contact.

Donors are matched to ActiveCampaign contacts by email, so a donor is only ever synced to one contact.

An email address is required for every ActiveCampaign contact

ActiveCampaign requires every contact to have an email address. A DonorPerfect donor with no email address will not sync to ActiveCampaign by default. If you need every donor represented in ActiveCampaign regardless of whether they have an email on file, ask your APIANT contact about enabling placeholder-email generation — a unique fake address is generated per donor so the contact can still be created. This is off by default.

Flags and tags

DonorPerfect flags sync to ActiveCampaign tags. Three account settings control how:

SettingWhat it doesDefault
Sync DonorPerfect flags with ActiveCampaign tagsWhether flags sync to tags at all. Off means the sync never touches tags.On
Remove ActiveCampaign tagsWhether the sync removes tags as well as adding them. Off means tags are only ever added.On
Remove only DonorPerfect flag tagsNarrows removal to tags that match the name of a DonorPerfect flag. A tag that doesn't match any DonorPerfect flag is never removed.On

The second and third settings only apply when flag sync is on, and the third only applies when removal is on.

Upgraded from an earlier version? Accounts set up before version 1.4 keep whatever they had, which means Remove only DonorPerfect flag tags is off unless you've asked us to turn it on. If you use ActiveCampaign tags for your own marketing, ask APIANT support to enable it.

What each combination does

All three on — the standard setup. DonorPerfect flags are mirrored as tags, and clearing a flag clears its tag. This includes a tag with the same name as a DonorPerfect flag that reached ActiveCampaign some other way, for example through a contact import. Any tag that doesn't match a DonorPerfect flag, like the tags you use for your own marketing, is left alone. This is what most organisations want, and it's how new accounts are configured.

Remove only DonorPerfect flag tags off — a strict mirror. ActiveCampaign's tags match DonorPerfect exactly. Any tag on a contact without a matching DonorPerfect flag is removed on the next sync, including tags you or your ActiveCampaign automations added. Only choose this if DonorPerfect is the sole source of tags for these contacts.

Remove ActiveCampaign tags off. Tags are only ever added, never removed. Clearing a DonorPerfect flag leaves its tag in place until you remove it yourself.

Flag sync off. Tags are never read or written. Field sync continues normally.

The settings are changed on our side rather than in your ActiveCampaign account — contact APIANT support if you want a different combination.

Flag-only changes don't trigger a sync

Adding or removing a DonorPerfect flag on its own does not cause that donor to sync. The change is saved correctly in DonorPerfect, but the donor won't appear in the sync until something else on their record changes.

This is how DonorPerfect works, not something the integration can adjust. Flags are stored in a separate table from the donor record and are written by a different API call, and that call doesn't update the donor's "last modified" date. Our sync polls for donors whose last-modified date has changed, so a flag-only edit is invisible to it. The same is true of checkbox/multi-value fields and "Other Info" custom fields.

What to do: edit anything on the donor's main tab — adding a note or touching the Narrative is enough. That updates the last-modified date, and the next sync run (within 5 minutes) picks up the record and applies the current flag state correctly.

Forcing a sync for a group of donors

Sometimes you'll want to push a whole group of donors to ActiveCampaign at once, without editing each record by hand. For example:

  • After an event, your team adds a Volunteer flag to 40 donors. Flag-only changes don't sync on their own, so none of those tags appear in ActiveCampaign.
  • You've cleaned up flags across a campaign's donors and want ActiveCampaign brought fully up to date for just that group.

You can do this yourself in DonorPerfect with Global Update and the standard Tag Date field. Tag Date is on the donor's main record and is designed for temporarily marking a group of records. Setting it to a new date counts as a change to the donor, so every donor you update is picked up by the next sync and refreshed in ActiveCampaign, including all synced fields and flags.

Steps

  1. Back up DonorPerfect first. Global Update has no undo, and DonorPerfect recommends a backup before every Global Update.
  2. Go to Utilities → Global Update.
  3. Action: Update.
  4. Table to Update: Main/Bio.
  5. Field to Update: Tag Date.
  6. Value to Update to: today's date as MM/DD/YYYY, for example 09/28/2026. Leave Value Contains Field Names unticked.
  7. Set Selection Filter: choose the group of donors to refresh (see below).
  8. Run the update. DonorPerfect tells you how many records were updated. Check that the number matches the group you expected.

Within about 5 minutes the sync starts picking those donors up. A large group is worked through over several sync runs.

Always use a selection filter

The filter is what lets you push just one group of donors. Without a filter, Global Update changes every donor in your database, and the next syncs will then reprocess your whole donor base. A full database sync takes much longer, uses a lot of your sync activity, and is rarely needed.

Good filters to use:

  • Donors with a particular flag, for example everyone with the Volunteer flag
  • Donors linked to a campaign or solicitation code
  • A donor type, or donors added or changed in a recent import
  • Any saved DonorPerfect selection filter your team already uses

Keep full-database refreshes for occasional clean-ups, and run them outside office hours.

Good to know

  • Tag Date only accepts a date. Entering text such as "Update ActiveCampaign" gives an error in DonorPerfect.
  • It overwrites any existing Tag Date. If your team already uses Tag Date for its own selections, talk to APIANT support first and we'll suggest another field.
  • Running it twice on the same day? Use a different date the second time, for example tomorrow's. Setting the same value again isn't a change, so those donors won't be picked up.
  • Donors without an email address are skipped, the same as in the regular sync.
  • Custom fields, contact notes and Other Info can't be used for this. They're stored outside the donor's main record, which is what the sync watches.

Prefer us to handle it? If you need a batch of flag changes reflected in ActiveCampaign, or you're not sure which filter to use, contact APIANT support and we can run an on-demand sync for those donors.

Contact creation vs. tag application timing

Whenever this sync creates a new contact or updates an existing one, that step always completes first — tag application happens afterward, as a separate step, typically seconds apart, sometimes less.

The gotcha: automations that fire on contact creation or update

Any ActiveCampaign automation that triggers the moment a contact is created or updated (list-subscription, a "contact updated" trigger, etc.) evaluates at that exact moment — using whatever tags the contact has right then, not the tags this sync is about to add or remove.

Practical effect: if you're relying on a tag to control what an ActiveCampaign automation does — for example, keeping certain contacts out of a Welcome Series — that tag-based condition is not reliable against a trigger tied to this sync's own create/update step. The automation can evaluate before the tag lands, whether the contact is brand new or already existed.

The fix: build the delay into the ActiveCampaign automation

If you have (or want to build) an ActiveCampaign automation whose logic depends on a tag this sync applies, add a step that waits before it evaluates tags, rather than acting the instant a contact is created or updated:

  • Add a short delay/wait step (a few minutes is enough) at the start of the automation, before the condition that checks for the tag.
  • Or use ActiveCampaign's "wait until" condition (if available on your plan) to pause until the tag is present, instead of a fixed delay — this is more precise since it isn't a race against a clock.

ActiveCampaign's own support team can help build either of these into an existing automation if you're not sure how.

Summary

  • Donor sync runs every 5 minutes; gift sync (Gifts Pipeline add-on) runs every 15 minutes. No write-back to DonorPerfect.
  • ActiveCampaign requires an email per contact — no-email donors don't sync unless placeholder-email generation is enabled.
  • Three settings control flag-to-tag sync. New accounts get all three on, which leaves tags you manage in ActiveCampaign untouched as long as they don't share a name with a DonorPerfect flag. Accounts upgraded from before version 1.4 keep their previous setting.
  • A flag-only change in DonorPerfect won't trigger a sync — touch a field on the donor's main tab and the next run picks it up. To push a whole group of donors at once, use Global Update on Tag Date with a selection filter, or ask APIANT support to run an on-demand sync.
  • Contact match/creation or update always completes before tag application.
  • Any ActiveCampaign automation that fires on contact creation or update can act before that sync's tags land — build a delay or tag-recheck step into the ActiveCampaign automation itself to avoid this.

Seeing something that looks out of sync? Contact APIANT support at support@apiant.com.

Related docs

Last updated September 28, 2026