Computed Fields: Transform Your Data Before It Reaches Buyers

Computed fields let you create dynamic fields whose values are derived from the lead data you already collect. With a few clicks you can reformat, merge, or enrich information so every buyer receives data exactly how they expect it.

What Computed Fields Are And Why They Matter

• Virtual fields, real flexibility. Define a new field once and reuse it across buyers within the same campaign without touching source integrations.
• Buyer-friendly formatting. Match field names, formats, and accepted values that individual buyers demand.
• No-code transformations. Combine fields, run transformers, and preview results directly in the UI - no syntax memorized, fewer mistakes.

Step-By-Step: Enabling, Configuring, And Reusing Computed Fields

1. Open the Computed Field Configurator. From any of your buyers configuration page, campaign triggers modals or the API filters modal, click on the icon to launch the configurator to see existing computed fields and quick-start instructions. This icon can be found at the top of the payload builder box, as shown bellow.

   

   
   
2. Add a new computed field. Click + Add computed field    , give it a descriptive name (e.g., phone_only_digits   , full_name    ). We recommend to use lowercase letters, numbers, and underscores only.
3. Build the output.
   1. Mix text and fields: static text, system fields, and campaign fields can be used to create the output value you need. In the box at the top of the screen, you can type any text, or use the +     button to insert an existing field.
   2. Apply transformers: by clicking on the blue field name or the orange  icon, a new configuration opens that allows you to transform the output value further. Transformers are a powerful way to create many different variations of your data, and can be used to convert almost any input data to any output.
4. Preview the result. click Test Output to test your new field. A box will open that shows an example input and output so you know exactly what buyers will get before saving. You can adjust the input and test as many times to ensure the output matches your desired format.
5. Save & publish. Once satisfied, save the computed field. It becomes available anywhere you map or reference fields in LeadProsper.

You can create as many computed fields as needed for each of your campaign. Please note, at this time, computed fields are defined at the campaign level.

You can also use the same campaign field or system field in multiple computed fields. For example, you might need to convert lp_lead_date   into multiple formats.

A field can have multiple transformers. They are daisy chained, and the order is very important, as you will see in the examples bellow.

Practical Examples You Can Recreate Today

Full Name

Goal: send full lead name. Receive first and last name as separate fields.

How:

Result:

Phone Normalization

Goal: send the phone number in the US common format. Many other formats can be chosen from.

Examples:

• 6503277650 ➔ (650) 327-7650
• (650) 327-7650 ➔ 6503277650
• 6503277650 ➔ 650-327-7650

How:

Result:

Date Format Switch

Goal: Convert supplier-provided YYYY-MM-DD   DOB (or any date) values into the MM/DD/YYYY   format a buyer requires.

Example: 1990-10-01 ➔ 10/01/1990

How:

Result:

TrustedForm Certificate ID

Goal: Extract TrustedForm ID from a TrustedForm Certificate URL

Example: https://cert.trustedform.com/aa08b22a0b1f1ae230bb6f6f4b9e82bf82011fbc ➔ aa08b22a0b1f1ae230bb6f6f4b9e82bf82011fbc

How:

Result:

Number to text conversion

Goal: Convert a number into a text.

Example: A credit score (number) to a credit rating (text). 810 ➔ Excellent, 700 ➔ average

How:

Result:

Simple text conversion

Goal: Convert a value to another value.

Examples: Commonly used to convert Yes to 1 and No to 0 or reword similar options that are collected in different ways. A good example would be a buyer requiring Roof Shade, but the data received is collected as Sun Exposure.

• A lot of sun ➔ No Shade
• No sun ➔ A lot of Shade

How:

Result:

Merging multiple fields and converting to one output text

Goal: Convert a value composed of multiple fields into one single value.

Example: Most common in home services, where project type must be combined with another field to provide one mapping.

How:

Result:

Advanced date to text conversion

Goal: Convert a date to a text representation of a range.

Example: You might collect a date of accident, but the buyer wants a timeframe as text. This is achieved by taking the input date, calculating the days different between today and the given date and using if_else_between   transformer to output a text based on defined ranges.

How:

Result:

Advanced text to date conversion

Goal: Convert specific text to a date.  

Example: Commonly used to convert timeframes  to actual dates.

• Less than 1 month ago ➔ 30 days ago ➔ 2025-09-01
• 1-3 months ago ➔ 3 months ago ➔ 2025-07-01

How:

This is used by using the if_else   transformer to convert the text to a relative date (in the past or future)

Result: