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