Jive Activity Feeder
This article will describe how to set up and configure the Jive Activity Feeder application. This application will query your Jive community, and "feed" new contacts into Eloqua (or update those that already exist) based on their daily activity.
*IMPORTANT* this app does not currently support Jive 6.
In order to use the app, you must be registered at cloudconnectors.eloqua.com. Jive access/credentials are also required for this app. The Jive REST API must be turned on and the Open Client Service enabled for this connector to work with your community.
Installation and Pre-Configuration
The Jive Activity Feeder does not require installation, as it is a standalone application that runs outside of Eloqua, and connects to your instance.
Things you'll need to do first:
- Make sure that the Eloqua user account that is being used for the feeder has Eloqua API access.
- Create a Contact Group in Eloqua (called a Shared List in E10), to store the Contacts created/updated by the feeder.
- *Optional* Create a DataCardSet (Custom Data Object) in Eloqua, to store the Activity data returned by the feeder.
Setup and Usage
To access the feeder, first visit cloudconnectors.eloqua.com and log in.
Once logged in, click on the Apps menu.
Next, click on Feeder, then Jive Activity Query. The following screen will appear:
Click New Step, and you will be presented with the following:
Select your Eloqua Credentials and click Go. The Configuration page will then be displayed.
On the Configuration tab, enter the following information:
- Description (optional): Some text about describing this feeder instance.
- Jive Community URL: The URL of your Jive community.
- Jive User Name: Your Jive username (must have proper API privileges).
- Jive Password: Your Jive password.
- Contact Group for Results: The Contact Group/Shared List that you'd like the contacts added to when the feeder runs.
- Store Community Data In: Where you would like the returned data stored in Eloqua. Options are Contact Record or Custom Data Object.
- Custom Data Object (only displayed if Custom Data Object is chosen to store data): The Custom Data Object to store the returned data in.
- Click Save Settings.
Now, click on the Field Mappings tab to choose where you would like to put the data returned from when the feeder runs.
On the Mappings tab, choose which Eloqua Contact and/or Custom Data Object fields to map corresponding data from Jive to.
The data returned from Jive falls into three categories:
- Profile data (shown above): Information pulled from the Jive user profile.
- Latest Activity data: Detailed information about the most recent activity that a member performed within the last day.
- Activity Totals: The total number of each activity the member performed in the last day.
If you choose to store the data in a Custom Data Object:
- For the Custom Data Object fields, the list selections will be populated based on the existing Custom Data Object chosen on the Configuration tab.
- Click Save Settings.
Now that the Configuration is complete, and the Mappings have been set, it's time to Test the feeder. Click on the Test tab.
On the Test tab you can test run the feeder. You can choose between a “Dry Run” (no data will be written to Eloqua) and a “Full Run” (The data will write to Eloqua – this is effectively a manual run of the feeder).
The History tab shows a history of previous feeder runs.
Once all is configured, all that is left to do is switch back to the Credentials tab and Run the feeder.
Now that the feeder is configured and enabled, the members and their activities will begin to flow into Eloqua. As members perform activities in your community, they will be brought into Eloqua as contact records and placed in the chosen group/shared list. If the contact does not exist in Eloqua, a new one will be created, and if you select the option, a custom object attached to the record containing the returned data. If the contact already exists, the contact record will be updated accordingly, as well as the custom data object attached to it (if you have selected this option).
Things to keep in mind:
- When the feeder runs, it will look at all activity in your community in the last day, and bring back those members that have done performed contributed (blog post, document, status update, discussion etc.).
- Detailed information will be brought back for the most recent activity only. The totals will be the aggregate of all other activity performed in each category.
- When storing the data in a contact record, the fields will be overwritten with new numbers/information each time it runs.
- This feeder is intended to be run on a daily basis, so will capture newly joined members also. You can use the Join Date to determine if they are new.