Why is the Company Name variable in my Sequence incorrect?

In certain circumstances, when a contact is emailed using the company name variable, a mismatch may occur between the contact's email domain or company and the company name variable utilized in the sequence. This often happens when duplicate accounts exist in a user's CRM, including instances where multiple domains direct or redirect to different companies. Such inconsistencies typically arise due to data inaccuracies within the CRM.

How multiple records are deduplicated within Unify:

For matching and deduplication, Unify uses different criteria depending on the record type:

Contacts: Matches are determined based on email address. If there are multiple contacts that match, only the contact that was most recently modified within the CRM will be updated.

Accounts: Matches are determined based on the domain of the company website. Domains are normalized so URLs that redirect to different domains will not result in duplicates. If there are multiple matching accounts, Unify prioritizes the account with more associated contacts, or if that's equal, the account that was most recently modified.

Leads: Matches are determined based on email address. If there are multiple matching leads, the lead that was most recently modified will be updated.

How does this impact company name variables in Sequences?

When you have multiple duplicate accounts in your CRM that redirect to different websites, Unify consolidates these based on domain redirects. The company name variable in sequences will come from the CRM account record that Unify selects as the "primary" record.

How Unify Handles This:

• Domain Consolidation: Unify automatically consolidates company records based on domain redirects. For example, if multiple domains redirect to the same destination (e.g., subsidiary.com redirects to parent.com), Unify treats them as the same company.

• Record Selection Priority: When multiple accounts match the same company, Unify selects which account to use based on the following criteria:

• The account with more associated contacts is prioritized.

• If there is a tie, the most recently modified account is selected.

• Email Service Provider Domain Handling: Be aware that domains from email service providers (like Gmail, Outlook, or educational institutions) may sometimes redirect to major providers like Google or Microsoft. In rare cases, this can cause incorrect company associations. Unify has implemented safeguards to prevent existing company record names from being overwritten during sync operations.

Why You're Seeing Wrong Company Names: This issue occurs because, even though Unify correctly identifies all your duplicate accounts as representing the same company (via domain redirects), it might select an account record with an outdated or incorrect company name in your CRM. For instance, if an old subsidiary record has been modified more recently than the parent company record, the outdated subsidiary name might be used in sequences.

Additionally, if your CRM contains derived company records created from contact email domains (such as educational or organizational email addresses), these domains might redirect to major email service providers, potentially causing temporary misassociations. Another common cause occurs when you have multiple CRM integrations connected to Unify. Even if a CRM integration is paused or disconnected, historical data from that CRM remains in Unify. If that historical data contains outdated company names, Unify may prioritize it over your active CRM's current data, resulting in incorrect company names appearing in sequences. However, Unify now prevents existing company names from being changed during sync operations to avoid this issue.

The Solution: To resolve this issue, note that you cannot directly edit company names in Unify itself, as you need to clean up company names in your CRM records rather than in Unify, as Unify relies on your CRM data as its source of truth. If you have multiple CRM integrations and suspect data conflicts, check whether Unify is pulling from a stale or disconnected CRM. You can resolve this by removing historical data from unused CRMs in Unify, which will force Unify to use only your active CRM as the data source. This will not affect any running plays or sequences, and you can always reconnect the CRM later if needed. Note that Unify will only update company names for records it creates, not existing records, which helps prevent accidental overwrites of established company data.

Verify Domain Field Mappings as a Prerequisite Step: Before troubleshooting company name mismatches or applying other fixes, first ensure that Unify is receiving accurate domain data from your CRM. Check that your CRM's website/domain field contains the correct value and that Unify's field mapping points to this field (not a different custom field). You can verify field mappings in Unify under Integrations > [Your CRM] > Field Mappings. If the mapping is incorrect or the domain field is empty in your CRM, update it and trigger a resync. CRM records typically sync to Unify every 15 minutes, after which Unify should correctly link accounts based on the updated domain data.

Missing Company Name Variables

When Company Name Variables Go Missing: Duplicate or linked company records and domain‑based matching can prevent Unify from populating the company name variable entirely, leaving it blank even though a company record exists in your CRM. This results in blocked sequence enrollments with missing variable errors.

Solutions for Missing Company Name Variables: Use snippets with fallback text in your sequence templates instead of direct company name variables, and handle already blocked enrollments by either manually editing each blocked enrollment or bulk unenrolling contacts, fixing data, and re‑enrolling them.

• Use snippets with static fallback text (cannot use other variables) to ensure enrollments continue even when the company name is missing.

• Manually edit each blocked enrollment to replace the missing value, or bulk unenroll affected contacts, fix the underlying CRM data, and re‑enroll them.

Troubleshooting Company Name Variables with Real-World Examples

Understanding Domain Redirects Through Acquisitions

Company acquisitions often create domain redirect scenarios that can cause confusion with company name variables. When a subsidiary is acquired and its domain redirects to the parent company's domain, Unify consolidates these as one company but may select the subsidiary's name if that account has more associated contacts.

Real-world example

If Lacework is acquired by Fortinet and lacework.com redirects to fortinet.com, Unify will consolidate these as one company. If the Lacework account in your CRM has more associated contacts than the Fortinet account, Unify will select “Lacework” as the company name even for contacts with @fortinet.com email addresses.

Practical Troubleshooting Steps

Check for Domain Redirects: To verify if domain redirects are causing company name mismatches, navigate to the company level in Unify, click into the “Linked Records” tab, and hover over the information icon next to the domain to see if redirects are present. This will show you exactly which domains Unify has consolidated and help you understand why a particular company name was selected.

Acquisition-Related Issues: This commonly occurs when companies are acquired—for example, if subsidiary.com is acquired and its domain redirects to parent.com, Unify will treat contacts from both domains as belonging to the same company. The key is understanding that Unify's selection is based on contact count and modification date, not the “correct” or most current company name.

CRM Duplicate Detection Rules Blocking Account Creation

When Salesforce duplicate rules prevent syncing: If you're seeing "Failed dependency" errors on Tasks, Contacts, or other records, the root cause may be that Unify is attempting to create a new Account record, but Salesforce's duplicate detection rules are blocking the creation. This prevents the Account from syncing, which then causes all associated records (contacts, tasks, emails) to fail with dependency errors.

How to Identify This Issue:

1. Open the error detail drawer in the CRM Error Page

2. Follow the link to the parent Company/Account record

3. Check if the error indicates a duplicate detection rule match (exact name match or fuzzy name match)

4. Look for cascading errors on related records (contacts, tasks, emails) that all stem from the same blocked Account

Resolution Steps:

1. Identify and merge the duplicate accounts in Salesforce so there's one clear match

2. Ensure the surviving Account has a populated website/domain field for proper matching

3. Retry the Company/Account record write first in the CRM Error Page

4. Once the parent Account syncs successfully, retry the dependent record writes (tasks, contacts, emails)

5. Allow up to 15 minutes for the write cycle to complete

Note: This issue is distinct from Unify's internal deduplication logic. Even if you run regular deduplication in your CRM, Salesforce's duplicate detection rules (especially fuzzy matching rules) may catch edge cases that your deduplication process misses.