This article is to outline the standard pieces of an app built on Cloudconnectors.eloqua.com


 

Credentials:

The credentials area is where you connect the CloudConnector with the Eloqua application. It typically has the following fields:

Eloqua DB - This is the instance of Eloqua that the connector is being configured to access. It is typically a name, with no spaces. This instance must have the API enabled.

User Account - This is the username of the Eloqua user that is accessing the Eloqua DB. This is typically a name (first name and last name) separated by a dot, with  no spaces. It is not an email address. This user must be in the API access security group.

Program Builder Step ID - This is the ID of the step within the Eloqua program builder. It is normally populated when the Connector is first configured. IF not, you can find that information within the step in program builder.

Enable Step (Run Automatically) - If this is set to disabled, the connector will not run. In order to run automatically, this needs to be set to enabled.


Configuration:
The configuration area will have fields that are specific to the connector being set up. It will often require the username/password for a third party system. As well, IF data can be potentially stored in multiple places within Eloqua (ie - Data Card OR Contact), or a specific Eloqua Asset needs to be selected (Form, Contact Group), it is typically done here.


Field Mappings:
If fields need to be mapped, either from Eloqua to a third party service OR from the third party service to Eloqua, it is done here.


Run Step:

Run step has 3 separate sub tabs:

 

Step Members:

This tab shows the records within the step in Eloqua. IF the numbers are off, you can click "Refresh" to have the service update with the current information.

The step shows 3 "statuses". They are:

Awaiting Action - these are records who have hit the step in program builder, but not been picked up by the Cloud Connector

In Progress - these are records who have been picked up by the Cloud Connector, but who have not been returned back to Eloqua

Complete - These are records who have been processed by the Cloud Connector and returned to Eloqua

Under step members, it is possible to reset the status of a record (ie - if you wanted to retest a record, you could set a record from Complete to Awaiting Action)


Run Step:

If there are records in the step in program builder, WITH the status of "Awaiting Action" you can run the step from within Cloud Connectors. This pushes a maximum of 10 records through. There are 2 options:

Dry Run - This will reach into the step in Eloqua, and return the ACTUAL data that will be sent to the 3rd party. It sends the data to the third party, with a flag indicating it's test data. It displays the data that is recieved back from the third party, but does not write the data into Eloqua.

Full Run - This will reach into the step in Eloqua, and return the actual data, which will be sent to the third party. The data will be returned and written to the Eloqua database.  If there is a cost to use the third party system, this will be incurred.

Sample Data:

The Sample Data tab allows you to processes records that aren't currently in the step in Program Builder. However, the records DO need to exist within the Eloqua install that is using the connector. IT will populate with the email address of the person configuring the step. Input each email address on it's own line. IF you do not check the "full run" box, this will be run as a dry run. If you do check the box, it will be run as a full run. Click "Test Contacts" to run.


History:

The history area shows the following information:

Total Queries - This shows how many times the step has processed

Valid Transactions - This shows how many times a record has been processed

Last Run time - This shows the last time the step executed

Error Count - IF there are errors this will show a count of them

Error Log - This will show the error message and the time