The Communications Enterprise Higher Logic integration uses the Higher Logic API in conjunction with Communications Enterprise’s Universal Webservice. It is compatible across all browsers, and can be used in conjunction with the Communications Enterprise platform.

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 Higher Logic
• Managing Data within Higher Logic

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 Integration.
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.

Updating Higher Logic Password

NOTE: An administrative user must update these credentials in Communications Enterprise.

1. Navigate to Settings > Integration Settings.
2. Enter the Password.
3. 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

The Higher Logic integration does not push tracking; rather, if you're already integrated with one of Communications Enterprise’s products, the tracking will send back via that integration.

• Aptify
• AmNet
• iMIS
• MemberSuite
• MSCRM
• netFORUM Enterprise
• Personify
• Salesforce

Considerations before Uploading Higher Logic Communities

Uploading recipients from the Higher Logic 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 Community from Higher Logic.

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: email address or the Higher Logic Contact Key. These choices assume that there is a Communications Enterprise integration installed (e.g., netFORUM or Aptify). On the other hand, if your main integration is Personify, there are some considerations to be made in regards to Custom ID.

Personify and Custom ID for Higher Logic

When using Personify and Higher Logic, it's recommended that the Custom ID for your Communications Enterprise account remain as email. The default setting for a Communications Enterprise account 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

• Email addresses cannot be overwritten from Higher Logic

Custom Member ID as a Unique ID

When custom ID is selected as the unique identifier, this will be generated by the unique identifier supplied with your AMS or API process. in the case of Higher Logic, this is the Contact Key.

Implications

• Every record uploaded to Communications Enterprise must contain a Contact Key
• Duplicate email addresses can exist
• Email addresses can be overwritten from Higher Logic

Replacing Communications Enterprise Records

Communications Enterprise provides two options when uploading a Saved Search:

• 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 characters
First Name, Last Name, Phone, Fax, City, State, Zip	50 characters
Company	200 characters
Enhanced Personalization Field	250 characters

Upload a Higher Logic Community to Communications Enterprise

The integration works with the Lists. Lists will execute on demand at the time of run from the Real Magnet Upload Scheduler (RMUS). All other Communities will update according to the schedule you have set in the Admin section of Higher Logic once per day, or more often (such as hourly).

Create Lists in Higher Logic

List Builder Will outline how to create a list in Higher Logic. 

NOTE: You must have Super Admin permissions to create a List.

Transferring Communities from Higher Logic to Communications Enterprise

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

The 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 Saved Searches 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 applies to On Demand and Scheduled jobs only.
	Run the job. This applies to On Demand and Scheduled jobs only.
	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 the Communications Enterprise platform. The list will contain:

• Distribution List Name - The name of the list in Higher Logic.
• 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 - One of the following times.
• Start Time (HH:MM) – The scheduled start time of the upload job.
• Last Run (MM/DD/YYYY HH:MM) – When the upload job was last executed and completed.
• Next Run (MM/DD/YYYY HH:MM) – When the upload job is next scheduled to run.
• Group Results - The group in Communications Enterprise the query was uploaded to and the results of the last upload, including 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.
2. Select Higher Logic Management.
3. Select Create Upload Job.
4. Select a Community.
5. Select Create Map.
6. Select View Entire Field List or One by One.
7. 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.
8. Click Create Schedule.
9. Select Create New Group or Add to Existing Group.
10. Select either Add to existing group or Replace existing list.
11. 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.
12. Click Create.
13. Select your frequency: Run Now, On Demand, or Scheduled.
14. Click Submit.

Manually Upload Communities to Communications Enterprise

You may have users who want to upload .csv files into the system, independent of the integration. When uploading a list within Communications Enterprise, independent of the RMUS, a user must include the Contact Key and email address. Upon upload, the user must map the Contact Key column to the Custom Member ID field in Communications Enterprise. The character limits for the various field types are listed below.

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

Communications Enterprise Data in Higher Logic

The Communications Enterprise tracking data will send back overnight to your installed CRM integration. For Personify, Higher Logic recommends completing an upload job before tracking is pushed back, so that IDs are synced. Tracking will display in their respective areas based on your CRM.

Frequently Asked Questions

Why is this individual record missing tracking information? Ensure that individual is assigned a Contact Key. If the individual was uploaded outside of the RMUS, you must ensure that it also has its Contact Key mapped to the Custom Member ID field in Communications Enterprise. This is how the Higher Logic platform identifies that individual in your CRM database. If an individual is missing this information, no tracking information will push back for that recipient to the CRM.