All guides

Capture & deduplication

Package multiple lead campaigns into a ZIP

Open the ZIP and check each nonempty list has one file with its intended preset and row count.

Start with a small representative sample

An agency account owner has one list per approved campaign and wants to archive CSVs together without combining customer or campaign rows.

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.

Before creating the ZIP, review the list sidebar and archive scope. Remove stale or unintended lists from the workflow through your normal review process.

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.

Two campaign titles can sanitize to a similar filename. A numbered prefix keeps archive entries distinct.

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 Campaign file. 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
Campaign fileQ4 / regional partnersA separate numbered, filesystem-safe campaign CSV

Open the ZIP and check each nonempty list has one file with its intended preset and row count.

Check the numbered filenames after downloading. Report any campaign where the initial CSV underspecifies the recipient's necessary source columns.

Make a test archive containing two lists with similar names and one empty list. Verify that the two files have distinct names and that there is no empty campaign file to confuse the recipient.

Review the cases that can slip through

Exporting a single merged sheet mixes account boundaries and makes it harder to find or remove a specific batch.

Before packaging, verify the selected preset applies to all of the included campaigns. If your team needs different columns for different destinations, package only after individually preparing those files in their intended formats. Treat a campaign archive as wide in scope even when its individual CSVs are small.

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.

Share the ZIP only with recipients authorized for every included list. Export one list at a time for narrower access.

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.

Use a destination that respects the scope of every packaged list. If ownership differs across campaigns, send reviewed files separately through approved channels.

Open one file from the beginning and one from the end of the archive and compare their presets. Check any sensitive contact fields before sharing. A package that covers an agency’s entire workspace requires broader authorization than a new vendor shortlist alone.

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 Campaign file 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.