Creating Integration Credentials For The Erbium Platform - a guide for Eloqua Administrators

Connecting the ERBIUM Platform to your Eloqua environment requires the following credentials for a unique, dedicated, API enabled ORACLE Eloqua user account:

• Company Name
• Username
• Password

Within the ORACLE Eloqua, when creating the user account to be used by the ERBIUM platform please ensure the following:

• The account should be created within your production instance (i.e. not a test instance) of ORACLE Eloqua
• The account should be a dedicated account for the sole use of the ERBIUM platform.
• The password for the dedicated user should be set to never expire.
• The user must be assigned to the 'API Users' Security Group within ORACLE Eloqua (See ORACLE Eloqua screen below)

Why Do I Need a Dedicated User Account ?

While you can theoretically use any user account to set up the integration, we strongly recommend against using a personal user account that is associated with an individual. If you do, your ERBIUM Platform connection can stop working unexpectedly if that person leaves your organization, changes their email or password, or their account is deactivated for any other reason.

Using a dedicated user account helps to avoid these types of issues, and can prevent problems with your integration in the future.

Why Do I Need a User Account that Never Expires ?

While you can theoretically use an account that expires you run the risk that your integration stop working without notice resulting in a loss of important information.

Why Do I Need a User Account with "API Users" Security Group ?

The "API Users" security group indicates to Eloqua that ERBIUM can connect and communicate via a programming interface instead of a screen based dashboard for example.