Understanding notification frequency
How quickly notifications appear in MoveData depends on how your integration sends data. Different platforms use different ingestion methods, and each method has its own timing characteristics.
How notification timing works#
MoveData receives data through four ingestion methods. The method your integration uses determines how quickly notifications appear after an event occurs on the platform.
| Ingestion method | Timing | Example platforms |
|---|---|---|
| Webhooks | Seconds (real-time) | Raisely, GiveEasy, Grassrootz, GiveWP |
| Polling | Minutes to hours (configured by MoveData) | Enthuse, Funraisin, JustGiving, TapRaise |
| Batch push | Minutes to hours (configured by platform) | GoFundraise |
| File upload | On demand (manual) | Benevity, CAF, Charitable Giving, Charities Trust, Facebook, Good2Give, Much Loved, PayPal Giving Fund |
Real-time integrations (webhooks)#
Webhook-based integrations push data to MoveData the moment an event happens. When someone makes a donation on a webhook platform, MoveData typically receives the notification within seconds.
If your platform releases a bulk volume of webhook events at once (for example, after a batch update or platform recovery), MoveData places them onto a processing queue and iterates through them in order.
You do not need to configure any timing for webhook integrations. The platform sends data automatically whenever a relevant event occurs.
Success
If you expect a webhook notification but do not see it, check the platform's webhook configuration to make sure it is still active and pointing to the correct MoveData endpoint.
Polling integrations#
Polling integrations work differently — MoveData checks the platform for new data at regular intervals. MoveData determines the polling schedule for each integration according to best-practice design, coordinated with the source platform. The polling interval is not always user-configurable — it is set to balance data freshness with API usage limits for each platform.
Check the integration article for your specific platform in this knowledge base to understand its polling schedule. For more detail on how to monitor polling, see Viewing polling attempts.
Viewing polling activity#
Each polling attempt creates a notification with Type = Job. You can use this to verify that polling is running as expected. For a detailed guide on filtering and interpreting these records, see Viewing polling attempts.
- Open the Notifications tab in the MoveData app.
- Filter the list by Type = Job and your integration name.
- Check the timestamps to confirm that polls are running at the expected interval.
Note
A Job notification with Success status means MoveData successfully checked for new data. It does not necessarily mean new data was found — it confirms the poll ran without errors.
File-based integrations#
Some integrations use file uploads rather than automated connections. With these integrations, notifications appear only after you upload a file.
You control the timing entirely by choosing when to upload. Organisations typically upload files on a schedule that matches their reporting cycle (weekly, fortnightly, or monthly).
Processing queue and delays#
After MoveData receives data through any method, notifications enter a processing queue. During busy periods, you may notice a brief delay between a notification appearing and its status changing from Processing/Queued to a final status.
This is normal behaviour. The queue ensures that notifications are processed in order.
Why you might see duplicate or delayed notifications#
There are a few reasons you might see unexpected notification behaviour:
- Duplicate notifications — some platforms send the same event more than once, or send multiple similar notifications at the same time. MoveData detects these duplicates and skips the repeated notification, resulting in a Skipped status.
- Intentionally skipped notifications — MoveData may skip notifications if their contents are not relevant to the Salesforce integration. This is expected behaviour and results in a Skipped status.
- Delayed notifications — a webhook platform experiencing downtime may send a batch of notifications when it recovers. These appear with the same created timestamp from MoveData's perspective but may relate to events that happened earlier.
- Out-of-order processing — during high-volume periods, notifications may finish processing in a different order than they arrived. Check the created date and time on each notification for the true arrival sequence.