Set up campaign fields
This article shows how to define campaign fields so every lead carries the data buyers need. Fields are the schema for the campaign. Missing or overly strict fields are one of the most common reasons day-one leads reject.
Set fields before you invite live traffic, and keep required fields as tight as the sale allows.
What are campaign fields?
Campaign fields define the data shape for leads in one campaign. Each field has a name, a type, and whether it is required. Suppliers must send values that match those definitions. Buyers and filters also read from the same field names.
Typical first fields include name, email, phone, zip, and state. Add vertical-specific fields only when buyers actually need them to accept.
| Setting | What it controls |
|---|---|
| Name | The exact key suppliers send for this value |
| Type | How the value is validated (string, email, phone, integer, date, and similar) |
| Required | Whether a missing or invalid value rejects the lead |
| Allowed values | Optional list for fields that must match a set (for example states) |
Prerequisites
- An existing campaign (see Create and configure a campaign)
- A short list of fields your buyers require to purchase
Set up fields
- Go to Campaigns and open the campaign.
- Open the Fields tab.
- Click Add (or the equivalent add-field control) for each field.
- Enter the field Name. Use a stable key you can share with suppliers, such as
emailorzip_code. - Choose the field Type that matches the data.
- Turn Required on only when you cannot sell the lead without that value.
- If the field should only accept certain values, add those allowed values.
- Click Save.
- Repeat until the schema covers your minimum sellable lead.
- Return to Overview and confirm setup health no longer complains about missing fields.
If your workspace supports CSV import for fields, you can bulk-add a known schema, then review required flags one by one.
Recommended day-one field set
| Field | Usually required? | Notes |
|---|---|---|
| Email or phone | Yes, at least one contact path | Match what buyers can actually contact |
| Name | Often yes | Split first and last only if buyers need the split |
| Zip or postal code | Often yes | Common for geo routing and filters |
| State or region | Sometimes | Useful for geo accept rules |
| Custom vertical fields | Only if buyers require them | Extra required fields create avoidable rejects |
Tips and gotchas
- Field names are contracts with suppliers. Renaming later forces everyone to update.
- Keep required fields tight. Optional fields can still be sent when available.
- Type mismatches reject even when the value "looks right" to a human. Match type to real data.
- If buyers need a value mapped into their own field names, handle that in buyer delivery mapping later. Do not invent duplicate campaign fields just to match each buyer's label.
- After you change required fields, re-test with a sample lead before live traffic.
Expected result
The Fields tab lists every value the campaign accepts, required flags match what you can sell without, and a test lead with complete data can pass field validation.
Frequently asked questions
What happens if a required field is missing? The lead is rejected during validation before a normal sale path. The lead timeline and rejection views help you confirm the cause.
Can I add fields after go-live? Yes, but coordinate with suppliers. New required fields will reject incomplete posts immediately.
Should every buyer-specific preference become a campaign field? No. Campaign fields are the shared schema. Buyer-specific accept rules belong in buyer filters or buyer delivery settings.
Do field names have to match the buyer's API names? Not necessarily. Campaign fields are your internal schema. Buyer delivery configuration can map values into what each buyer expects.
How do fields relate to filters? Filters evaluate campaign fields (and some enriched values). Build fields first, then add filters that reference those field names.
Can I make a field required for one supplier only? Required on the Fields tab is campaign-wide. Use supplier-level filters or supplier defaults when you need source-specific behavior.
Related articles
Comments
No comments yet — be the first to share your thoughts.