Creating and Managing Tables

Feature Snapshot

Summary:
Tables let you store reference data in LeadConduit and use it in your flows. You upload a CSV, choose the key column (or columns) that identify each row, and choose the columns to return. Flows can then match incoming leads against the table to enrich them with extra data or set their purchase price. You don’t need a separate rule for every value.

Key Benefits:

• Replaces hundreds or thousands of flow rules with one table
• Change your data by uploading a new CSV, with no flow edits
• One table can be used by several flows
• Built into LeadConduit, so you don’t need an external database or service
• See at a glance which flows use a table and when it was last queried

Typical Use Cases:

• Pricing leads by postal code, state or other attributes (e.g. a different price for each of 40,000 postal codes)
• Routing leads by territory (postal code → buyer or office)
• Adding campaign data from a tracking phone number
• Mapping codes to descriptions (state → region, sub ID → landing page)

How It Works

You manage tables under Assets → Tables. Each table comes from a CSV file and has three parts:

• Rows and columns. These come from your CSV. The first row holds the column headers.
• Key column(s). LeadConduit uses these to find the right row for a lead. In a flow, you map a lead field to each key column, for example Postal Code → zip_code. If you use more than one key column, the lead must match all of them.
• Data to return. These are the columns whose values come back when a row matches. By default, every column is returned.

Example

This CSV uses zip_code and product as key columns and returns region and price:

zip_code,product,region,price
78701,auto,Central,12.50
78701,home,Central,9.00
10001,auto,Northeast,18.00
94105,auto,West,15.75

A lead with Postal Code 78701 and product home matches the second row, so the table returns region = Central and price = 9.00. A lead with Postal Code 10001 and product home matches no row, because both keys must match.

Matching rules

• Matching is exact and case-sensitive. For example, TX does not match tx.
• Spaces at the start and end of a value are ignored.
• Each key value appears only once in a table. If your CSV repeats a key, the first row is kept and the rest are skipped.

Where tables are used

• Lookup using Table step: adds the returned columns to the lead as fields such as lookup_table.query.price. Later steps, like filters, deliveries and pricing, can use these fields. See Enriching Leads with the Lookup using Table Step.
• Lead purchase price → Table: sets the price a source is paid from a price column in the table. This works on standard submissions and on Real-Time Bidding pings and posts. See Setting the Lead Purchase Price from a Table.

When you update a table, every flow that uses it picks up the new data. You don’t need to change the flows.

Step-by-Step Instructions

Prepare your CSV

Before you upload, check your file:

• The first row holds the column headers, and each header is different.
• The file is saved as CSV and is 26 MB or smaller.
• Every row has a value in each key column.
• Key values are stored exactly as your source sends them, including letter case and leading zeros (e.g. 02134, not 2134).

Create a table

1. In the left menu, select Assets, then Tables.
   Expected Result: The Tables page lists your tables with their Rows, Columns, Last queried, Last updated and Flow usage.

2. Select Create Table.
3. Enter a Table name. This field is required.
4. Optionally, enter a Description.
5. Under Upload data, drag your CSV onto the upload area, or select Choose File.
Expected Result: A file chip shows the file name, size and number of rows.

6. Under Key column, choose the column used to find the right row. The first column is selected by default.

   • To match on more than one column, select Add Key and choose the next column.
   • To remove a key column, select its trash icon.

7. Under Data to return, choose which columns are added to the lead when a row matches:

   • Leave return all columns to matched leads on to return every column.
   • Turn it off to choose specific columns.

8. Check the Table Preview on the right. Each column header is labeled Key or Return. Confirm the labels are on the columns you expect.

9. Select Create Table.
   Expected Result: A message confirms the table was created and reports the rows added and any duplicate rows skipped, for example: Table “My Test Table” created — 1 row added, 13 duplicate rows skipped. The table’s detail page opens.

Tip: Key columns can’t be changed after the table is created. Decide on your key columns before you upload.

Review a table

On the Tables page, select a table name to open its detail page. It shows:

Rename a table or edit its description

1. Open the table.
2. Select the pencil icon next to the name.
3. Edit the name or description, then save.

Update a table

1. Open the table and select Update Table.
2. Drag your CSV onto the upload area, or select Choose File. The file must include the same key column(s) and return columns as the table.
3. Choose how to apply the file:
   • Leave Replace all table entries with new upload cleared to add new rows and update existing ones. Rows that aren’t in the new file stay in the table.
   • Select Replace all table entries with new upload to replace the whole table. Rows that aren’t in the new file are removed.
4. Select Update.
   Expected Result: A message reports the result, and Last updated changes. Flows that use the table pick up the new data. You don’t need to change them.

Download a table

1. Open the table.
2. Select the ⋯ menu next to Update Table, then select Download CSV.
   Expected Result: The table’s data downloads as a CSV file.

Delete a table

1. Open the table, or find it on the Tables page.
2. Select the ⋯ menu, then select Delete, and confirm.

A table that a flow uses can’t be deleted. Remove it from each flow listed under Flows first: remove the Lookup using Table step, or change the source’s Lead purchase price to another option. Then delete the table.

Deleting a table is permanent. Download it first if you want to keep a copy.

Validation & Monitoring

• Check the upload result: After you create or update a table, read the counts in the confirmation message. If fewer rows were added than you expected, check the file for repeated or empty key values.
• Check the row count: The Rows value on the detail page shows how many rows the table holds.
• Check the preview: Confirm the Key and Return labels in the Table Preview are on the right columns.
• Check usage: Last queried shows the last time a flow used the table, and Flows (or Flow usage on the Tables page) shows which flows use it. If Last queried stays empty after leads arrive, check the flow’s setup.

Best Practices

• Decide on your key columns before you create the table. They can’t be changed later.
• Store key values in the same format your source sends them, including letter case and leading zeros.
• Format key columns as text in your spreadsheet before you export, so values like 02134 keep their leading zero.
• Keep one row per key value. If a key repeats, only the first row is kept.
• For prices, store plain numbers only (12.34, not $12.34 or 1,250).
• Give tables clear names and descriptions, so others know what each one holds and where it’s used.
• Download a copy of the table before you replace all of its entries or delete it.

Frequently Asked Questions (FAQ)

What file format and size are supported?

CSV files up to 26 MB. The first row must hold the column headers.

What happens if my file has the same key more than once?

The first row with that key is kept and the rest are skipped. The confirmation message tells you how many duplicate rows were skipped.

Can I change the key columns after I create a table?

No. To use different key columns, create a new table.

Is matching case-sensitive?

Yes. TX doesn’t match tx. Spaces at the start and end of a value are ignored.

Do I need to edit my flows after I update a table?

No. Every flow that uses the table picks up the new data.

What’s the difference between updating and replacing a table?

By default, an update adds new rows and updates existing ones, and keeps rows that aren’t in the new file. With Replace all table entries with new upload selected, rows that aren’t in the new file are removed.

Can more than one flow use the same table?

Yes. The Flows list on the detail page shows every flow that uses it.

Why can’t I delete a table?

A flow is still using it. Remove the table from each flow listed under Flows, then delete it.

My table has three key columns. Can a flow match on only two of them?

No. Every key column needs a lead field mapped to it, and the lead must match all of them. If a key column is left unmapped, the lookup can’t return a result. To match on fewer columns, download the table (⋯ → Download CSV) and create a new table that uses only the key columns you want. Make sure each combination of those keys is unique, because only the first row for each key is kept.

Glossary

Related Articles

• Enriching Leads with the Lookup using Table Step
• Setting the Lead Purchase Price from a Table
• Pricing
• Real-Time Bidding

• tables-list-page.jpeg100 KB
• tables-create-new-table.jpeg100 KB
• tables-detail-page.jpeg100 KB
• tables-update-modal.png80 KB
• tables-delete-modal.png20 KB