Using the Zapier Email Parser
Interested in using the Zapier Email Parser to connect your leads to your CRM? We'll walk you through the process of setting up the Zapier Parser.
Ensure you have a Zapier Lead Email set up on your account!
A Zapier parser email address looks something like this: [email protected]. After you generate a
mailbox in the Zapier email parser (https://parser.zapier.com) please send your Robot email address
to the MediaBrains customer support team so we can configure your lead alerts to be sent to the correct address. Additionally, we can send test
leads to your Zapier parser email address to ensure everything is working correctly.
Below is a sample of the Zapier Email Parser template that can be used to collect the fields for one of our leads.
You may notice the lead alert looks different than the lead alerts you receive in your inbox. Due to limitations with how Zapier parses emails, we have to use a different format for the lead alerts. The lead alerts you receive in your inbox are formatted to be easily read by the Zapier Email Parser - this includes outputting every possible field a lead from our system may have, even if the field does not have a value. The Zapier Email Parser will ignore fields that do not have a value, so you can use the same template for all of your leads.
Lead Data Dictionary
This data dictionary can be used to help understand the fields sent in the Zapier lead notification email. The field key is the key used to access the field in the sample Zapier template below.
| Lead Field | Description | |
|---|---|---|
| Person Info | Full Name | The full name of the person who submitted the lead. This is a combination of the first and last name fields. |
| First Name | The first name of the person who submitted the lead. | |
| Last Name | The last name of the person who submitted the lead. | |
| Email Address | The email address of the person who submitted the lead. | |
| Employment Info | Job Title | The job title of the person who submitted the lead. |
| Phone | The phone number of the person who submitted the lead. | |
| Company Info | Company Name | The company name where the person who submitted the lead is employed. |
| Company Industry | The industry for the company where the person who submitted the lead is employed. | |
| Company Size Range | The range of the number of employees for the company where the person who submitted the lead is employed. | |
| Company HQ Address | Address | The address (line 1) for the company's headquarters where the person who submitted the lead is employed. |
| Address Line 2 | The address (line 2) for the company's headquarters where the person who submitted the lead is employed. | |
| City | The city for the company's headquarters where the person who submitted the lead is employed. | |
| Region | The region (state) for the company's headquarters where the person who submitted the lead is employed. | |
| Postal Code | The postal code for the company's headquarters where the person who submitted the lead is employed. | |
| Country | The country for the company's headquarters where the person who submitted the lead is employed. | |
| Lead Order | The name of the lead order this lead is attached to. This field only applies to leads that are part of a pay-per-lead order. This could be used to route leads based on the lead order they are attached to. | |
| Lead Type |
This field represents the type of lead. Possible lead type values are:
"Request for quote",
"Request for information",
"Website click",
"Add to list",
"Content download".
|
|
| Lead Type Specific Fields | Lead Category | The category this lead originated from. This field is only present for leads that are part of a category. Some leads, such as leads that originated from your company profile, may not have a category. |
| Content Title | The content title of the content downloaded for a content download lead. This will be the piece of content that was downloaded by the person who created the lead. Applicable only to content download lead type. | |
| Product Name | The name of the product that is related to this lead. Products can be related to website click leads and request for information leads. If there is a product name attached, the lead is either a click on the product's website link, or a request for information about the product. | |
| List Name | The name of the user's list that your company was added to. The user was creating a shortlist of vendors on the directory site, and your company was added. This is the name of the list the user was adding your company to. Applicable only to add to list lead type. | |
| Click Location |
This is the location the click lead originated from. This could be: Category listing, Company profile, Product, or Banner Ad.
Applicable only to add to website click lead type.
|
|
| Subject | This is the user-entered subject on a lead where the user is requesting information or a quote from your company. Applicable only to request for information and request for quote lead types. | |
| Message | This is the user-entered message on a lead where the user is requesting information or a quote from your company. Applicable only to request for information and request for quote lead types. |
Sample Zapier Template
The following sample may be a useful representation of how we have seen a successful Zapier parser template configured. This template can be used to collect the fields for one of our leads, and handles multiple lead types very well.
The trick to getting the fields to stick is to "triple-click" your mouse to select the entire value (it will include the entire line) and enter the field name. After assigning output values to all lead fields - your template should look similar to the sample below, including having the "three dashes" delimiter right next to the end of each output field.