DonorPerfect Tag Sync

Write the tags on a BetterUnite contact into a DonorPerfect checkbox field, so the segments you build here are available there too.

Set it up

In DonorPerfect, decide which checkbox field your tags belong in. Donor Interests, field name DONINTS, is the usual choice, but any checkbox field works.
In that field's code list, under Settings, Code Maintenance, add a code for each BetterUnite tag you want to carry across.
In BetterUnite, open Sync Options on the DonorPerfect setup page, switch on Send contact tags, type the DonorPerfect field name into Checkbox field tags are written into, and click Save Options.

The field name is the short name DonorPerfect uses internally, as it appears in their Screen Designer, not the label on screen. It is up to 20 characters.

When tags are written

Tags are written whenever a contact is matched to a DonorPerfect constituent during a sync, which in practice means the first time each contact comes up in a run. They are not a separate job and there is no tags tab: turn the option on, and the next donation or pledge sync carries the tags across with the donors it touches.

A contact who has never given, and so has never been synced, has no constituent for tags to be written onto.

How tags are matched to codes

Each BetterUnite tag is matched against the codes on that field, first on the description, which is what a person sees in both systems, and then on the code itself for organizations that have named them the same.

A tag with no matching code is skipped, not created. DonorPerfect will not invent a code, so a tag it does not recognize is passed over quietly and the rest of the tags still go across. If a tag never seems to arrive, add it to that field's code list in Code Maintenance.

Removing a tag

Each sync sets the constituent's checkboxes to exactly the list of tags the contact currently has. Remove a tag in BetterUnite and the matching box is unchecked on the next sync. Clear all of a contact's tags and all the boxes on that field are cleared.

BetterUnite owns that field once you turn this on. Anything a staff member ticks on that field in DonorPerfect is replaced the next time that contact syncs. Point the integration at a field kept for this purpose rather than at one your team edits by hand.

Why a checkbox field and not Flags

DonorPerfect Flags look like the natural home for tags and are not. Setting a flag that is already set fails outright, and the only way to remove one flag is to delete every flag the constituent has. A checkbox field can be set to exactly the list we send, in one call, which is what keeping two systems in step actually requires.