NOTE: This article references "Real Magnet" -- a previous name of the Higher Logic Communications Enterprise product.

The Communications Enterprise Personify integration connects your Personify database directly to Communications Enterprise using Communications Enterprise’s Universal Web Service. It is compatible across all browsers, and can be used in conjunction with Communications Enterprise. The integration is compatible with Personify versions 7.3 or higher.

NOTE: The integration is compatible with Personify versions 7.3 or higher; this guide is applicable to Personify 7.3 and higher, and only for V2 of the Communications Enterprise integration.

Watch the video

Who should read this guide?

This guide is for Communications Enterprise users responsible for determining messaging and contact management guidelines. It assumes that you are familiar with:

• Using the Communications Enterprise system
• Managing users in Personify
• Managing data within Personify

Failure Notifications

Whenever there is a failure for the integration, an individual can opt-in to receive a daily notification.

To modify this setting:

1. Log in to Communications Enterprise.
2. Select Settings.
3. Select Integrations.
4. Select Integration Settings.
5. Under Failure Report, ensure that Enabled is set to YES.
6. Enter a Run Time.
7. Enter the email address(es) (comma separated format).
8. Click Save.

User-Access Requirements

A Communications Enterprise account administrator can designate what users in the account have permission to access the integration. Below you will find tables detailing what each permission level means and what a user can do with that permission.

To assign a permission:

1. Select Settings.
2. Select Permissions.
3. Select Integration Access Levels.

Communications Enterprise User Permissions

Scheduled Upload

Permission Level	View	Run	Create/Schedule	Edit	Delete
Full Access	Y	Y	Y	Y	Y
Read Only	Y	Y	N	N	N
No Access	N	N	N	N	N

Tracking

Permission Level	View	Edit
Full Access	Y	Y
Read Only	Y	N
No Access	N	N

Unsubscribe Mapping

Permission Level	View	Create	Edit	Delete
Full Access	Y	Y	Y	Y
Read Only	Y	N	N	N
No Access	N	N	N	N

Configuring Tracking Information in Communications Enterprise

As a default, no tracking information is selected to push over to the production environment. In order to select what tracking information is pushed to Personify, and when, an administrator must log in to Communications Enterprise.

Communications Enterprise recommends that full access over manage tracking be a permission granted only to other administrators. Once tracking information has been selected, Communications Enterprise will only sync records with Personify from that point onward. It is for this reason that access to this panel should remain limited.

NOTE: This page also provides detailed error descriptions in the event any records have not synced the night before.

To enable tracking, log in to Communications Enterprise, and then:

1. Select Settings.
1. Select Integrations. 
2. Select Personify Management.
3. Select Manage Tracking.
4. Select the Tracking items to sync to the Personify.
5. Select the time you would like for this information to come over.

NOTE: With any integration platform, there is a known use of data; for this reason, Communications Enterprise recommends that the data be sent over in off-peak hours.

Options for tracking data that can be returned to Personify include:

• Email Delivered
• Opens
• Click-throughs
• Unsubscribes
• Subscribes
• Suppressed
• All Bounces
• Soft Bounces
• Hard Bounces
• User Not Found Mailbox Full
• Bad Domain
• Temporarily Unavailable
• In Progress
• Send Failed
• Fax Sends
• SMS Sends
• Event Signups
• Survey Submissions
• Facebook Posts
• Facebook Comments
• Facebook Likes
• Twitter Tweets
• Twitter Replies
• Twitter Mentions
• Twitter Retweets
• Landing Pages Submitted
• Website Visits
• Goal Reached

Considerations before Uploading a Personify Query

Uploading recipients from the Personify interface to Communications Enterprise can be performed in a variety of ways. Below are the considerations that must be made before you upload your first query from Personify.

Unique Identifiers

Every database-driven system has a way to enforce uniqueness on records to avoid duplicates. Communications Enterprise offers two options for determining uniqueness:

1. Email address
2. Personify Master Customer ID (custom member ID)

NOTE: The default setting has the recipient’s email address as the unique ID.

Email as a Unique ID

When this default option is enabled, Communications Enterprise will only create one record for any single email address. For every record uploaded to Communications Enterprise that contains a custom ID and an email address, Communications Enterprise will create a unique record based on that email address.

NOTE: There can be NO duplicate email addresses with this method.

Implications

• Recipients only have one email address in the system and will not be sent duplicate messages
• Email addresses are not overwritten when a list is uploaded from Personify
• The most recently uploaded record details will be stored in Communications Enterprise for that email address

Custom Member ID as a Unique ID

When custom ID is selected, the Personify Master Customer ID will become the unique identifier.

Implications

• Every record uploaded to Communications Enterprise must contain a Personify Master Customer ID
• Duplicate email addresses can exist
• Email addresses can be overwritten from Personify based on custom ID
• Duplicate messages can be sent to the same email address if multiple Personify Master Customer IDs exist.

Replacing Communications Enterprise Records

At times there may be a reason for replacing a list of recipients in a given group; this is particularly true when it comes to updated membership lists or when your unsubscribe setting is unsubscribe to specified group:

Communications Enterprise provides two options when uploading a list:

• Adding recipients - If add to existing list is selected, Communications Enterprise will only add the records to the group with the records from the upload. Individual records will not be updated or overwritten.
• Replacing recipients - If Replace existing list is selected, Communications Enterprise will replace the records in the group with the records from the upload. The records being removed are not deleted, only removed from the group (they remain in the database), and there is no impact on the historical data.

NOTE: The replace method can be made the default. To do so, submit a request to your Implementation Project Manager or to Support.

If Replace is selected (Communications Enterprise’s default setting to overwrite existing data), based on the unique identifier will overwrite the corresponding data that exists in Communications Enterprise. This can be particularly useful in instances where there is one database of record that is in the process of being constantly updated.

NOTE: Add to Group will not update individual records in Communications Enterprise.

Character Limitations

When uploading a list to Communications Enterprise the maximum characters allowed per field are:

Field Type	Character Limit
E-mail, Address 1, Address 2, All Custom Fields	100
First Name, Last Name, Phone, Fax, City, State, Zip	50
Company	200
Enhanced Personalization Field	250

Uploading a Personify Query to Communications Enterprise

All individual queries that are transferred from Personify to Communications Enterprise are referred to as an upload job. Upload jobs that are allowed via the integration are:

• Marketing Lists in folders prefaced with RealMagnet
• SQL Views (the ID column must be aliased as MASTER_CUSTOMER_ID and the name of the view must begin with RealMagnet)

Transferring Lists from Personify to Communications Enterprise

Data can be transferred from Personify to Communications Enterprise via a scheduled upload or one-time transfer from within Communications Enterprise.

Scheduled Upload

The Real Magnet Upload Scheduler (RMUS) is a feature of the integration that allows for automated uploads to the Communications Enterprise system; it is extremely useful in the event there are any lists that you send to on a regular basis.

It allows the following upload job types:

• Run Now - This upload job will run once. Once completed, edits or changes cannot be made to this upload job.
• On Demand - This upload job will only run when the green play icon is clicked or using the Sync on Send functionality. This will deploy the upload job when a message is scheduled to send to the group attached to the upload job.
• Scheduled - This upload job will run on a scheduled basis, either daily or weekly, and can be manually run by clicking the green play button. When selecting a group connected to an active Marketing Automation campaign, this option can also upload groups on an hourly basis.

The RMUS can be accessed by logging into Communications Enterprise and selecting Settings. The details below will cover all aspects of the RMUS.

Icon Legend

Icon	Description
	Delete the upload job.
	Edit the upload job. This function only applies to On Demand and Scheduled jobs.
	Run job. This function only applies to On Demand and Scheduled jobs.
	View the rejected individual records (Communications Enterprise validates all email addresses uploaded to Communications Enterprise).

Upload Jobs Page Overview

This page contains a list of your existing upload jobs in Communications Enterprise, you’ll see a list of the existing upload jobs, and it will contain the following:

• Query Name - The name of the query in Personify.
• Date Created - The date the upload job was created.
• Job Type - Whether the job is Run Now, On Demand, or Scheduled.
• Frequency - The frequency of the scheduled job, for Run Now and On Demand this will remain blank
• Scheduled time - The times the job has either completed or is scheduled to run next.
• Start Time (HH:MM) – The time the upload job is scheduled to start.
• Last Run (MM/DD/YYYY HH:MM) – The time the upload job was last executed and completed.
• Next Run (MM/DD/YYYY HH:MM) – The next scheduled time it is set to run.
• Group Results - The group in Communications Enterprise the query was uploaded to and the results of the last upload, that includes the total number in the group and the number added. Any error that may occur on upload will surface here.
• Actions - The allowed actions a user can make to the upload job.

Create an Upload Job

To create an upload job in Communications Enterprise:

1. Select Settings.
2. Select Integrations.
3. Select Personify Management.
4. Select Create Upload Job.
5. Select a query
6. Select Create Map.
7. Select View Entire Field List or One by One.
8. Select which columns you would like to bring over to Communications Enterprise. These are a one-to-one relationship when mapping fields. This means that you can only map the fields on the left side of the screen with one item on the Communications Enterprise side once.
9. Click Create Schedule.
10. Select Create New Group or Add to Existing Group.
11. Select either Add to existing group or Replace existing list.
12. Depending on account settings the third upload step may reveal the option whether or not to update. Select Do not Update Existing Records (Only Add Records To Group) or Update Existing Records.
13. Click Create.
14. Select your frequency: Run Now, On Demand, or Scheduled.
15. Click Submit.

Manually Upload Individual Queries to Communications Enterprise

You may have users that want to upload .CSV files into the system, independent of the integration. When uploading a list within Communications Enterprise, independent of the RMUS in order for tracking information to report back to Personify, a user must include the Personify Master Customer ID and email address. Upon upload, the user must map the Personify Master Customer ID column to the Custom Member ID field in Communications Enterprise.

Field Type	Character Limit
E-mail, Address 1, Address 2, All Custom Fields	100
First Name, Last Name, Phone, Fax, City, State, Zip	50
Company	200
Enhanced Personalization Field	250

Communications Enterprise Data in Personify

Communications Enterprise Tracking Details

The tracking result of a message is the only information to report back to Personify, this includes opt-out information. This tracking information will update once a day, typically overnight. The Communications Enterprise tracking data is displayed on the Personify Member Record page, in the System Activities area.

The child form will contain the activity and sub-activity codes related to the Communications Enterprise integration. Because the Communications Enterprise Data is stored in Personify, it can be used for querying and data segmentation.

Communications Enterprise Unsubscribe Information

Customers using Interest Areas can push unsubscribe data to Personify as not only an activity record but it can also update a recipient’s Interest Area in Personify. Just like tracking, this is a one-way stream of information from Real Magnet to Personify. A breakdown of this relationship can be found on Manage Subscription Preferences with Personify page.

To associate a group, group category or message category with a Personify Interest Area, you’ll first need to meet the following requirements:

1. Your unsubscribe type must be by Group Category or Message Category.
2. The functionality must be enabled for your integration.

Associating Groups or Categories with Interest Areas

To create the one way link between Communications Enterprise and Personify, navigate to Settings.

1. Select Settings.
1. Select Integrations.
2. Select Personify Management.
3. Select Manage Unsubscribes.
4. Select which group or category in Communications Enterprise that corresponds to the Interest Area in Personify.
5. Once the selections have been made, click Submit.

When a recipient selects the one-click unsubscribe option, this information will write back to the CUS Customer Subsystem in Personify.

The Communications Enterprise integration stores the activity data to the dbo.CUS_ACTIVITY table. This is the default configuration. However, because the integration writes back directly to the Personify database instead of writing back to the dbo.CUS_ACTIVITY table, data can be stored in a custom table.

Creating Interest Areas in Personify

An Interest Area is a system type that is not fixed and must be created (OPT_IN_INTEREST_AREA). To do so:

1. Click System Admin.
2. Click System Codes.
3. Click System Types and Codes.
4. Click Create New Type.
5. Select CUS Customer Subsystem from the Subsystem menu.
6. Enter OPT_IN_INTEREST_AREA under Type.
7. You can choose what you would like for the description (e.g., Opt In Interest Areas).
8. Click Save.

To create an additional Interest Area for your recipients to opt-in or out of:

1. Click System Admin.
2. Click System Codes.
3. Click System Types and Codes.
4. Select CUS Customer Subsystem from the Subsystem menu.
5. Double-click CUS OPT_IN_INTEREST_AREA to select.

NOTE: If the OPT_IN_INTEREST_AREA option isn't available, you'll need to create this type.

6. Select Edit Codes for this type.
7. Click Add Code.
8. Enter a code and description.
9. Click Save.

NOTE: Codes must be Active and Email must be entered in Option 1 in order to be exposed in the Communications Enterprise integration.

To view the interest areas an individual is subscribed to:

1. Find the customer for which you'd like to view their participation records.
2. Click Participation.
3. Select Maintain Opt-in/Opt-Out Preferences.

Viewing Marketing Automation Information in Personify

Once integrated with Communications Enterprise’s Marketing Automation platform, a few additional items will now be visible to you in Personify:

• Additional Activity codes, including:
• Landing Pages Submitted
• Website Visits
• Goal Reached

Creating Records in Personify via Communications Enterprise Landing Pages

When creating a landing page campaign in Marketing Automation, there is an additional option to create records in Personify. This option is configured per landing page.

Requirements

• Marketing Automation
• The Stored Procedure RealMagnet_InsertProspect
• Communications Enterprise’s most recent version of the service

If you have a pre-existing integration and these options are not already available, create a case and we’ll review your account settings.

Configuration

When creating a landing page campaign in Marketing Automation, there is an additional option to create records in Personify. This option is enabled once you create a landing page – there will now be an option to Integrate this campaign with Personify Management.

When records are created in Personify, Communications Enterprise will use the email address to define uniqueness. If a record already exists by that email address in Personify, Communications Enterprise will ensure that the Custom Member ID is populated with the Personify Master Customer ID.

• A new record created from a landing page via Marketing Automation will be created in Personify as a Real Magnet constituent class.
• Insert a record with the following defaults:
• Country Code - ‘USA’
• CUS_ADDRESS_ID - ‘BLANK’
• ADDRESS_STATUS_CODE - BAD

Fields

If a Landing Page is configured to collect the following fields, it will also create the record with those fields in Personify.

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

Frequently Asked Questions

Question	Answer
Why are there multiple opens in my recipient’s activity history?	Communications Enterprise reports back gross opens. This means that each time a recipient opens the message, this record is scored and tracked.
Why is there no tracking data updating to my Personify?	Did you select tracking data? Log in to Communications Enterprise and walk through the below: Select Settings. Select Integrations. Select Personify Management. Select Manage Tracking. Select the Tracking items to sync to Personify.
Why is this individual record missing tracking information?	Ensure that individual is assigned a Personify Master Customer ID. If the individual was uploaded outside of the Real Magnet Scheduler, you must ensure that it also has its Personify Master Customer ID mapped to the Custom Member ID. This is how the Personify platform identifies that individual in its database. If an individual is missing this information, no tracking information will push back for that recipient to Personify.
How can I configure additional fields for my Marketing List?	For Marketing Lists, the integration will display whatever fields are available via the sys.all_columns in the Personify database as outlined in the Stored Procedure [dbo].[RealMagnet_GetFields], if there are additional fields that you would like to display, typically client teams create that Marketing List as a SQL view instead.
Why am I getting the message: “This upload job has one or more groups to which you do not have access.”?	Do you have access to the group? If you have an Enterprise account, you will need to ensure that you have access to the group the Upload Job is connected to, or ensure that the group has not been archived.
When I attempt to create an Upload Job, I receive an error when attempting to map my Upload Job or when uploading.	Is this a SQL view? All SQL views must contain the ID aliased as MASTER_CUSTOMER_ID, this is case sensitive.
What happens if the tracking data portion is canceled mid-stream?	Communications Enterprise logs the failure and re-attempts to send the data to Personify.
What happens if I am using Internet Explorer?	Due to Internet Explorer’s security configurations, as part of this integration installation, we recommend clients complete the following: 1. Add magnetmail.net to Trusted Sites. 2. Use Compatibility Mode.