Integrations

Partner data validation pilot

Upload partner prospect files to validate addresses against your fiber availability API and confirm which records match your serviceable footprint.

Overview

**Partner data validation** lets you upload a CSV file of prospect addresses from a partner vendor, then automatically verify each address against your Fiber Homes availability API. The system checks whether each claimed-available address truly matches your serviceable footprint, identifies conflicts where partner data differs from your provider lookup, and flags invalid or unconfirmed records before you deploy reps to the field.

Each validation run processes up to thousands of addresses in the background, returning results that show confirmed matches, conflicts, unconfirmed addresses, and errors. You can review results by outcome, export the full report as CSV, and optionally approve confirmed rows to import them as new prospects in your workspace.

How To

  1. **Navigate to Integrations** from the main menu, then select **Partner Data Validation**.
  1. **Click Start New Validation Run** and upload a CSV file containing partner prospect data. Your file must include columns for `sourceRecordId`, `street`, `city`, `state`, and `claimedAvailable` (true/false). Optional columns include `zipCode`, `partnerProvider`, `partnerTechnology`, `territoryName`, and `assignedRepName`.
  1. **Review the upload preview**, which shows total records, valid records, and any row-level errors (missing required fields, duplicate IDs, invalid state codes). Fix file errors before proceeding.
  1. **Click Confirm and Start Validation** to queue the run. The system processes records in batches and queries your Fiber Homes API for each address. Validation runs in the background and may take several minutes for large files.
  1. **Check run status** from the validation runs list. Each run shows the source file name, total records, completion progress, and final status (running, complete, or failed).
  1. **Open the results page** once the run completes. You'll see a summary table showing counts by outcome:
  • **CONFIRMED_MATCH** – Address verified and matches partner claim
  • **CONFLICT** – Address verified but partner availability claim differs from API result
  • **CONFIRMED_UNAVAILABLE** – Address verified but not serviceable
  • **UNCONFIRMED** – Address lookup returned no match or low confidence
  • **INVALID** – Address failed validation (bad format, missing data)
  • **ERROR** – API lookup failed
  1. **Filter results by outcome** to review specific rows. Click any row to see full address details, partner claim, API response, and validation notes.
  1. **Export results as CSV** by clicking **Download Full Report**. The export includes all original partner columns plus validation outcome, API provider, API technology, and match confidence.
  1. **Approve confirmed matches** (optional) by selecting rows with outcome `CONFIRMED_MATCH` and clicking **Import as Prospects**. This creates new prospect records in your workspace, pre-assigned to territories and reps if those columns were included in your upload.

Tips

  • Run validation before assigning territories to reps so you only deploy teams to verified addresses.
  • Use the conflict report to identify partner data quality issues and request corrections from your vendor.
  • Export unconfirmed rows and manually review addresses that didn't match the API—they may be new construction or require address normalization.
  • Schedule validation runs via the cron endpoint (`/api/cron/partner-data-validation`) to process large files overnight.

Questions

**Q: What happens if my API key isn't configured?** A: The validation run will fail with status `ERROR`. Configure your Fiber Homes API key in workspace settings under Integrations before starting a validation run.

**Q: Can I re-run validation for the same file?** A: Yes. Each upload creates a new validation run with a fresh batch of API lookups. Previous runs remain in your history for comparison.

**Q: How long does validation take?** A: Processing time depends on file size and API rate limits. Expect 1–2 seconds per address. Runs larger than 1,000 records may take 30+ minutes and should be scheduled via cron.

**Q: What if a row has errors in the preview?** A: Rows with errors (missing required fields, duplicate IDs, invalid state codes) are excluded from validation. Fix the file and re-upload to include those rows.

Need to see how KnockTracer fits your workflow?

Start with map-first sales tracking now, then layer in partner sync, install handoffs, and customer launch flows as your team grows.