amiando Cloud App
This article will describe the individual pieces of the amiando Cloud App, and how to use them within your instance of Eloqua.
In order to use the amiando Cloud App, you will need to have an amiando API Key (see here for information on how to get your API Key), an existing event set up in the amiando system, and must be registered at cloudconnectors.eloqua.com. When creating your account on cloudconnectors.eloqua.com, 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.
amiando Cloud App Components
The amiando App consists of the following:
- amiando Widgets - this Cloud Component allows you to embed event-related widgets into an E10 landing page. The following widgets are available:
- Registration Form/Ticket Shop
- Participant List
- My Events
- amiando Feeder - allows you to pull into an Eloqua group, all the people who registered for or attended your amiando event.
Installing and Configuring the Cloud App
The amiando Widgets are already available for use in E10, but may need to be enabled. See here for more information.
A Cloud Component is inserted into a landing page via drag and drop within the landing page editor.
From the editor toolbar, select the "Cloud Components" button. A select box containing all of the available Cloud Components will then display.
Drag and Drop the amiando Widgets component onto a landing page:
Next, save the page, then double-click the icon for the component that you just dropped onto the page. The following screen will appear:
Enter your cloudconnectors.eloqua.com credentials and log in. The configuration screen for amiando Widgets will then be displayed:
On the configuration page, do the following:
- Enter the Admin Email Address (your email address) and your amiando API Key.
- Click “Save Settings”, and a list of your amiando events will show in the Event drop-down list.
- Select an Event, and then choose a Widget Type that you would like to display on the landing page.
- Select the other optional settings to customize the Widget to the needs of your landing page, and click “Save Settings”. You can now close the configuration page.
Now, render the landing page, and you will see your amiando Widget on the page where you placed it.
- The amiando Feeder does not require installation, as it is a standalone application that runs outside of Eloqua, and connects to your instance.
- In order to successfully configure the feeder, you must first do the following:
- Make sure that the Eloqua user account that is being used for the feeder had Eloqua API access.
- Create a Contact Group in Eloqua (called a Contact 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 in Eloqua, to store the Event information returned by the feeder. For more information about creating a DataCard Sets, please search the knowledge base for an article named "Database Management".
- To access and configure the feeder, first visit cloudconnectors.eloqua.com and log in. Once logged in, select Products...Feeder, and choose "amiando Feeder”.
Click New Step on the screen that appears:
The configuration screen will then appear:
Enter your Eloqua Client Name, Query Frequency (how often the feeder should run), Eloqua User Name (make sure the user has API permissions), Password, and Admin Email Address. Click Go.
On the Configuration tab, provide a description for the feeder (optional) enter your amiando API Key, and choose your Event. Next, choose the existing Contact Group (E9) or Contact List (E10), and Custom Data Object where your new contacts will be stored in Eloqua.
On the Fields Mappings tab, choose which Eloqua Contact and Custom Data Object fields to map to corresponding data from the amiando system into when the feeder runs. For the Custom Data Object, the field list selections will be populated based on the existing Custom Data Object chosen on the Configuration tab.
On the Run Step tab you can test the feeder. You can choose between a “Dry Run” (no data will be changed in Eloqua) and a “Full Run” (The data will write to Eloqua – this is effectively a manual run of the feeder).
Once all is configured, all that is left to do is switch back to the Credentials tab and Enable the feeder:
Now that the amiando feeder is configured and enabled, leads will begin to flow into Eloqua based on your Events.