Skip to content

Skip trace a list

The Properties page, where you select properties to skip trace.

Skip tracing looks up owner contact information for a property-oriented list. Goliath offers it from Properties and from Upload data in Library. A skip-trace run produces a downloadable result; it does not create contacts when you choose Skip Trace & Export in an upload.

Skip tracing can use organization credits. Review the number of rows and the credit prompt before you confirm a run.

  1. Open Library → Uploads and select Upload data.
  2. Choose your source and upload or connect the property list.
  3. At What do you want to do with it?, select Skip Trace & Export.
  4. Review the preview, including the addresses Goliath will use.
  5. Confirm any credit step and complete the review.
  6. Find the result in Library → Downloads when it is ready.

The review step is important. A property source with incomplete or malformed addresses may produce fewer useful matches than the row count suggests.

From Properties, select the rows to work with and use the bulk Skip trace action. That starts the property-oriented export flow for the current selection. Use Skip trace & contacts only when you intend for the outcome to create contacts as part of that flow.

Automatically re-skiptrace when new information is available is off unless you tick it, in that flow and on a workflow’s Skip Trace and Add Contact step. With it on, when a probate lead’s executor is named after the first trace, Goliath skip traces the executor too, for 1 credit each, and your Dashboard says how many it re-skiptraced and found. With it off, the Dashboard suggests those re-skiptraces for you to approve. Both Dashboard notes are ideas, so neither shows while that idea is turned off or muted.

Open the result in Library → Downloads to see its rows, then download it in one of the formats offered. If you need contacts, use an import or property workflow that explicitly creates contacts instead of assuming every skip-trace export changes the contact database.

  • Check that the selected records are the intended properties.
  • Review address quality and remove obvious duplicate or test rows.
  • Estimate whether the result is useful enough to justify the run.
  • Read the credit confirmation; do not treat a preview as a no-cost lookup.