BETA - Please be aware that this feature is currently in beta mode
The following is a guideline to follow when using the recipe "List Load for Eloqua". Please read these guidelines before cloning the recipe.
This project uses Openprise's App Factory List Load app. We recommend you review the following video on building a list loading app before cloning this recipe.
This recipe provides the following:
- Jobs that process a list and load the records into Eloqua.
- An App Factory app to submit lists for loading.
- An App Factory app to review the list load results.
- A bot to run the above jobs using the App Factory application.
The assumption is that your Eloqua objects are being imported on a regular basis by pre-existing bots.
This recipe does not support adding the list members to a campaign.
- Create a spreadsheet in Google drive for the template for the lists to be loaded. This spreadsheet will define the attributes for the list to be loaded by the list load app. Please use the exact column names shown below.
Column name Openprise data type Added as New Lead text, single value Address text, single value Status text, single value City text, single value Company text, single value Country text, single value Email Address text, single value First Name text, single value First Responded Time text, single value Job Title text, single value Last Name text, single value LinkedIn Profile URL text, single value No. of Employees text, single value Phone Number text, single value Postal Code text, single value Rejected text, single value State text, single value Transaction ID text, single value Uploaded By text, single value Upload Time date Website URL text, single value
- Add one record to the template by adding a sample email (ie. firstname.lastname@example.org). You can leave all other values in the spreadsheet blank.
- Create a data source named from the above spreadsheet. When creating the data source:
- The Data source name should be List Load Template.
- The source technology and data format for the data source should be Google Drive - Sheets.
- On the Map screen (during data source creation), change the data type for the attribute Upload Time to the Date data type.
- All other fields can be left as the default data type of Text, single value.
- Two additional columns will be added when the data source is created: OPFileNames and OPAutoDate. These attributes should remain in the data source.
- Import the above data source. You should end up with a data source that has one record in it with the junk email. This data source is only used to define the columns expected for processing by the list load app.
- Create a data source for the Eloqua Contact object with at least the following attributes. Note: If these data sources are already created, please verify that the following attributes are defined in the data sources.
Contact id city accountName Country emailAddress firstName lastName businessPhone Zip or Postal Code State or Province Address 1 title Website
- Create a new data target: Create a new data target for Contacts with the attributes listed in the above table.
To clone the project recipe, navigate to Projects > Recipes and select the project recipe to clone.
You will need to provide:
- Project name
- Prefix and/or suffix for all objects in the project
- Data source to be used in the project
- Data target to be used in the project
Examine the cloned project
We recommend you look through all the newly created project elements to familiarize yourself with what has been created.
- Any job that is marked with errors. These errors must be manually corrected.
- Export tasks that write back to Eloqua. Make changes by selecting any values that you want to write back to Eloqua. Note: Any Export task to Eloqua has been bypassed for your protection. We recommend that you run the jobs with the bypass enabled so you can review any data changes before writing data back to Eloqua.
- Review logic in the jobs to validate that it meets your requirements for cleaning the incoming list data and matching it to any existing contact and account.
- Review logic in the job that rejects a list record due to missing data. By default, these jobs will only reject records with a missing email address or a duplicate record identified by a duplicate email address.
- Please note that these jobs are built with the assumption that you have a separate, active process to handle duplicate records in Eloqua. If you have duplicate records in your instance, you'll need to change the job Eloqua_List02 - Match to existing to properly handle the case when a list record matches multiple contacts.
- Check that you have an automated bot that imports Contacts on a frequent basis, so if a list is loaded twice in close succession, duplicate records are not created in Eloqua.
Test the App
When you're ready to test, change any export task that is bypassed to allow updates. Then, prepare a series of sample lists to test the list load app. It is suggested you test each use case separately for ease of diagnosing errors, and only include a few records in each test. Results should be verified in both the App and in Eloqua directly.
For example, test the following use cases:
- A list of records missing an email address. (These should all be rejected).
- A list of records that match existing contacts in Eloqua. Select emails for records that can be updated without affecting other processes (eg. test contacts).
- A list of net new records.
To run each test:
- Launch the App Portal and locate the List Load application.
- Run the application.
- Load a test list into the UI and optionally remap any columns needed. This is only needed if your list has different column names from the file spreadsheet used to create your initial data source.
- Select the "Load with Mapping" button after the list has been dropped into the app.
- Let the app process the list and check the outputs using the List Load Review app.
- Check the results using Eloqua directly by looking up the records that should have been updated and/or added.
- Repeat for each test.