FAQ & Known Limitations

Frequently Asked Questions

Why is the initial sync taking so long?

This is expected. Bloomerang's API is limited to 20 records per request, so large datasets require many individual API calls. The initial sync can take 60 minutes or longer depending on your data volume. Subsequent syncs only process recent changes and are much faster.

Can I sync some data types but not others?

Yes. Each data type (supporters, transactions, funds) has independent push and pull toggles. You can enable or disable sync for each type and direction separately in your integration settings.

What happens if I disconnect and reconnect the integration?

Disconnecting stops all sync activity. When you reconnect, you'll need to re-enter your API key and Default Fund ID. Previously synced records retain their linked IDs, so the integration should pick up without creating duplicates.

Do I need to use a specific Bloomerang API version?

Yes. The integration requires Bloomerang API v2.0. Make sure you generate your key from the API Keys v2.0 section in Bloomerang Settings, not an older version.

Can I use my WeGive test account with my Bloomerang production instance?

No. Environment matching is strictly enforced. Test WeGive accounts can only connect to Bloomerang Sandbox instances. Production WeGive accounts can only connect to Bloomerang production instances.

How do I know which environment I'm in?

Check the top right corner of your WeGive dashboard. Test accounts are marked with "[TEST]" in the account name.

Known Limitations

Bloomerang API is limited to 20 records per request. This makes initial syncs and full re-syncs slow for large datasets. There is no workaround for this limit.

Environment matching is strictly enforced. Test WeGive accounts only connect to Bloomerang Sandbox, and production accounts only connect to production Bloomerang. No cross-environment syncing is possible.

Default Fund ID is required. Bloomerang requires all transactions to have a Fund ID. If the Default Fund ID is missing or incorrect in your integration settings, all transaction syncs will fail.

Only three data types sync. The integration currently syncs supporters/constituents, transactions, and funds. Other data types (campaigns, custom fields, communications, etc.) do not sync between the two systems.