Skip navigation
1 2 3 Previous Next

Do It

32 Posts authored by: TJ Fields-Oracle

When using Eloqua Cloud Apps, it is important to remember that the Eloqua credentials stored within your apps will need to be kept up to date.  When your Eloqua credentials expire, and you change them within Eloqua, they will need to also be changed on cloudconnectors.eloqua.com.

 

Doing this is a quick and easy process, as you need only change them in one place, and it will cascade across all apps that use that set of credentials.


Here is what you will need to do:


  1. Log into cloudconnectors.eloqua.com,
  2. Go into the credentials management area by clicking your username on the top right of the main menu bar, and selecting My Credentials from the drop-down.
  3. Find the appropriate Eloqua credentials from the list and click the edit icon (the little pencil).
  4. Input the new (or updated) Eloqua credentials and then click Update.
  5. Make sure that the credentials show a green "Valid" next to the Credentials label.
  6. Close the window and you are all set!  Any app using those credentials will now be up to date with your Eloqua username and password.


Note: When your credentials expire, you should receive a notification email from cloudconnectors.eloqua.com letting you know.

 

Here is a brief video of how to do this http://screencast.com/t/X5cOgMgW6u0

When setting up your Eloqua cloud app, it is always a good idea to test it out to make sure all is working as expected before enabling it.  In order to help you do this, the cloud apps offer a set of tools. 


To access the tools, go into the setup screen for your app and click on the Test tab.

 

StepMembers.png

 

The Step Members tab will show you the counts of contacts in your step.  If your campaign is not activated, there will likely not be any members Awaiting Action.  If you do have members in one of the statuses, you can use the Action field to view the members or manually change their status.

 

The Clear Wrong Member Types button is used when the connector is trying to act on Contact records, but finds Accounts/Companies or Prospects in the step instead.

 

Next, let's look at the Run Manually tab.

 

RunManually.png

 

The Run Manually tab will allow you to perform a Dry Run or a Full Run of your step.  A Dry Run will simulate a run, but will not actually write the data back to Eloqua.  A Full Run will perform a run of your connector, and actually update Eloqua with the results.  When you perform a run, a table will pop up upon completion to show you the results.  The table will provide information on any errors that occur so that you can make adjustments prior to enabling.

 

Next, there's the Sample Data tab.

 

SampleData.png

 

Use the Sample Data tab if you wish to test your setup on select contacts.  Enter their email addresses, one per line, and click Test Contacts. (Note: these contacts must already exist in your instance).

If you check the Full Run box, the data will be written to Eloqua, if left unchecked, it will simulate the connector and show you the results.

 

To check the history of your step execution, click on the History tab.  Take note of any messages in the Error Log, and troubleshoot accordingly.

 

History.png

 

Some apps will also have an extra Tools tab that allows the retrieval of raw XML that can also be used to troubleshoot.

 

On24TestTools.png

 

Now that you have tested your step, you should be all set to enable it and your data will being to flow into Eloqua.

 

If the app is enabled, and still not working correctly, use the Support tab for further troubleshooting tips.

If anyone has recently been experiencing issues with Cloud Components not properly rendering, they should now be back and up and running.

Important: This Cloud Connector/Component will be decommissioned  after March 31st 2017. Please review the App Replacement Cheatsheet for instructions

 

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.

 

What is the difference between Appcloud.eloqua.com and Cloudconnectors.eloqua.com?

 

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.

CC_Menu.png

 

Next, click on Feeder, then Jive Activity Query.  The following screen will appear:

NewStep.png

Click New Step, and you will be presented with the following:

Creds.png

Select your Eloqua Credentials and click GoThe Configuration page will then be displayed.

Config.png

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.

 

Mappings1.png

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.

Mappings2.png

    • Activity Totals: The total number of each activity the member performed in the last day.

Mappings3.png

 

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.

TestTab.png

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.

History_Tab.png

Once all is configured, all that is left to do is switch back to the Credentials tab and Run the feeder.

Credentials_Tab.png

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.

Important: This Cloud Connector/Component will be decommissioned  after March 31st 2017. Please review the App Replacement Cheatsheet for instructions

 

Data.com Cloud App

 

This post will describe the Data.com Cloud App, and how to use it within your instance of Eloqua.

 

With the Data.com Cloud App, you now have access to clean, up-to-date, and comprehensive data that can be accessed from within your marketing automation programs.

 

In order to use the App, you must be registered at cloudconnectors.eloqua.com.  When creating your account, make sure the user whose Eloqua credentials you provide is added to the “API Users” security group to ensure it has API access.  Your Eloqua administrator will have to do this for you.   You will also need a Data.com (Jigsaw) account (Note: the app uses whatever license you have with Jigsaw, so you will be charged for data accordingly).

 

What is the difference between Appcloud.eloqua.com and Cloudconnectors.eloqua.com?

 

Data.com Cloud App Components

 

The Data.com integration consists of several components, each of which are set up in roughly the same manner.  The instructions should be easily translatable between the different connector options.

 

The following Cloud Connectors are available:

 

    • Search for Contacts and/or Prospects - When you have companies that you’re interested in, whether you want to flesh out the list of the key people at an account that has shown some interest, or to proactively target a territory or a list of named accounts, this connector allows you to find the contacts at those companies who are in key roles. Simply by specifying the role (ie, marketing, sales, finance), level (ie manager, director, vice president), and geography, you can retrieve as many contacts as you specify at each company that flows through a given program builder step.
      • Using the Data.com (Jigsaw) Contact Search connector, you can pass in a company name (located on the Company/Account record) and retrieve from Data.com the associated contacts by level and role, and put them into a contact group/shared list in Eloqua.
      • Using the Data.com (Jigsaw) Prospect Search connector allows the passing of a company name (located on the Company/Account record) to Data.com to retrieve the associated contacts (as Eloqua Prospects, no phone or email) by level and role.

 

    • Retrieve Company data - When the information on companies in your database goes little farther than a name, you will be very limited in your ability to market to them. This is a common problem when the information comes in via web forms though as company questions like revenue, industry, number of employees, or stock ticker tend to bulk up forms and drive visitors away. With the Company Info cloud connector, you can quickly append and correct this type of information directly from the Data.com company database.
      • Using the Data.com (Jigsaw) Company Info (Contacts) connector, you can pass in a company name, stock ticker, or URL (located on the contact record) and retrieve from Data.com the associated company information to pull into the contact record.
      • Using the Data.com (Jigsaw) Company Search connector, you can pass in a company name, stock ticker, or URL (located on the company/account record) and retrieve from Data.com the associated company information.  This information is then written to the company/account record.

 

    • Refresh Contact data - When a contact enters your database, its information begins to go out of date immediately. Titles change, phone numbers are updated, and new information may be gathered that you don’t yet have. This Cloud Connector allows you to query Data.com for a known contact and update any information on that contact.
      • With the Data.com (Jigsaw): Contact Refresh connector, you can query Data.com for a known contact and update any information on that contact.

 

Components of the AppCloud

 

Installation

 

To illustrate how to install the apps in Eloqua, we will look at installing the Contact Search connector.

 

Log into cloudconnectors.eloqua.com and click on the Apps menu.

 

AppMenuContact.png

You'll see the different Data.com connector options listed.  Select Data.com Contact Search from the menu.

 

The following screen will appear:

NewStepInstall.png

 

Click on Install Connector.  You'll then be shown the installation screen.

InstallInstructions.png

 

If you are an Eloqua customer administrator, you can click on Add Connector, and it will take you to the Cloud Connector Management area in your instance, with the install settings pre-populated.

 

You can also choose to do a Manual Install.  Note the settings above, then go into the Cloud Connector Management area in your instance. 

CloudConnectorSetup.PNG

Enter the settings as shown below:

CloudConnectorManagement.png

 

 

Enter the following information:

 

The method above can be used to install the other Data.com connectors.  The connectors that return Contact data can be found under the Contact Data menu, while those that return Company or Prospect data can be found other their corresponding menus.

AppMenuCompany.png

AppMenuProspect.png

 

Configuration

 

To configure apps that operate on Contact records (Contact Refresh, Company Info), you can use the Canvas (as shown below).  For connectors that operate on Company/Account records (Contact Search, Prospect Search, Company Search), you will need to use Program Builder, but the configuration process is the same.

    • Add a step to your marketing automation program at any point you would like to run the connector on a Contact record.
      • Note: The Cloud Connector will run on any Contact that flows into that step, and return the result(s) to fields within the Contact record.
      • Make sure that you have an account on cloudconnectors.eloqua.com.
      • Drag a "Send to Cloud Connector" step onto the Canvas from the toolbar:

Canvas1.png

    • Double-click on the "Send to Cloud Connector" step, select the connector from the list, and click on the configure button.

Canvas2.png

    • When the Login screen appears, enter your cloudconnectors.eloqua.com credentials and click Log In.

CC_Login.png

    • Next the first setup screen for the App will appear.

Creds2.png

    • The value for Step ID will automatically populate.  Select your Eloqua Credentials from the list, then click Go.

 

    • The Configuration page will then be displayed.

Config2.png

 

On the Configuration tab, enter the following information:

      • Description (optional):  Some text to describe this connector instance
      • User Name:  Your Jigsaw user name
      • Password: Your Jigsaw password
      • Click Save Settings.

 

Now, click on the Mappings tab.

FieldMappings2.png

On the Mappings page, choose the following:

      • Company Identifying Field:  The field on the Contact record containing the company Name, Stock Ticker, or Website to search Data.com for.
      • Choose the contact fields to save the returned data in. Data.com returns a lot of great information, but if you don't want any particular field, simply do not map it on this page.

      • Click Save Settings.

 

Testing

 

You are now ready to Test the connector to make sure all is set correctly.  Click on the Test tab.

CC_Test1.png

Once your step is enabled and running, the Step Members testing tab will show you the number and status of Contact records ( for Contact Refresh, Company Info) or Company/Account records (for Contact Search, Prospect Search, Company Search) in your step.

 

The Run Manually testing tab will allow you to perform a Dry Run or a Full Run of your step.

CC_Test2.png

A Dry Run will simulate a run, but will not actually write the data back to Eloqua.  A Full Run will perform a run of your connector, actually updating Eloqua.

 

Use the Sample Data tab if you wish to test your setup on select contacts or companies/accounts.

CC_Test3.png

Enter contact email addresses (or company/account names), one per line, and click Test Contacts. (these contacts or companies/accounts must already exist in your instance).

       (Note: If you check the Full Run box, the data will be written to Eloqua, if left unchecked, it will simulate the connector and show you the results.)

 

To check the history of your step execution, click on the History tab.

HistTab.png

Enabling

 

Now that you have tested your step, it's time to enable it.  Click on the Credentials tab.

CredsTabStepNew.png

 

When you are ready to enable your step, click the Enable Step button. (Note: Remember to also enable your program in Eloqua)

 

As Contact records (for Contact Refresh, Company Info) or Company/Account records (for Contact Search, Prospect Search, Company Search) flow into the step, the app will connect to Data.com and return data on the Contacts, Companies/Accounts, and Prospects.  The data will then be pulled into Eloqua for use in your marketing campaigns.

 

The other connectors are set up in the same manner, but contain different configuration and mapping options.

There have been some useful enhancements made to the Form Population Cloud App recently, and I just wanted to bring them to everyone's attention.

 

For those not familiar with this app, it is a Cloud Component that can be added to an E10 landing page, along with your form, and will allow you to pre-populate the form with data from Eloqua.

 

You can configure the app to fill in your form fields with Eloqua contact data, visitor profile data, static values, query strings, and now...values from DataCards and Email Group subscription status.

 

When a known contact or tracked visitor lands on your page, the app will pull the chosen data from Eloqua, and pre-populate your fields with the data according to your mappings.  The component has been enhanced to also support multi-select lists, check-boxes.

 

If you haven't already, give the app a try, it may save you some headaches!!

Important: This Cloud Connector/Component will be decommissioned  after March 31st 2017. Please review the App Replacement Cheatsheet for instructions

 

See the attached document for instructions on how to send Video Digital Body Language to Eloqua using Questionmine.

 

Questionmine can also be found on the Eloqua AppCloud

Important: This Cloud Connector/Component will be decommissioned  after March 31st 2017. Please review the App Replacement Cheatsheet for instructions

 

DataCard Evaluator Cloud App

 

This post will describe the DataCard Evaluator Cloud App, and how to use it within your instance of Eloqua.

 

With the DataCard Evaluator Cloud App, you can analyze multiple DataCards attached to a contact, and return values based on field comparisons (max, min, sum, or average values).  The returned value can be written to a contact field of your choosing.

 

In order to use the App, you must be registered at cloudconnectors.eloqua.com.  When creating your account, make sure the user whose Eloqua credentials you provide is added to the “API Users” security group to ensure it has API access.  Your Eloqua administrator will have to do this for you.

 

What is the difference between Appcloud.eloqua.com and Cloudconnectors.eloqua.com?

 

DataCard Evaluator Cloud App Components

 

The DataCard Evaluator Cloud App consists of the following Cloud Connector:

 

    • DataCard Evaluator - analyze multiple DataCards attached to a contact, and return values based on field comparisons (max, min, sum, or average values).

 

Components of the AppCloud

 

Installation and Configuration

 

To install the app in Eloqua, do the following.

 

Log into cloudconnectors.eloqua.com and click on the Apps menu.

AppsMenu.png

Click on Contact Data, then Data Card Evaluator, and the following screen will appear:

Install_App.png

Click on Install Connector.  You'll then be shown the installation screen.

Add_Connector.png

If you are an Eloqua administrator, you can click on Add Connector, and it will take you to the Cloud Connector Management area in your instance.  The install settings will be pre-populated.

 

You can also choose to do a Manual Install (note the settings above) and then go into the Cloud Connector Management area in your instance.  Enter the settings as shown below.

CloudConnectorSetup.PNG

CloudConnectorManagement.png

 

 

  Enter the following information:

 

To configure the App, do the following:

    • Add a step to your marketing automation program at any point you would like to run the data card evaluator connector on a Contact record.
      • Note: The Cloud Connector will run on any Contact that flows into that step, and return the result(s) to another field within the Contact record.
      • Make sure that you have an account on cloudconnectors.eloqua.com.
      • Drag a "Send to Cloud Connector" step onto the Canvas from the toolbar:

Canvas1.png

    • Double-click on the "Send to Cloud Connector" step, select DataCard Evaluator from the list, and click on the configuration button.

Canvas2.png

    • When the Login screen appears, enter your cloudconnectors.eloqua.com credentials and click Log In.

CC_Login.png

    • Next the first setup screen will appear.

Creds.png

    • The value for Step ID will automatically populate.  Select your Eloqua credentials, then click Go.

 

    • The Configuration page will then be displayed.

Config.png

On the Configuration tab, enter the following information:

      • Description (optional):  Some text about this connector instance
      • Rule to use: This is the rule that will be run on the set of DataCards attached to the contact.  The result of this rule will be written to the result contact field selected on the Mappings tab

Options are as follows

        • Average of Values:  calculates the average of numeric values in the Field to Evaluate.
        • Maximum of Values:  determines the highest (maximum) of numeric values in the Field to Evaluate.
        • Minimum of Values:  determines the lowest (minimum) of numeric values in the Field to Evaluate.
        • Latest of Date Values:  finds the most recent (latest) of date values in the Field to Evaluate.
        • Earliest of Date Values: find the oldest (earliest) of date values in the Field to Evaluate.
        • Count of Values:  determines the count of DataCards in the set mapped to the current contact.
        • Sum of Values:  returns a sum of the numeric values in the Field to Evaluate.
        • Field A where Field B is Maximum: returns the chosen contact field (the Field to Select on the Mappings tab) from the DataCard that contains the highest (maximum) numeric value in the Field to Evaluate.
        • Field A where Field B is Minimum: returns the chosen contact field (the Field to Select on the Mappings tab) from the DataCard that contains the lowest (minimum) numeric value in the Field to Evaluate.
        • Field A where Field B is Latest:  returns the chosen contact field (the Field to Select on the Mappings tab) from the DataCard that contains the most recent (latest) date in the Field to Evaluate.
        • Field A where Field B is Earliest:  returns the chosen contact field (the Field to Select on the Mappings tab) from the DataCard that contains the oldest (earliest) date in the Field to Evaluate.
        • Field A where Field B is Equals X:  returns the chosen contact field (the Field to Select on the Mappings tab) from the DataCard that equals the exact value in the Field to Evaluate.

 

      • Click Save Settings.

 

    • Next, click on the Mappings tab.

Mapping.png

 

On the Mappings tab, select the following (Note: in order to explain their use, ALL possible fields/settings are shown below.  Which fields/settings will show depends on the Rule to use that you have set):

 

Contact Fields

      • Email Address: the field on the Contact record containing the email address.
      • Result:  the contact field to store the result of the evaluated Rule to use.
      • Result (Number):  the contact field to store the result of the evaluated Rule to use (shown when the Rule to use is a numeric operation)
      • Result (Date):  the contact field to store the result of the evaluated Rule to use. (shown when the Rule to use is a date operation)

 

DataCard Fields

        • Email Address: the field on the Custom Data Object containing the email address (used to find DataCards mapped to a contact).

        • Field to Evaluate:  the Custom Data Object field used to evaluate the Rule to use.
        • Field to Select:  the Custom Data Object field to return when running Field A where Field B operations.

 

      • Click Save Settings.

 

You are now ready to Test the connector to make sure all is set correctly.  Click on the Test tab.

CC_Test1.png

Once your step is enabled and running, the Step Members testing tab will show you the counts of contacts in your step.

 

The Run Manually testing tab will allow you to perform a Dry Run or a Full Run of your step.

CC_Test2.png

A Dry Run will simulate a run, but will not actually write the data back to Eloqua.  A Full Run will perform a run of your connector, actually updating Eloqua.

 

Use the Sample Data tab if you wish to test your setup on select contacts.

CC_Test3.png

Enter their email addresses, one per line, and click Test Contacts. (these contacts must already exist in your instance).

       (Note: If you check the Full Run box, the data will be written to Eloqua, if left unchecked, it will simulate the connector and show you the results.)

 

To check the history of your step execution, click on the History tab.

History_Tab.png

Now that you have tested your step, it's time to enable it.  Click on the Credentials tab.

CredsTabStepNew.png

 

When you are ready to enable your step, click the Enable Step button. (Note: Remember to also enable your program in Eloqua)

 

As Contacts flow into the step, the app will look in the Custom Data Object that you selected on the Configuration tab, and find the DataCards mapped to the contact.  It will then evaluate the chosen Rule to use against the Field to Evaluate, and return the resulting value to the Result contact field.

Important: This Cloud Connector/Component will be decommissioned  after March 31st 2017. Please review the App Replacement Cheatsheet for instructions

 

SnapApp Feeder

 

This article will describe how to set up and configure the SnapApp Feeder application.  This application will allow you to "feed" new contacts into Eloqua (or update those that already exist) based on their interaction with your SnapApp(s).

 

In order to use the app, you must be registered at cloudconnectors.eloqua.com.

 

What is the difference between Appcloud.eloqua.com and Cloudconnectors.eloqua.com?

 

Installation and Pre-Configuration

 

The SnapApp 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. For more information about creating a contact group, please search the knowledge base for an article named "Database Management".
    • Create a DataCardSet (Custom Data Object) in Eloqua, to store the information 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.

Feeder_Menu.PNG

 

Next, click on Feeder, then SnapApp Feeder.  The following screen will appear:

NewFeeder.png

Click New Step, and you will be presented with the following

Creds.png

Select your Eloqua Credentials and click GoThe Configuration page will then be displayed.

ConfigUNPW.png

On the Configuration tab, enter the following information:

    • Description (optional):  Some text about describing this feeder instance
    • SnapApp Username:  Your SnapApp Username (email address)
    • SnapApp API Key:  Your SnapApp API Key
    • SnapApps to Display:  Controls which SnapApps are shown in the SnapApp drop-down list.  Options are:
      • All Apps: Will list all of the SnapApps in your account
      • Apps by Campaign: Will present you with another option to select a Campaign from your account, then will display the SnapApps associated to that campaign.
    • SnapApp:  This is the SnapApp that you want to feed data in from.
    • Contact Group for Results:  The Contact Group/Shared List that you'd like the contacts added to when the feeder runs.
    • Store Data In:  Where you would like the return data stored in Eloqua.  The only option for this feeder is Custom Data Object.
    • Custom Data Object:  The Custom Data Object to store the SnapApp data in.

 

Depending on the type of SnapApp you select, the following additional settings will be displayed:

 

    • Questions:  Up to 10 questions that you want to track the answers to (for Quiz type SnapApps) .

QuestionsConfig.png

    • Additional Fields:  Up to 5 additional fields that you wish to track.

AdditionalConfig.png

    • Click Save Settings.

 

Now, click on the Field Mappings tab to choose where you would like to put the data returned from SnapApp when the feeder runs.

Mappings_Tab.png

On the Mappings tab, choose which Eloqua Contact and Custom Data Object fields to map to corresponding data from the SnapApp system.

    • For the Custom Data Object fields, the list selections will be populated based on the existing Custom Data Object chosen on the Configuration tab.
    • For Display Name Field, the field you choose MUST be set as Unique in Eloqua in order for the feeder to function properly.  (Note: this field cannot be set to email address - see Eloqua Cloud Apps: Custom Object Unique Codes for more info).

 

Depending on the type of SnapApp you select, the following additional mappings will be displayed:

 

    • Answers:  The answers to up to 10 questions that you chose on the Configuration tab (for Quiz type SnapApps).

QuestionsMapping.png

    • Additional Fields:  Up to 5 additional fields that you wish to track.

AdditonalMapping.png

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

TestTab.png

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.

History_Tab.png

Once all is configured, all that is left to do is switch back to the Credentials tab and Run the feeder.

Credentials_Tab.png

Now that the feeder is configured and enabled, the leads from your SnapApp will begin to flow into Eloqua.  If the contact does not exist in Eloqua, a new one will be created, and a custom object attached to the record containing the returned data.  If the contact already exists, the record will be updated accordingly, and a new custom data object attached to it.

Now that we've looked at Event / Webinar Cloud Apps - Registering Dynamically, let's look at how to dynamically query for attendance.

 

There is a new capability within the Event/Webinar cloud apps (WebEx, Adobe, Citrix GTW) that allows you to dynamically source the ID from either a contact record, or a custom data object.

 

In the previous post, we registered the contact for an event, sourcing the ID from the contact record.  When we did that, the connector created a Custom Object/Data Card, mapped to each contact record, that contained the Event/Webinar ID.  We want to use the ID contained in that same Custom Object / Data Card to query for attendance.  When the attendee is found, we also want to write the attendance data back to the same Custom Object / Data Card.

 

Let's start by setting up a Query connector.  On the Configuration page, choose to source the ID from a Custom Data Object Field.

 

CDO_As_Source.png

If you choose the source type of Dynamic (in a Custom Data Object Field), when the connector runs, it will look at the contact and find all of their mapped Custom Objects/Data Cards in the chosen Custom Data Object/Data Card Set.

 

Now let's set up a rule to handle the case where multiple custom objects are returned for a given contact.  In the Dynamic Event Source Configuration section, choose your Selection Rule.  Based on your choice, the section will be displayed as follows:

Eloqua Cloud Connectors - Step Details - Google Chrome_2013-02-15_15-45-30.png

Or

Eloqua Cloud Connectors - Step Details - Google Chrome_2013-02-15_15-45-43.png

The Selection Rule will be evaluated against to field chosen for Field to Evaluate on the Mappings page.  The choices are as follows:

  • Latest of Date Values - Returns the object with the field containing the latest (most recent) of date values.
  • Earliest of Date Values - Returns the object with the field containing with the earliest (oldest) of date values.
  • Field Contains Value - Returns the object with the field containing the Comparison Value.
  • Field Equals Value - Returns the object with the field exactly matching the Comparison Value.

 

We now have our rule for matching, but we'll need to chose the Field to Evaluate, as well as the Custom Data Object field that contains the Event/Webinar ID to use for the query.

CDO_As_Source_Mapping.png

 

When the connector runs, if multiple records are found, it will apply the Selection Rule to the Field to Evaluate and return the matching record.  It will then and retrieve the Event/Webinar ID from the chosen field in the Custom Object, and use that to query for attendance.  The attendance data will be written back to the same object that acts as the source.

 

By using these new dynamic ID source capabilities, you can streamline your Event/Webinar management.

In addition to the recent release of Form Tools - Running a Cloud Connector via Form Processing Step, enhancements to the Eloqua Event/Webinar apps were also introduced.  Now you can Form Tools - Running a Cloud Connector via Form Processing Step, and also use a field on the contact record or a mapped Custom Data Object, as a dynamic source for the Event/Webinar ID.

 

This means that you can use the same custom object created when you registered the contact, to query for attendance and hold the returned data.

 

To see this in action, let's first configure a Form Tool to register a contact. (Note: this will also work when running the Register connector on the canvas or program builder)

 

Start by following the step from Form Tools - Running a Cloud Connector via Form Processing Step.

 

On the Configuration screen, let's choose to source the ID dynamically from a contact field.

Eloqua Cloud Connectors - Step Overview - Google Chrome_2013-02-19_16-07-51.png

If you choose the source type of Dynamic (in a Contact Field), when the connector runs, it will look for the ID in the contact field that you specify on the Mappings page.

Eloqua Cloud Connectors - Step Overview - Google Chrome_2013-02-20_11-26-39.png

By doing this, we can use the same connector to register contacts for different events/webinars.  So, we can put a form field containing the ID (hidden or shown) on your registration form and map it to the contact record.  When the contact submits the form, the ID will be written to their record.  Now, when the Form Tool executes for the contact, it will use the ID found in the field and register them for that Event/Webinar.

 

The other thing we'll do is save the Join URL, Event/Webinar ID (and any other returned data) to a Custom Data Object/Data Card Set.

Eloqua Cloud Connectors - Step Overview - Google Chrome_2013-02-20_10-12-16.png

When the connector executes, it will create and link a new Custom Object/Data Card to the contact, in the specified Custom Data Object/Data Card Set that contains the Event/Webinar ID.

 

Now for the really cool part...we can use this same Custom Data Object with the Query connector, and dynamically source the ID from the Custom Data Object itself.  So, we can use the same object to hold both the Register information (Join URL etc) and the Query results (minutes attended, polls answered etc.).

 

See Event / Webinar Cloud Apps - Querying Dynamically for details on how to do this.

With the most recent release of cloudconnectors.eloqua.com, you may have noticed a New Form Tool button on the connector overview pages.

 

You may be asking yourself "what is that" or "how does that work"??  Well, with this new feature, you now have the ability to set up a Cloud Connector to run "one-off" when a contact submits a form.

 

To illustrate how this works, let's walk through an example.  As a marketer, I want to be able to use the WebEx Register Attendee connector to register a contact for an event.  I have found that, when using the connector in a program, I am unable to process those "last minute" registrations due the run cycle of the steps on the canvas.  Since I am already using a form submit to add contacts to the program, which in turn kicks off the registration step, it would be really great if I could just execute the same connector functionality as soon as form is submitted.  Well, this is where Form Tools come in!!

 

Here's how to set things  up...

 

Start by logging into cloudconnectors.eloqua.com, the clicking on the App menu.

 

AppsMenu.png

Next, select the WebEx: Register connector from the Communicate menu.  (NOTE: You can set up any program step-based Cloud Connector as a Form Tool)

 

The connector overview page will then be displayed.

NewTool.png

 

Click on the New Form Tool button.  The Credentials page will be displayed.

 

Creds.png

Choose your Eloqua Credentials, and then click Go.

 

InstructionsLink.png

When the New Form Tool page shows up, you'll notice that the page looks exactly the same as it would if you were setting the connector up from a program step.  The difference here is that you do not need to Enable the step, as this will not run on a scheduled basis.  More on that later.

 

Continue to Configure the app as you normally would, and don't forget to set up any required Mappings.  When this is complete, Save your setup and then click on the Instructions link.

Instructions.png

The Instructions will then appear, explaining how to use the new Form Tool.  Highlight and copy the URL shown next to the "Point the processing step to" bullet...you will need it for the next step.

 

Go into Eloqua, and if you have not already, create the form that will be used for the event registration.  In the Form Editor, go into the Processing Step area and create a new Post Data to Server step.

EloquaFormProcessingStep.png

Paste the URL that you copied from the Form Tool configuration screen into the box, as shown above.  Save the form.

 

Setup is now complete!  When this form is deployed, and a contact fills in the required info and submits, the WebEx Register Attendee connector will fire "one-off" and register the contact for the event.  The connector acts as it normally would, updating the contact or custom data object (depending on your setup choice) with the Join URL etc.

 

Some things to keep in mind...

  • As mentioned earlier, you do not need to Enable this connector.  It does not run on a scheduled basis, but rather is "triggered" by a form submit via the processing step.
  • You can set up any program step-based connector as a Form Tool.  So, in addition to event registration you can perform things like one-off String Manipulation or Concatenation, or Normalize contact data on the fly.
  • The connector is set up the same way as if it was being executed via a program step.  This means it can create custom objects, modify the contact record, or trigger an external event like sending  a Tweet when a form is submitted.r

Important: This Cloud Connector/Component will be decommissioned  after March 31st 2017. Please install the replacement app.

 

Contact Data Normalizer Cloud App

 

This post will describe the Contact Data Normalizer Cloud App, and how to use it within your instance of Eloqua.

 

With the Contact Data Normalizer Cloud App, you can now normalize the data in a given field against a number of maintained master lookup tables.

 

In order to use the App, you must be registered at cloudconnectors.eloqua.com.  When creating your account, make sure the user whose Eloqua credentials you provide is added to the “API Users” security group to ensure it has API access.  Your Eloqua administrator will have to do this for you.

 

What is the difference between Appcloud.eloqua.com and Cloudconnectors.eloqua.com?

 

Contact Data Normalizer Cloud App Components

 

The Contact Data Normalizer Cloud App consists of the following Cloud Connector:

 

    • Contact Data Normalizer - allows you to  normalize the data in a given field against a number of maintained master lookup tables.

 

Components of the AppCloud

 

Installation and Configuration

 

To install the app in Eloqua, do the following. Log into cloudconnectors.eloqua.com and click on the Apps menu.

 

AppsMenu.png

Click on Contact Data, then Data Normalizer, and the following screen will appear:

InstallConnector.png

 

Click on Install Connector.  You'll then be shown the installation screen.

InstallConnector2.png

If you are an Eloqua administrator, you can click on Add Connector, and it will take you to the Cloud Connector Management area in your instance, with the install settings pre-populated.

You can also choose to do a Manual Install (note the settings above) and then go into the Cloud Connector Management are in your instance.  Enter the settings as shown below.

CloudConnectorSetup.PNG

CloudConnectorManagement.png

 

 

  Enter the following information:

 

To configure the App, do the following:

    • Add a step to your marketing automation program at any point you would like to run the contact data normalizer connector on a Contact record.
      • Note: The Cloud Connector will run on any Contact that flows into that step, and return the result(s) to another field within the Contact record.
      • Make sure that you have an account on cloudconnectors.eloqua.com.
      • Drag a "Send to Cloud Connector" step onto the Canvas from the toolbar:

Canvas1.png

    • Double-click on the "Send to Cloud Connector" step, select Contact Data Normalizer from the list, and click on the configuration button.

Canvas2.png

    • When the Login screen appears, enter your cloudconnectors.eloqua.com credentials and click Log In.

CC_Login.png

    • Next the first setup screen for the App will appear.

LoginNew.png

    • The value for Step ID will automatically populate.  Select your Eloqua Credential, then click Go.

 

    • The Configuration page will then be displayed.

Config1.png

 

On the Configuration tab, enter the following information:

      • Description (optional):  Some text about this connector instance
      • First Normalization Set - Fifth Normalization Set: These are the maintained master lookup tables used to normalize your data.  You can select up to 5 sets, each to be used with the fields specified on the Mappings page.  Options are as follows:
        • Country to ISO 3 letter - Returns the 3 letter code for a given country
        • Country to ISO 2 letter - Returns the 2 letter code for a given country
        • Country to ISO Numeric - Returns the numeric code for a given country
        • Country to Internet domain - Finds the internet domain for a given country (for example, Canada would return .ca)
        • Title to Level - Returns a job Level for a given job Title.  See table below for some examples of normalized values:

ValueTable1.png

        • Title to Role - Returns a job Role for a given job Title.  See table below for some examples of normalized values:

ValueTable2.png

        • State (+ Country) to State - Returns the state for a given State and Country combination.
        • Country to World Region - Returns the World Region for a given country (NA, EMEA, APAC, LA)

 

    • Click Save Settings.

 

    • Next, click on the Mappings tab.

Mappings.png

On the Mappings tab, choose the following:

      • Email Address:  The field on the Contact record containing the email address.
      • First Normalization Set - Fifth Normalization Set:  The contact data that you wish to normalize, based on the Normalization Sets chosen on the Configuration page.

        • Lookup Field: The contact field containing the data you wish to normalize.
        • Return Field: The contact field to write the normalized data back to.
      • Click Save Settings.

 

You are now ready to Test the connector to make sure all is set correctly.  Click on the Test tab.

CC_Test1.png

Once your step is enabled and running, the Step Members testing tab will show you the counts of contacts in your step.

 

The Run Manually testing tab will allow you to perform a Dry Run or a Full Run of your step.

CC_Test2.png

A Dry Run will simulate a run, but will not actually write the data back to Eloqua.  A Full Run will perform a run of your connector, actually updating Eloqua.

 

Use the Sample Data tab if you wish to test your setup on select contacts.

CC_Test3.png

Enter their email addresses, one per line, and click Test Contacts. (these contacts must already exist in your instance).

       (Note: If you check the Full Run box, the data will be written to Eloqua, if left unchecked, it will simulate the connector and show you the results.)

 

To check the history of your step execution, click on the History tab.

HistTab.png

Now that you have tested your step, it's time to enable it.  Click on the Credentials tab.

CredsTabStepNew.png

 

When you are ready to enable your step, click the Enable Step button. (Note: Remember to also enable your program in Eloqua)

 

As Contacts flow into the step, the app will evaluate the data in the chosen contact fields (Lookup Fields) against the chosen Normalization Sets, and write the normalized value back into the contact fields selected as Return Fields.

Important: This Cloud Connector/Component will be decommissioned  after March 31st 2017. Please install the replacement app.

See HERE for instructions on how to install and use the Vidyard Cloud Component for Eloqua.

Important: This Cloud Connector/Component will be decommissioned  after March 31st 2017. Please review the App Replacement Cheatsheet for instructions

 

Colleague Scoring Cloud App

 

This post will describe the Colleague Scoring Cloud App, and how to use it within your instance of Eloqua.

 

With the Colleague Scoring Cloud App, you can now score a contact based on the activity of their colleagues at the same company.

 

In order to use the App, you must be registered at cloudconnectors.eloqua.com.  When creating your account, make sure the user whose Eloqua credentials you provide is added to the “API Users” security group to ensure it has API access.  Your Eloqua administrator will have to do this for you.

 

What is the difference between Appcloud.eloqua.com and Cloudconnectors.eloqua.com?

 

Colleague Scoring Cloud App Components

 

The Colleague Scoring Cloud App consists of the following Cloud Connector:

 

    • Colleague Scoring- allows you to score a contact based on the level of activity seen from their colleagues at the same company.

 

Components of the AppCloud

 

Installation and Configuration

 

To install the app in Eloqua, do the following.

 

Log into cloudconnectors.eloqua.com and click on the Apps menu.

ConnectorSelector.png

 

Click on Contact Data, then Colleague Scoring, and the following screen will appear:

InstallConnector.png

Click on Install Connector.  You'll then be shown the installation screen.

InstallConnectorDetails.png

If you are an Eloqua administrator, you can click on Add Connector, and it will take you to the Cloud Connector Management area in your instance, with the install settings pre-populated.

You can also choose to do a Manual Install (note the settings above) and then go into the Cloud Connector Management are in your instance.  Enter the settings as shown below.

 

CloudConnectorSetup.PNG

 

CloudConnectorManagement.png

 

  Enter the following information:

 

To configure the App, do the following:

    • Add a step to your marketing automation program at any point you would like to run the colleague scoring connector on a Contact record.
      • Note: The Cloud Connector will run on any Contact that flows into that step, and return the result to another field within the Contact record.
      • Make sure that you have an account on cloudconnectors.eloqua.com.
      • Drag a "Send to Cloud Connector" step onto the Canvas from the toolbar:

Canvas1.png

    • Double-click on the "Send to Cloud Connector" step, select Colleague Scoring from the list, and click on the configuration button.

Canvas2.png

 

    • When the Login screen appears, enter your cloudconnectors.eloqua.com credentials and click Log In.

CC_Login.png

    • Next the first setup screen for the App will appear.

CC_Config1.png

 

    • The values for Eloqua Client Name and Program Builder Step ID will automatically populate.  Enter the remaining information, then click Go.

 

    • The Configuration page will then be displayed.

Config.png

On the Configuration tab, enter the following information:

      • Description (optional):  Some text about this connector instance
      • Colleague Scoring Approach: This is the calculation that the app will perform on the contact scoring field (chosen in the next step) for all colleagues associated to the same company.  Options are shown below:

ConfigScoringApproach.png

      • Click Save Settings.

 

    • Next, click on the Mappings tab.

Mappings.png

On the Mappings tab, choose the following:

      • Contact Score Field:  The Contact field that holds score that you wish to use, along with the Colleague Scoring Approach, to calculate the score for colleagues at that company.
      • Company Score Field:  The Contact field to write the calculated company score back to.
      • Click Save Settings.

 

 

You are now ready to Test the connector to make sure all is set correctly.  Click on the Test tab.

CC_Test1.png

Once your step is enabled and running, the Step Members testing tab will show you the counts of contacts in your step.

 

The Run Manually testing tab will allow you to perform a Dry Run or a Full Run of your step.

CC_Test2.png

A Dry Run will simulate a run, but will not actually write the data back to Eloqua.  A Full Run will perform a run of your connector, actually updating Eloqua.

 

Use the Sample Data tab if you wish to test your setup on select contacts.

CC_Test3.png

Enter their email addresses, one per line, and click Test Contacts. (these contacts must already exist in your instance).

       (Note: If you check the Full Run box, the data will be written to Eloqua, if left unchecked, it will simulate the connector and show you the results.)

 

To check the history of your step execution, click on the History tab.

HistTab.png

Now that you have tested your step, it's time to enable it.  Click on the Credentials tab.

CredsTabStep.png

 

When you are ready to enable your step, click the Enable Step button. (Note: Remember to also enable your program in Eloqua)

 

As Contacts flow into the step, the app will evaluate all colleagues associated with the same company as the contact, perform the chosen scoring approach on the contact score field, and write the result back to the chosen company score field.

Filter Blog

By date: By tag: