When using the Leadspace for Eloqua integration, there are several best practices that should be followed for maximum success with the Leadspace Enrichment cloud application. This article highlights some Leadspace recommended best practices and answers to frequently asked questions.
Best Practices
Throughout this section, there are several hyperlinks to valuable KB articles that your team can bookmark and review as needed. This is the material that Leadspace leans on while discussing the Eloqua Integration with your team.
Refer to the Integration Guide: It is recommended that Eloqua Admins familiarize themselves with the Eloqua Integration Tutorial when using the app. This provides a good foundation of how the application works which gives context on the following information.
Eloqua User Registration: Leadspace must provision each user that is going to be using the Leadspace for Eloqua enrichment integration. If an unregistered user logs in to Eloqua and tries to work with the Leadspace Enrichment cloud app, the canvases will fail. Therefore, please make sure that all users that will be interacting with the app are added on the Leadspace side.
- Create a Support Ticket and provide first, last, email, and Eloqua user ID for all users
- Follow the instructions in the registration email that Support sends out once the user is added. Users have 24 hours to register after the email is sent
Ensure Users are Actively Using the App: If an Eloqua user is registered to the app but is inactive for a year, that user will expire. Leadspace receives notifications in advance of a user expiration and will work to notify the customer before the expiration. However, if you notice that records are getting 'stuck' in the Leadspace Enrichment app on the canvas, it may be that the user has expired. If you believe this to be the issue, please create a Support Ticket so Leadspace can review and assist.
Notify Leadspace of Changes to Contact Object: Leadspace maintains an input and output field mapping .csv file for your Eloqua integration. This governs both the field data you send to Leadspace for enrichment (input data) and the data Leadspace sends back to Eloqua (output data). If any of the input fields we have in the .csv file are mapped incorrectly or removed by the customer, the integration will fail. Therefore, it's important that Leadspace is notified when changes are made to Contact fields in Eloqua.
Here's some more information on this:
- Leadspace has automated alerts that go to Support and DevOps when there's an input mapping conflict in the system. We will do our best to notify customers proactively when this occurs.
- When the Leadspace Enrichment app is moved to a canvas, it automatically calls the input/output field mapping endpoint to verify that the input fields are accounted for. If you get an error while trying to add the cloud app, it may be caused by an input mapping issue.
- Contact Leadspace Support or your CSM if you make any changes to contact fields. We will review your mapping and provide you with next steps to get the app back up and running.
- Refer to the Eloqua Integration Tutorial article for more information on the mapping process.
Notify Leadspace of Changes to CDO Fields: It is best practice to make sure that your CDO fields (output fields) are aligned with the mapping file for your integration. While a mismatch or missing CDO field will not cause the integration to fail as it will when an input field is mis mapped or missing, it's still good hygiene to audit your fields regularly for the following reasons:
- To make sure that you are receiving data for the fields that are critical to the operationalization of the enriched data you are getting from Leadspace.
- To make sure you are aware of any new fields Leadspace is offering that may be of interest
- To make sure you are not spending resources capturing data for fields that are not important to your use case
Leadspace Support is happy to setup a call with your team to go over your output field mapping at any time. Please Submit a Ticket with any questions.
Deactivate, Remove & Re-add the Leadspace Enrichment App: This is a pre-cursor to the next step which is to uninstall/reinstall the Leadspace Enrichment app. However, this is a good step to try first before proceeding with the next step.
As mentioned above in the "Changes to Contact Object" information, the field mapping service is called whenever the cloud app is dragged/dropped into a canvas. Therefore, if there are updates to your mapping, this process can be used to re-activate the canvas. You can follow the Eloqua: Leadspace Enrichment Cloud Action Reset article for the steps:
- Move records out of the Leadspace Enrichment and/or 'Wait' steps in the canvases
- Deactivate all Eloqua canvases that are using the Leadspace Enrichment app
- Remove the Leadspace Enrichment app from the canvas
- Re-add the Leadspace Enrichmet app to the canvas by dragging & dropping
- Save and activate the canvas and run records through
Refresh the Leadspace Enrichment App: One of the most common troubleshooting techniques for the Leadspace for Eloqua integration is to uninstall and reinstall the Leadspace Enrichment cloud app. If certain changes are made; especially when users are added/refreshed, it is a required step to make sure your Eloqua canvases continue to send records to Leadspace for enrichment. Customers can follow the Refresh Eloqua Application article for instructions.
Here's a list of things that may require the app to be uninstalled and reinstalled:
- Leadspace adds new Eloqua users to the integration
- Eloqua users expire and are re-added and re-registered by Leadspace
- General troubleshooting as instructed by Leadspace
Contact Oracle: The Leadspace Enrichment app is a cloud app, which is affected by many things including Leadspace and Oracle infrastructure. Each Eloqua environment is different, with different resource burdens and API traffic, so contacting Oracle support directly is never a bad idea. Most of the issues you will encounter with the Leadspace for Eloqua integration can be solved by following the above and working with Leadspace Support, but there are occasions when the issue needs to be reviewed by the Oracle team as well. It never hurts to have both Leadspace and Oracle looking into Eloqua issues at the same time for visibility and coverage.
FAQs
| Question | Answer |
| What kind of canvas can I use for Leadspace Enrichment? |
You can use either a program or campaign canvas when using the Leadspace Enrichment Cloud App. Program is recommended for inbound enrichment while Campaign is typically used for one-off use cases. |
| What services does the Leadspace for Eloqua integration provide? |
The integration is used for enrichment only, and can be used in a myriad of ways.
Here is a list of helpful articles that outline these flows: |
| How many records can I send to Leadspace at one time? |
The Leadspace recommendation is no more than 200K per day, but can vary based on resources and traffic in an individual instance. Please contact your CSM or Submit a Support Ticket before sending any bulk over 100K records. |
| Does the integration use Single or Bulk API? |
Leadspace for Eloqua integration uses our bulk API to process records. We receive the bulk, process, enrich, then 'handle' by sending the data back to Eloqua to populate the fields in your mapping file. |
| To which object does Leadspace write the data? |
Leadspace works with 3 objects in your Eloqua instance:
Note that Leadspace cannot push data to your custom objects, only the ones above. And while we can push Leadspace Enriched data to the Contact object, it is not recommended. We recommend to push data to a CDO and then each customer makes an internal decision on what to do with it from there. |
Related Articles
For more helpful articles along with the aforementioned, please visit https://support.leadspace.com and search for 'Eloqua'. Here's a shortcut to the search results for all of our articles on our Support page: