We are trying to achieve the Eloqua and Adobe Target Integration. Could some one please provide your inputs if some one has done this integration? We need to use those Eloqua segments imported into target as an audience and provide the personalized experience based on those eloqua segments.
I was looking into the documentation related to the data providers. Is this the right approach for making the call to eloqua with in the at.js window.targetGlobalSettings.dataProviders and send it as parameters in a Target request to target those eloqua segments to provide the personalized experience?
Yes, Data Providers approach would work fine when integrating Target with 3rd party. Here you would make an Eloqua API call with some parameters to fetch appropriate segments. The segments returned (based on the visitor) could be set as profile parameters so that those are just set once and used in subsequent target requests in the same session. Then create relevant audiences in Target based on these profile parameters, to be used in the activities.
Thank you for @shelly-goel for your response. Really appreciate that!
Couple of follow up questions:
1. To make that call from the at.js data provider, eloqua parameters should be available either through the data layer or some cookie on that page already right.
2. Another approach listed for Eloqua integration.
Eloqua visitor ID and can be integrated with ECID using the visitor service. At this point, any and all (non-PII) data can be sent to Adobe Target by way of APIs using nothing more than the Eloqua ID.
Only thing thats confusing in the second approach is if the customers are already mapped using this customer id or crmid to ECID using the visitor service for authenticated state and the offline CRM attributes, can they also map the eloqua visitor id too using the same approach or they are limited to map only one id using that approach.
Any pointers would be appreciated.