Tags & custom fields

Every captured lead is stamped with information your automations can act on. There are two kinds: tags (every widget) and custom fields (calculators only).

Tags

Tags are the main automation hook. Every captured lead gets a layered set:

1. conversion-toolkit — on every lead from this app, always.
2. A widget-type tag — calculator-lead, wizard-lead, or spinner-lead, so you can tell where a lead came from.
3. Your “Extra tags” — whatever you type in the widget’s Lead capture section (e.g. summer-sale, homepage). These are the ones you’ll usually trigger on.
4. Result tags — added once the outcome is known:
   • Calculators add calculator-result.
   • Spin-to-win adds spinner-win.
   • Quizzes add per-answer tags you define (the powerful one — see Bucketing & segmentation).

Tip

Set Extra tags to something specific per campaign — q1-roi-calc, bf-spinner — so a platform workflow can target exactly that widget’s leads.

Custom fields (calculators)

Calculators can save their results onto the contact as custom fields — not just in the note. Turn on Save results to CRM custom fields in the calculator’s Lead capture section.

How it works:

• The instant you save the widget, Conversion Toolkit creates one contact custom field per result (and reuses a matching field if it already exists, so saving repeatedly never makes duplicates).
• Fields are named with a CT · prefix so they’re easy to find in the platform, e.g. CT · Loan amount.
• When a lead is captured, each result is written into its field.

Examples of fields created:

Calculator template	Custom fields created
Mortgage payment	CT · Total monthly (PITI), CT · Principal & interest, CT · Loan amount, CT · Total interest over life, CT · Down payment %
Solar savings	CT · 25-year estimated savings, CT · Break-even point, CT · Net cost after 30% tax credit, CT · Recommended system size
Home affordability	CT · Max home price (est.), CT · Max loan amount, CT · Est. total monthly housing, CT · Back-end DTI used

Two things to know

• Values are saved as text exactly as shown (e.g. $2,134). That’s perfect for showing the number in an email, but the platform’s “greater than / less than” filters won’t reliably compare them as numbers.
• Don’t rename a CT · field in the platform. The app matches fields by name, so a rename makes the next save create a new one. Style/segment around them instead.

The safety net: the note

Even if custom fields are off (or the location hasn’t granted that permission), the result/answers are always written to a contact note. You never lose the data — see Permissions & data.

What this app does not do

To set expectations honestly:

• Only calculators write custom fields. Quizzes and spin-to-win write tags + a note.
• Only email, name, and phone are captured as contact fields — nothing else.
• There’s no automatic “range” tagging (e.g. “tag high-value if payment > $2,000”). For value-based routing, see the guidance in Bucketing & segmentation.