Standard Contact Fields

In your Outbound Automation system, you have the ability to input the following standard fields for every lead or contact that enters your system:

First Name, Last Name, Email, Phone, Address, City, State, Zip, Sub ID, Pub ID, Source

For dynamic lists or static lists pulled from your boberdoo system, these fields will automatically populate based on the fields in your lead type.

oa fields and magic strings

For static lists uploaded via CSV, you can map any fields in your list file to any of these field options.

oa fields and magic strings

Custom Contact Fields

If you would like to insert contacts into your Outbound Automation system that include fields other than those listed above, you will need to build and map custom fields.

In order to do this, you need to configure the webhook that passes leads from your boberdoo leadsystem into your Outbound Automation system. Access your boberdoo leadsystem and click Settings>Webhook/Notifications. Locate the ‘New lead – matched’ and ‘New lead – no matches’ webhook. Locate the ‘cstmLeadToMarketingMangerGernric’ Function and click the ‘Edit notification’ tool.

oa fields and magic strings

Locate the ‘Function’ dropdown option and select the ‘LeadToMarketingMangerCustomFieldsGeneric – Forward lead refund to Marketing Manager with Custom Fields’ option. This will clear your existing Arguments and display five new custom field boxes.

oa fields and magic strings

Next, fill in each field with the lead type field you would like included with each contact that is added into Outbound Automation from your boberdoo leadsystem.

Option 1: You can use the Magic Strings tool to pull a magic string from the Available Magic Strings list.

Option 2: To use a separate field from your lead type, you need to manually enter the magic string. See the exact formatting structure below.

Example 1
– Lead Type Field Name: Project
– Magic String: {LEAD_FIELD_PROJECT}

Example 2
– Lead Type Field Name: Estimates Completed

Note: This webhook is not mapped to a specific lead type. Because of that, we can only insert data into fields that match your custom fields exactly. The example above includes common home improvement fields. However, if an auto insurance lead entered your system that did not contain the ‘Project’ field, this contact’s custom field would remain empty.

Magic Strings Options

Outbound Automation stores specific field values for your company, the contacts as well as the matching partner (assuming the contact was imported as a matched lead from the leadsystem). See the list of available magic strings below.

Your Company Magic Strings


Contact Magic Strings


Partner Magic Strings


Note: For the partner magic strings, you must include {@PARTNERS} at the beginning of your partner strings and {/PARTNERS} at the end.


Using Magic Strings

All of the magic strings listed above can be used in two different ways.

1. Auto-Populate Email Creatives

When building Subject Lines and Email Bodies, you have the option to utilize any of the magic strings listed above. Simply use the bracketed strings and the your system will automatically populate the corresponding value when the email is sent.

oa fields and magic strings

The company information magic strings are also added to the bottom of each of our email templates, but can be manually removed from each email. These magic string values are pulled from the Company Information section of the Setup page.

2. Pre-Populate Landing Page Forms

You can also use magic strings to pre-populate any form that is directly linked to from the email. This is especially effective for any campaign that is encouraging an additional lead submission. Pre-populating forms with all of the information you have available can considerably improve conversion rates. When building your email body, use the Link tool to assign a URL to any linked text or image. Next, enter your landing page URL with the appropriate field mapping attached. See image below.

oa fields and magic strings

In this example, the form we are directing the lead to records the First Name field as “First_Name”. Because of this, we have mapped the First Name field on the form to our {CONTACT_FIRST_NAME} field. If your form records First Name as f_name, this link would look like this:{CONTACT_FIRST_NAME} If you are using a boberdoo Form, you can view your form field structure by going to Settings>Lead Types.