All guides

Capture & deduplication

Deduplicate multi-page prospect tables

Capture page one, move manually to page two, and inspect the added and duplicate counts before moving on.

Start with a small representative sample

An SDR sees promoted rows repeated at the top of three source pages. The goal is one list of unique contacts after manually reviewing each page.

Choose a source page you are authorized to use. Make a named list for the job so you can compare new rows with earlier entries from the same source. Include a typical row, a row with a missing or ambiguous value, and a row with formatting that tends to break the next step. A sample can be just a few rows as long as it gives you a way to verify the process before using a whole campaign.

Build a three-page experiment with one promoted duplicate and two rows exclusive to each new page. Capture each view into the same list.

Check the source before export

Start in the ordinary page or view containing the records and choose an appropriately named list. Click the toolbar capture button and inspect the added count. For a multi-page job, move to the next page yourself, wait for it to render, and capture into the same list. Compare the first few added records with the visible source. If the page is a virtualized grid, work from the segments you can actually see after changing the view.

Different people can share a name and company. Look at visible profile URLs and review common-name collisions before exporting.

Write down the number of source records you expect to review. If only part of a source table renders at once, make sure your count describes the portion you actually captured. The evidence can be simple: a distinct first row, a last visible row, and a field you can find again later. On a repeated run, these reference points help explain the difference between a bad mapping and a changed source page.

Work through an example

The table shows what a useful before-and-after check looks like for Profile URL. Use it as a model for your own field map. Inspect the visible input first. Look at the output in its intended form, then consider what an operator would do if the source value turned out to be unavailable or different. When the field has more than one legitimate interpretation, include a second example with a different expected result.

FieldVisible exampleExpected result
Profile URLhttps://www.example.com/people/sarah?utm_source=list#detailsexample.com/people/sarah

Capture page one, move manually to page two, and inspect the added and duplicate counts before moving on.

Check the duplicate total and manually compare the profile identities on the first and third pages. Pause if one page was still loading when clicked.

Capture a known repeated contact from two pages and confirm only one appears in the campaign. Then add a contact whose role is similar but profile link and name are different. Verify the new record remains in the list.

Review the cases that can slip through

Creating a new list per page prevents deduplication from running across the whole campaign.

Expect new rows and duplicates to vary when the source changes its ordering during the day. Avoid interpreting a duplicate count as proof the current page was processed without errors. Use at least one known overlap as a comparison point and check a few rows unique to the second page.

Check the sample after filtering and editing. Search should return both the ordinary case you expect and the exception you selected deliberately. If the exception is hard to find, add a review note or place it in a separate list. Keep an original source reference where it is useful. The goal of this pass is a repeatable decision about those few ambiguous rows before the selection takes on a life of its own.

Prepare the destination

Open the Workbench in its own tab and inspect raw source columns as well as derived ones. Use the search box to find representative names, employers, or terms. Update a cell if the visible source supports the change. A skipped duplicate may be an expected overlap from two pages, or an ambiguous match you need to look at. Keep the context of a match available before relying on the final total as a measure of what was captured.

Keep the manually observed page counts, final row count, and any decisions about deliberate duplicates with the campaign.

Label the first output a trial and record the list name, selection, target format, and the field that determines whether the row can be used. Compare at least one expected blank and an ordinary populated row after export. Keep test changes easy to roll back. For larger jobs, measure the number of rows that need manual handling so you know where the remaining review will take time.

Validate what the recipient will use

Compare the final presentation to the human decision that uses it. A CSV is suited to an editable follow-up, TSV works for a quick paste, a PDF supports reading in a meeting, and a ZIP keeps campaigns apart. Capture and export are separate decisions, especially when a list contains contact details that only one reviewer needs. If the downstream task needs just a narrow set of rows, apply a filter in the Workbench before the CSV, TSV, or PDF step.

Write down whether a source filter or sort changed between captures. When it did, separate intentional overlaps from missed rows in your final review.

Document the first and last row you remember on each source page. This lightweight record helps when a site inserts promoted entries or resorts results after the second capture. It gives you evidence about the views you actually reviewed when row totals do not add up.

Review one result where the converted value looked straightforward and one where your team had to choose between plausible interpretations. Give the recipient the updated row count and a practical next action. If review exposed a source inconsistency, note the observable issue and include enough context for the recipient to reproduce it. Close the loop by storing or removing the trial material according to how long your team needs it.

Record the minimum needed for a repeat run

Save a simple checklist with your source path, list name, review filter, format, and destination fields. Keep the choices about Profile URL near the top so the next operator can pick a meaningful test row. A useful recurring process records the fields that affected the outcome and the points where someone needed judgment. It can be rerun when the source layout changes without forcing every old decision into a script.

LeadSheet Clean keeps captured rows and derived values in the browser. Start with Standard Clean CSV or copy TSV when you need a quick review sample. Lifetime Pro adds unlimited export rows, specialized presets, PDF briefs, and multi-list ZIPs. Select the path that produces the format and selection required for your handoff, and verify the license or Free allowance before repeating a large export.