Skip to main content

Understanding Input-Mapping — Lookup 🔍, Name Accuracy 🧩, & Content Input ✍️

Learn why Autobound creates these columns automatically, and how you can use them to increase maximum accuracy and personalization.

Daniel Wiener avatar
Written by Daniel Wiener
Updated over a week ago

Why are these columns automatically created and mapped?

When creating a new campaign, Autobound auto-creates various fields in your campaign to make setup easier & guarantee content personalization & insight generation work immediately.

You can always hide or remove columns as needed, but at least one Lookup field must remain mapped, or Autobound won't know who you're targeting.

Quick Overview of Icons

  • 🔍 Lookup
    ​Required. Identifies exactly who the contact and sender are, enabling Autobound to generate content and insights accurately.
    ​

  • 🧩 Name Accuracy
    ​Optional. Lets you override Autobound's automatic naming to ensure contacts and companies appear exactly as you want in messages.
    ​

  • ✍️ Content Input
    ​Optional. Allows you to steer how the AI writes by adding extra context, specifying value props, setting tone preferences, or changing the writing style.

Deep Dive into Each Input-Mapping Category

🔍 Lookup Inputs (required for resolution)

What columns fall under Lookup?

  • contactEmail, contactLinkedinUrl, contactCompanyUrl

  • userEmail, userLinkedinUrl, userCompanyUrl

Why are they required?


Lookup fields ensure Autobound knows precisely who your message is being sent to and who it's from. Without at least one contact lookup field (contactEmail, contactLinkedinUrl, or contactCompanyUrl), the AI won’t know which contact to resolve, and the content generation will fail with a clear error message.

How does Autobound use Lookup fields?

  1. Matches your provided email, LinkedIn URL, or company URL against Autobound's database.

  2. Finds accurate contact details and company context.

  3. Pulls personalized insights specific to that individual and organization.

How to debug common Lookup issues:

  • Double-check that at least one Lookup field is mapped and filled out per row.

  • Ensure you haven't accidentally deleted or hidden a Lookup field needed for resolution.

  • If your content is not pulling from your custom Content Hub data, verify your sender email's domain matches your Autobound account domain, or explicitly map userCompanyUrl.

🧩 Name Accuracy Inputs (optional overrides)

What columns fall under Name Accuracy?

  • contactName, contactCompanyName

  • userName, userCompanyName

When should you use Name Accuracy fields?

  • To fix name formatting: "Jon" vs. "Jonathan".

  • To enforce exact company names: "ACME Inc." vs. "Acme".

How does Autobound use Name Accuracy fields?


These fields override Autobound’s default resolved name only in final messages, ensuring your communication always appears exactly as intended. Importantly, these overrides do not influence insight lookup or contact matching.

How to debug common Name Accuracy issues:

  • If contact or company names are appearing incorrectly, first confirm you provided a value in the Name Accuracy fields.

  • If placeholders like "[First Name]" appear, ensure that your Lookup fields contain valid identifiers. Without successful contact resolution, Autobound has no default name to use or override.

✍️ Content Input Parameters (optional personalization)

What columns fall under Content Input?

  • additionalContext, valueProposition, salesAsset

  • writingStyle, language, model

When should you use Content Input fields?
Use these fields whenever you want to guide or explicitly instruct how Autobound's AI writes content, overriding its default behavior. Examples:

  • Prompting specific mentions ("we met for coffee last week").

  • Ensuring Autobound includes a certain asset or value prop.

  • Adjusting tone, language, or model for testing variations.

How Autobound prioritizes Content Input:

  • Highest: Explicit row-level values you provide.

  • Mid-level: Campaign-level settings (in your "Content & Insight Input Settings").

  • Default fallback: Content Hub persona-based defaults.

How to debug common Content Input issues:

  • Confirm your mapped Content Input column is filled in with a value. Blank cells cause Autobound to revert to lower-level defaults.

  • Ensure that if you've hidden a Content Input column, it is still mapped properly. Hidden columns still apply their data to the engine—they simply don't appear visually in your campaign table.

FAQs & Edge Cases

Q: What if I map multiple Lookup fields (e.g., contactEmail + contactLinkedinUrl)?
​A: Autobound cross-references these inputs. If both match, lookup confidence is boosted. If there's a conflict, resolution confidence decreases, potentially causing content generation or insight retrieval to skip the contact.
​

Q: Can I delete contactEmail and rely solely on LinkedIn URLs?
​A: Yes—Autobound can fully resolve using LinkedIn URLs alone, provided that column stays mapped and populated.

Q: Why isn't Autobound using my Content Hub data even though userEmail is set?
​A: If the sender email’s domain differs from your Autobound account, Autobound uses global data instead. Provide userCompanyUrl explicitly to ensure your own Content Hub data applies.

Still need help?

  • Input Mapping Panel: Navigate to your campaign's Settings → Input Mapping.

  • Questions or stuck? Reach out via Intercom. Please include a clear screenshot showing your mapped columns, visible values, and any error messages you're encountering.

Did this answer your question?