The Personify integration for landing pages adds new prospects to your Personify AMS/CRM with a minimum of barriers. When recipients submit a Marketing Automation landing page, Communications Enterprise can make their information available in your Personify instance.

NOTE: This integration solution is not intended to handle subscription management or conduct surveys.

Installing Universal Services

Landing page integration is based on the universal services integration that is already used outside of Marketing Automation. So, when Marketing Automation is enabled for your account, you won't need to install anything else to start integrating landing pages to Personify.

When you are ready to install, create a case and request assistance from our Support team.

The installation process includes:

1. Running a script to create the necessary stored procedures for your Personify database.
2. Running the main installation package.

Installation will set up the default options as described below. If you would like to customize any part of the integration (such as the stored procedures), you can do so.

NOTE: Communications Enterprise is unable to maintain any customization you add.

How the Integration Works

To use the integration, you will need the Personify integration and Marketing Automation activated for your account. For assistance, create a case for our Support team.

Creating Integrated Campaigns

After this is done, a new Integration section will be available when you create a landing page campaign. Check the Integrate with Personify checkbox to create new records in Personify.

NOTE: This checkbox is optional for each landing page campaign, meaning you can choose to have some campaigns integrated, while others are not.

Creating New Records

Communications Enterprise creates records directly in the Personify database using a SQL insertion. By default, records are created under a Real Magnet constituent class. This class is created as part of the installation process.

Using the Real Magnet constituent class allows you to easily find records created by Communications Enterprise. On your CRM360 search page in Personify, there is a constituent class menu. After the integration is installed, you can choose Real Magnet as one of the options from this menu.

Record Creation Logic

When the campaign is deployed, records are added to Personify through the following workflow:

1. Recipient submits the landing page.
2. Communications Enterprise checks to see if the submitting user's email address is tied to an existing record Communications Enterprise.

If the email address is not found, Communications Enterprise creates a contact record. Then...

1. Communications Enterprise searches the Personify database to see if the email exists.

1. If no record of the email exists, Communications Enterprise creates a new one. Communications Enterprise then takes the Personify ID and stores it in the Custom ID field.
2. If one record of the email exists, Communications Enterprise stores the Personify ID in the Custom ID field.
3. If more than one record of the email exists, Communications Enterprise stores the Personify ID for the first record returned.

If the email address is found, Communications Enterprise checks the Custom ID field. Then...

1. If the Custom ID field is blank, Communications Enterprise searches the Personify database to see if the email exists.

NOTE: This process also happens if the field contains a dummy ID. Dummy IDs are created when your Communications Enterprise account requires a Custom ID to create contact records, but none is submitted through the landing page. Dummy IDs have a set format which Communications Enterprise recognizes.

1. If no record of the email exists, Communications Enterprise creates a new one. Communications Enterprise then takes the Personify ID and stores it in the Custom ID field.
2. If one record of the email exists, Communications Enterprise stores the Personify ID in the Custom ID field.
3. If more than one record of the email exists, Communications Enterprise stores the Personify ID for the first record returned.

2. If the Custom ID field is not blank, Communications Enterprise does not update the Personify database.

1. The fact that the recipient submitted a landing page can be seen in Personify through the embedded Communications Enterprise report.

Communications Enterprise and Personify Field Mappings

The following Communications Enterprise fields are available to map to Personify fields:

• Email (required)
• First Name
• Last Name
• Company
• Address 1
• Address 2
• City
• State
• Zip
• Phone Number
• Fax

No additional fields can be added. You can set default values for these fields by modifying the stored procedure which creates Personify records.

NOTE: Make sure to include required fields on your Communications Enterprise landing page.