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


What is the difference between and


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 and log in.


Once logged in, click on the Apps menu.



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


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


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


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


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


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


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


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


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