Start by creating a Feed or editing an existing feed. Click the
"Add New Feed" button to initiate Feed creation.
Feed Name
The feed name.
Consider incorporating the Gravity Forms form name.
Action
Create a New Contact is the only available action.
Contact Details
Use this section to describe what actions the Feed Add-On will
take when processing a form post that can create a new Infusionsoft
Contact.
Map Fields
Use this section to select which Infusionsoft CRM fields pair with
their respective Gravity Form fields. Fields are organized in two
groups: Standard and Dynamic.
Standard Fields
There four Standard Form fields: Company, Email,
First Name, Last Name. Change
the Select a Field value when you want to store a
Standard field.
Dynamic Fields
Fields in this list are any form fields whose name does not match
a Standard form field. For example, Account
Balance is a dynamic field because it is not a Standard form
field.
Important
Do not create an Infusionsoft Custom Contact field with
a name that matches a Standard field. You will not be able to
access one of the fields.
Click the + button to add a dynamic field.
Click the - button to remove a dynamic field.
Lead Source
Use this setting to assign a lead source to the Contact.
Employ one of the following:
Select a value from current lead sources
Select Add Custom Lead Source and enter the
appropriate value
Attachments
Use this setting to allow file uploads to the Contact's
file box. Attachments are limited in size to 10Mb
Unconditional API Goal
Use this optional setting to start the Contact in an
Infusionsoft campaign.
All contacts will enter this campaign. Use campaign
sequences to apply tags, create opportunities, assign ownership,
send emails. Connect the API Goal to one or more sequences to
create a decision diamond and conditionally start a sequence.
Create an Infusionsoft campaign in which the API Goal is
the left-most goal.
Copy the Goal Name to this setting from Infusionsoft. The
Goal Name is case-sensitive.
Email Opt In
Systasis strongly recommends you enable this setting.
Use this setting to mark the contact "Marketable".
A contact will not receive a confirmation email when this
setting is YES.
Consider employing an email confirmation sequence to send
such an email.
Avoid Duplicate Contacts
Systasis strongly recommends you enable this setting.
When YES, the addon will attempt to update an existing
contact after searching for that contact. If not found, the contact
will be added to Infusionsoft.
You can search for a contact using one of the following
lists. Remember to map any Standard Fields you select.
Email
Email, Name
Email, Name, Company
Affiliate Link Click Tracking
The Infusionsoft Feed Add-On supports affiliate link click
tracking using a custom field type.
The purpose of this field is to extract an Affiliate ID from
the URL, and send it to Infusionsoft via its affiliate link click
tracking service.
You will use this field as follows:
Add an Affiliate Id field to a Gravity Form.
This field type is specific to the Gravity Forms Infusionsoft
feed add-on.
Important
Add only one Affiliate Id field to a form.
Configure the resulting field to indicate the name of the
URL query variable.
Step One: Add an Affiliate field
Find the Affiliate ID field in the "Advanced Fields" section
Add the field to a form like any other field, usually at the
top of the form.
The Affiliate Id field will be a hidden field on your form.
Step Two: Configure an Affiliate field
The only configuration required for an Affiliate Id field is to
name the URL query parameter. The presence of this field triggers the
Infusionsoft Add-On to create a link tracking record for the
Affiliate ID in the newly created or updated Contact.
Open the field's configuration panel, then click the
"General" tab.
Change the Field Label value to "Affiliate Code" from
"Untitled".
Click the "Advanced" tab
Enter the name of the URL query parameter in the "Parameter
Name" setting.
Conditional API Goal Logic
This is an optional step.
You can configure the Feed Add-On to cause an Infusionsoft
Contact to achieve an API goal under certain conditions. In this
example, the goal is achieved only when the visitor enters an email
address.
Enable conditional API goal logic
Enter the API goal name
Select the Gravity Forms field, the condition kind, the
condition value
Add another row, or save the current settings
Combine Fields
This is an optional step.
The purpose of this feature is to help you avoid assigning
too many Infusionsoft custom fields when saving form entries from a
form that has many recordable fields.
You configure the Feed Add-On to set a selected
Infusionsoft Contact value to a comma-separated list. The list values
are obtained from Gravity Form's multivalued field types such as
checkbox, radio.
Use the list values as input to various Infusionsoft
decision diamond rules based on the "contains value" rule.
The decision diamond rule will search the Contact field for
a match to the appropriate checkbox value and branch to the assigned
sequence when found.
Feed Conditional Logic
This is an optional step.
You can cause the Feed Add-On to create an Infusionsoft
Contact under certain conditions. For example, Contact creation
occurs only when the visitor enters an email address.
Enable conditional feed logic.
Select the Gravity Forms field, the condition kind, the
condition value.
Add another row, or save the current settings.
Update The Feed
Click the Update Settings button to save your work.
Clear Field Cache
Due to Infusionsoft API usage limits, Gravity Forms stores
Infusionsoft custom fields data for twelve hours. If you make a
change to your custom fields, you might not see it reflected
immediately due to this data caching.
Employ the following procedure to clear this cache.
Infusionsoft custom fields will be available when you edit a feed.
Navigate to Gravity Forms Settings > Systasis Gravity Forms
Feed Add-On.
Click the "Clear Custom Fields Cache" button
Gravity Forms => Infusionsoft data type map
These are suggested GF types.
The GF Single Line Text data type will map to any Infusionsoft
data type.
Infusionsoft data types that **do not** define value choices
will reject a bad value when that value is out of range. For example,
Infusionsoft will not store a Single Line Text with the value
"32-Jan-2018" as a Date data type.
Infusionsoft data types that define value choices will accept
any value even when that value is not in the choice list.