Overview
Partner feeds bring in prospect records, serviceability data, and install handoff statuses from external systems. Before sending reps into territories, you need to confirm that data is flowing correctly and that sync runs are completing without errors.
The **Integrations** screen shows feed health at a glance: when the last sync ran, how many records were processed, and whether any alerts need attention. A healthy feed means reps see accurate provider data, up-to-date install statuses, and reliable prospect lists when they're knocking doors.
If a sync fails or stalls, reps may work from stale data—leading to duplicate touches, missed callbacks, or confusion about which addresses are already spoken for. Regular sync checks catch these issues before they impact the field.
How To
- **Open the Integrations screen.**
Navigate to **Integrations** from the main menu. You'll see a table listing each active partner feed.
- **Check the last sync timestamp.**
Each feed row displays when the most recent sync ran. If the timestamp is older than expected (for example, more than 24 hours when daily syncs are configured), investigate or trigger a manual sync.
- **Review record counts and status badges.**
Look for the number of inbound records processed and any status indicators like "Healthy," "Warning," or "Error." A green "Healthy" badge means the feed is current and error-free.
- **Scan for alerts or error messages.**
If a feed shows a warning or error badge, click into the detail view to see what went wrong—common issues include authentication failures, schema mismatches, or network timeouts.
- **Trigger a manual sync if needed.**
Use the **Run Sync Check** or **Sync Now** button to force an immediate refresh. Wait for the sync to complete, then verify the timestamp and record count update.
- **Confirm handoff statuses are current.**
If your workflow includes outbound install handoffs, check that completed installs are flowing back into KnockTracer so reps don't revisit closed accounts.
Tips
- **Set up daily sync schedules** aligned with your partner's data refresh cadence—morning syncs ensure reps start each day with fresh records.
- **Enable sync notifications** so managers receive alerts when a feed fails or falls behind schedule.
- **Cross-reference the map view** after a sync to spot missing or duplicate addresses that might indicate a feed issue.
- **Document partner API credentials** in a secure vault so you can quickly troubleshoot authentication errors without waiting on external teams.
Questions
**Q: How often should partner feeds sync?** A: Most teams run nightly syncs to keep prospect data current without overwhelming the system. High-velocity teams may sync every few hours, while low-volume feeds can run weekly.
**Q: What should I do if a feed shows an error but I can't resolve it immediately?** A: Pause the feed to prevent bad data from reaching reps, notify your partner contact, and use the last known-good sync until the issue is fixed. Update the team so they know which data may be stale.