Discussions

Product Notice: Eloqua Bulk API form submit activity exports – Update to linked Contacts [May 2022]

JodyMooney-Oracle
JodyMooney-Oracle Product Management, EloquaPosts: 394 Employee
edited Mar 17, 2022 7:53PM in Developer Tools

Overview

With the arrival of Eloqua release 22B (May 2022), we are modifying how Contacts are linked to Bulk API form submit activities, by first checking for the Contact Id that was set upon form submission then if there is not a Contact Id set upon form submission, checking for a Contact that’s mapped to the Visitor.

 

What’s changing?

Currently the Bulk API form submit activities set linked Contact information by looking at the Contact mapped to the Visitor record, if there is a Visitor record with a mapped Contact linked to the form submit. If there is not a Visitor record, or the Visitor record is not mapped to a Contact, then the Bulk API will use the Contact Id that was set upon form submission. This behavior differs from how the Application API and Insight link Contact information to form submissions.

 

With Eloqua 22B, we are modifying how Contacts are linked to Bulk API form submit activities to match the Application API and Insight, by first checking for the Contact Id that was set upon form submission then if there is not a Contact Id set upon form submission, checking for a Contact that’s mapped to the Visitor.

 

Note: This update only impact Bulk API form submit activity exports

 

Timeline

With the arrival of Eloqua release 22B (May 2022), we are modifying how Contacts are linked to Bulk API form submit activities, by first checking for the Contact Id that was set upon form submission then if there is not a Contact Id set upon form submission, checking for a Contact that’s mapped to the Visitor. Check the Eloqua Release Center for specific dates and times.

 

Next Steps

If retrieving form submit activities with linked Contact information via the Bulk API, prepare for Contact information to be set by first checking for the Contact Id that was set upon form submission then if there is not a Contact Id set upon form submission, checking for a Contact that’s mapped to the Visitor.

 

Additional Resources

View changes for Eloqua's APIs including, new features, significant recent changes, and platform notices, on the Eloqua Developer Changelog.

If you have questions, post a discussion on Developer Tools!

 

FAQ

 

Q: What Bulk API exports are impacted by this change?

A: Only Bulk API form submit activity exports are impacted.

 

Q: Why is this behavior being changed?

A: This behavior is being changed to be consistent with how the Application API and Insight link Contact information to form submissions.

 

Q: What happens if the Visitor is linked to a Contact different than the Contact Id set upon form submission? 

A: The Contact that was set upon form submission is used.

 

Q: What happens if the Visitor is linked to a different Contact after submission and there is no Contact Id set upon form submission? 

A: If the Visitor is mapped to different Contact later on then the most recent Contact information is exported, i.e. the Contact currently mapped to the Visitor is exported.

Group Product Manager, CX - Marketing: Eloqua