zintara.io

Lead management · Practical guide

Missing custom field in a campaign: trace import to preview

Trace the field through four places: source column, import mapping, saved contact and template token. A value visible in the CSV is not proof the campaign can render it.

Reviewed · Examples are illustrative

Who this helps: Operators preparing contact data, exclusions and campaign audiences.

Define the decision

Custom-field problems often come from naming rather than transport. A file may call a column Website URL while the template uses website, or a record may contain an empty string after mapping. Work with one affected contact so the evidence stays specific instead of changing every token at once.

Work through the procedure

  1. Open the original row and identify the intended value. Confirm it belongs to the correct contact, not a neighboring row.
  2. Inspect the import mapping and resulting key on the saved lead. Record exact spelling and casing.
  3. Compare the token with that key. Check whether its name collides with a standard variable that takes precedence.
  4. Correct the data or supported token, preview the affected contact and review other records using the same field before activation.

Worked example

The following is a synthetic example for this procedure, not a customer result or performance benchmark.

CSV column: research_topic
Saved custom key: research_topic
Campaign token: {{researchTopic}}
Mismatch: underscore key versus camelCase token
Fix: align with the saved supported key, then preview populated and empty records

Read the result

The example is a key mismatch, so SMTP changes would not help. Another case might show the correct key but an empty saved value, pointing back to mapping or source quality. Following the chain prevents a successful fix for one contact from hiding missing data across the rest of the audience.

Check before moving on

  1. Search subject lines as well as bodies for the incorrect token.
  2. Inspect a second contact to distinguish a systemic mapping issue from one incomplete row.
  3. Review markup-like characters in the rendered preview rather than assuming every custom value is plain prose.

Limits and next action

Do not populate missing research with invented claims to make a preview look complete. Zintara replaces known exact tokens and merges custom fields after standard values. Use neutral wording or hold the affected record when essential context is unavailable.

Source: Zintara product and contact workflow context

Source references

Worked examples are illustrative. Editorial procedures are suggested methods, not measured performance claims or promises of additional product features.

Related guides

Explore the Zintara workflow