Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn more

View all

Sign in to view all badges

SOLVED

Oracle Eloqua and Adobe Target Integration

cqexplorer
Level 2
Level 2

Hi Team,

 

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?

 

https://experienceleague.adobe.com/docs/target/using/implement-target/client-side/functions-overview...

 

Thanks!

Adobe Target Oracle Eloqua
1 Accepted Solution
shelly-goel
Correct answer by
Community Advisor
Community Advisor

Hi @cqexplorer

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.

Thanks

View solution in original post

4 Replies
shelly-goel
Correct answer by
Community Advisor
Community Advisor

Hi @cqexplorer

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.

Thanks

View solution in original post

cqexplorer
Level 2
Level 2
 
 

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.

Thanks

shelly-goel
Community Advisor
Community Advisor

@cqexplorer

1. Yes, that's right or any other way to get/ generate those values in the javascript code of data provider

2. Yes there's a possibility to use Experience Cloud ID service if you have the Experience Cloud provisioned for your organization. You can set multiple IDs for a visitor leveraging setCustomerIDs in ID Service (visitorAPI).

There are a couple of ways to make profile data available in Target: Bulk Profile Update API or Customer Attributes (You can compare which one works in your use case: https://experienceleague.adobe.com/docs/target/using/implement-target/before-implement/methods/metho...).

Then use crx.<attribute name> (Under Visitor Profile) while creating Audiences in Target.

Other References:

https://experienceleague.adobe.com/docs/id-service/using/reference/authenticated-state.html?lang=en#...

https://experienceleague.adobe.com/docs/core-services/interface/customer-attributes/attributes.html?...