Skip to main content
Before running a data import or syncing historical data through an integration, pause your triggered (auto-trigger) messages. Otherwise, imported records — like historical donations — can fire live messages such as your “Thank You” email, sending donors messages for transactions that happened in the past.

​
Option 1: Pause a single message

  1. Go to Marketing > Messages and open the message you want to pause (e.g., “Thank You”).
  2. Click Pause in the top-right corner of the message page.
The message status changes from Live to paused, and it will no longer send while your import runs.

​
Option 2: Pause all live messages at once

  1. Go to Marketing > Messages (All Messages).
  2. Filter by Status: Live.
  3. Select all messages using the checkbox in the header row.
  4. Click More > Pause (Draft).
All selected messages are paused in one action.

​
Optional: ask WeGive Support to disable engagement events for integration data

If your import comes through an integration (rather than a direct CSV upload), there’s also a backend setting that stops WeGive from creating engagement events for synced records at all — a stronger safeguard than pausing individual messages, since it suppresses the underlying trigger rather than just the message that would fire from it. This isn’t a self-service dashboard toggle. It’s configured by WeGive Support/Engineering on your organization’s record, not from Settings. If you’re about to run a large historical sync through an integration, contact WeGive Support ahead of time and ask them to turn on “Disable Engagement Events For Integrations” for your organization before you start, then turn it back off once the import finishes.

​
After your import: re-enable your messages

  1. Return to Marketing > Messages and filter by paused/draft status.
  2. Select the messages you paused.
  3. Click More > Set Live.
Your triggered messages will resume sending for new, real-time activity. Tip: Wait until the import has fully finished processing before setting messages live again, so late-processing records don’t trigger sends.