If you’re working with individuals instead of businesses in Salesforce, understanding person accounts is essential. But how do you actually use them with FormAssembly and avoid common pitfalls?
In this webinar recap, we break down how Person Accounts work, when to use them, and how to configure your FormAssembly Salesforce connector to support accurate, efficient data collection. Read on for an overview of the presentation, or watch the webinar on-demand here.
What Are Person Accounts in Salesforce?
Person Accounts are a hybrid record type in Salesforce that combine Accounts (typically used for businesses) and Contacts (used for individuals).
Instead of managing these separately, Person Accounts allow you to represent an individual as a single record, while Salesforce maintains both objects behind the scenes.
Why this matters:
- You get account-level functionality (ownership, reporting)
- You retain contact-level detail (individual data fields)
- You simplify the user experience with a single record view
This structure is especially useful for organizations working with:
- Donors or constituents
- Customers as individuals (not companies)
- Partners, contractors, or applicants
Why Use Person Accounts with FormAssembly?
When paired with FormAssembly, Person Accounts enable:
- Streamlined data collection for individuals
- More flexible Salesforce reporting
- Cleaner data models without duplicate records
- Improved user experience for internal teams
However, because of their hybrid structure, they require specific configuration in your Salesforce connector.
How to Create Person Accounts in FormAssembly
One key takeaway: If you’re using Person Accounts in your organization’s Salesforce setup, you don’t create a “Person Account” directly in FormAssembly. Instead, you:
- Create an Account record
- Assign the correct Record Type ID
This Record Type ID tells Salesforce: “This account should behave as a Person Account.”
Critical step: Record Type ID
Without a Record Type ID, Salesforce defaults to a Business Account. The Record Type ID controls:
- Page layout
- Field visibility
- Record behavior
Best practice: Save your Record Type ID so it’s easy to reuse across connectors.
How to Avoid Duplicate Records
To prevent duplicate Person Accounts, use a lookup step in your connector. Filter by:
- Record Type ID (required)
- A unique identifier (e.g., email)
This ensures that only Person Accounts are matched, business accounts are excluded, and data remains clean and consistent.
How to Work with Person Accounts in Campaigns
Some Salesforce objects – like Campaign Members – don’t connect directly to accounts. Luckily, there is a workaround.
Because Person Accounts have a contact behind the scenes, you can:
- Look up the Person Account (Account object)
- Retrieve the associated Contact ID
- Use that Contact ID to create the campaign member
This allows you to enroll individuals in campaigns, track engagement, and maintain proper relationships in Salesforce.
See for yourself: In this on-demand webinar recording, you’ll see how to find Record Type IDs and Contact IDs and use them to configure a Salesforce connector in FormAssembly.
Key Configuration Tips
1. Always Use Record Type IDs
This is the most common issue. If you don’t do this, records will default to Business Accounts and Person Account fields won’t appear.
2. Map Person-Specific Fields
Always map fields like First Name, Last Name, and Email. These come from the contact side and must be explicitly mapped.
3. Account for Validation Rules
Person Accounts are affected by validation rules on the Account object and the Contact object. Ensure your form mappings satisfy both.
4. Understand Connector Differences
- Workflow Connector: Can directly access related data (like Contact ID from Account lookup)
- Form Connector: Requires additional lookup steps
Choose your approach based on your use case.
Advanced Use Cases to Consider
Complex Relationships (Households, Groups)
You can connect multiple Person Accounts using:
- Party Relationship Groups
- Junction objects (similar to campaign members)
Repeatable Data Structures
When working with repeatable sections:
- Map one repeatable section per action
- Use dependencies to maintain relationships
- Carefully structure nested workflows
Testing Safely
Best practice:
- Use a Salesforce sandbox
- Clone forms for testing
- Validate before deploying to production
Common Questions About Person Accounts
Can you convert existing contacts in Salesforce into Person Accounts?
Not directly. This typically requires a data migration process and should involve a Salesforce admin.
Can you turn off Person Accounts later?
No. Enabling person accounts is a one-way change in Salesforce.
Do you need to rebuild FormAssembly forms if your data model changes?
Not necessarily. In most cases, you can:
- Clone existing forms
- Update mappings
- Reuse the structure and form logic with minimal changes
Key Takeaways
- Person Accounts combine accounts and contacts into a single, flexible record
- In FormAssembly, they are created by setting the correct Record Type ID
- Lookups should always include Record Type ID to avoid duplicates
- Some objects require accessing the underlying contact record
- Testing in a sandbox is recommended for safe implementation
Final Thoughts
Person Accounts unlock powerful ways to manage individual data in Salesforce, but only if they’re configured correctly.
With the right setup in FormAssembly, you can streamline data collection, improve accuracy, and build more flexible workflows that align with your Salesforce data model.
Interested in learning more? Schedule a personalized demo of FormAssembly – or request a free trial to explore on your own.
