How Do I Bulk Skip Trace from a File?

About

Bulk skip trace lets you enrich hundreds or thousands of property records with contact information in a single operation. This is essential when you’re importing a new lead list, uploading a purchased property file, or enriching a filtered segment of your portfolio. Goliath offers three common paths: enable skip trace during CSV upload so every row is traced as it’s imported, select properties from your list and trace the selection via the Actions menu, or navigate to the Skip Trace Requests page and launch a run against an existing tag or list. Each successfully traced record consumes one skip trace credit, and Goliath shows the total cost before charging so you can review large batches carefully.

Step-by-Step Guide

1. Choose your bulk skip trace method

   Decide which path fits your workflow. If you’re uploading a fresh CSV or Excel file of properties, you can enable skip trace during the import wizard—Goliath will trace every row as it ingests the file. If your properties are already in Goliath, you can filter the Properties list to your target segment, select the rows you want to enrich, and choose Skip Trace / Enrich from the Actions menu. Alternatively, navigate to the Skip Trace Requests page at /data/skiptrace-requests and kick off a run against a saved tag or list.

2. Enable skip trace during upload (Method 1)

   When you upload a CSV or Excel file via the import wizard, look for the skip trace option in the wizard settings. Toggle it on to trace every row during ingest. Goliath will display a cost estimate based on the number of rows in your file. Review the estimate carefully, confirm the charge, and proceed with the upload. The import and skip trace run in tandem, and you’ll be notified when both complete.

3. Select and trace from the Properties list (Method 2)

   Apply filters to narrow down the properties you want to trace—for example, properties with no contact information or a specific tag. Use the checkbox column to select individual rows, or click the selection menu above the list and choose Select All to include every property that matches your current filters. If you want to limit the batch size, choose Select first N from the menu and enter a number—this is useful for controlling cost predictably (e.g., “trace the first 500 that match my filter”). Once your selection is ready, open the Actions dropdown and click Skip Trace / Enrich.

4. Review the cost confirmation

   Goliath displays a confirmation dialog showing the total number of records you’ve selected and the total credit cost. Large batches can consume many credits, so review this carefully before confirming. Each successfully traced record consumes one credit; records that do not match contact data typically do not incur a charge. Click Confirm to start the skip trace request.

5. Monitor progress on the Skip Trace Requests page

   Navigate to the Skip Trace Requests page to track your bulk run. Each request shows a status—Pending, Running, Completed, or Failed—along with counts of records traced and matched. You can navigate away from this page; Goliath will notify you when the run completes. If you need to stop a run mid-flight, use the cancel control next to the request.

6. Review results and enriched records

   Once the run completes, Goliath appends contact information to your property records the same way single-property skip trace works. Phone numbers and email addresses are attached to the property record, and contact records are created or updated for each matched owner. Tags you applied to the original properties carry over to the new contacts. Check the request detail on the Skip Trace Requests page for per-row results and any errors.

Pro Tips

• Use the Select first N option when working with large filtered sets to bound your batch size and control costs predictably
• Failed rows do not block the entire batch—Goliath continues processing and reports per-row results so you can review what didn’t match
• Bulk skip trace runs scale well: thousands of records typically complete in minutes, not hours

Frequently Asked Questions

Q: How long does a bulk skip trace run take?

Run time scales with the size of your batch. Hundreds of records complete in under a minute, and even batches of several thousand records typically finish within a few minutes.

Q: What happens to records that do not match contact data?

Records that do not match are reported in the results, and you typically are not charged a credit for un-matched records. The Skip Trace Requests page shows counts of both traced and matched records so you can see what succeeded.

Q: Do failed rows block the entire batch?

No. Goliath processes each row independently, so a single failed or un-matched record does not stop the rest of the batch. The request detail shows per-row results and any errors.

Q: Can I cancel a skip trace run mid-flight?

Yes. The Skip Trace Requests page includes a cancel control next to each running request. Canceling stops the run and prevents additional credits from being consumed.