What This Does
VipeCloud's lead parsing system automatically converts inbound lead emails into contact records. When a lead email arrives in your connected inbox, the system checks it against a set of rules - if it matches a known lead source, it creates or updates the contact and populates the configured fields.
This article documents every supported lead source, the exact logic the system uses to identify each one, and what a correctly formatted lead email looks like.
If a lead is not parsing, find the lead source below and compare the trigger logic to your actual incoming email. This is the fastest way to self-diagnose a parsing issue before contacting support.
π§ This article is a work in progress. New lead sources are added on an ongoing basis. If your lead source is not listed here, it does not necessarily mean it is unsupported - see our full list in your account here, or contact support with a sample lead email and we can confirm or set up a new rule.
Franchise Direct
Franchise Direct
Note: With Franchise Direct leads, you need to be careful about correctly selecting the parsing rule because they have two different lead formats that they send commonly. Check both our "Franchise Direct" format as well as our "Franchise Direct (Alt Format)" and make sure you choose the one that matches the leads you are receiving.
Rules:
Subject includes
"Franchise Direct Lead"
Subject does not include
"Canopy"
Body does not include
"lead_source="
Franchise Direct (Alt Format)
Franchise Direct (Alt Format)
Note: With Franchise Direct leads, you need to be careful about correctly selecting the parsing rule because they have two different lead formats that they send commonly. Check both our "Franchise Direct" format as well as our "Franchise Direct Canopy" format and make sure you choose the one that matches the leads you are receiving.
Subject includes
"Franchise Direct Lead"
Body includes
"lead_source="
Franchise Hive
Franchise Hive
Rules:
Subject includes
"New Lead received from Franchise Hive"
Franchise.com
Franchise.com
Rules:
Subject includes
"New lead from Franchise.com Network"
FranchiseClique
FranchiseClique
Rules:
Subject includes
"FranchiseClique.com Presents This Franchise Lead"
Great Franchise Leads
Great Franchise Leads
Subject includes
"You Have Another Great Franchise Lead"
Growth Elevation
Growth Elevation
Body includes
"From: lead@growthelevationgroup.com"
LinkedFranchiseLeads
LinkedFranchiseLeads
Note:
The leads that were previously being parsed under the name of LinkedFranchiseLeads are now being parsed by the rule titled "LinkedVAnow".
Strategic Leads
Strategic Leads
Rules:
Subject includes
") Strategic Leads"
Example Lead:
VeteransFranchise
VeteransFranchise
Rules:
Subject includes
"VeteransFranchise.com Presents This Franchise Lead"
Example Lead:
Troubleshooting - Lead Not Parsing
If a lead arrived but did not create a contact record, work through the following before contacting support.
Confirm that a contact wasn't created. Automations>Email Parsing is where you'll find an audit log of your parsing activity. Scroll to the bottom of that screen for a list of Created Contacts where you can search for contacts. When checking this, click "Show updated contacts (audit)" to show parsing activity that didn't create a new contact because it was already existing.
Verify the email was sent to your connected inbox The lead must arrive directly at your VipeCloud parsing inbox.
Check the rule logic for that source Find the lead source in this article. Compare the rule logic exactly to the subject line or body of the incoming email.
The lead source may have changed their format. Compare the lead in your inbox with the sample lead in this article. If it looks different, forward it to support@vipecloud.com and we'll make any needed updates.
If the source is not in this article, contact support with a sample lead email. Include the full email - subject line, sender address, and body.
What to Send Support
Lead source name
Full sample lead email (subject line, sender address, and body). Forward the complete email from your inbox - no .eml attachments.
Expected behavior - did it parse partially, not at all, or to the wrong contact?





























