Eloqua — Export to Custom Data Object

The Oracle Marketing Cloud: Eloqua integration can now export Lytics profile data and audience membership to an Eloqua Custom Data Object (CDO). Unlike the existing audience export, which writes to a contact list, this job populates a dedicated object — so Lytics-computed data like scores, attributes, and audience flags stays off the master contact record while still being usable in Eloqua's campaign canvas, dynamic content, and reporting.

What you can do

• Land Lytics profile fields and audience membership in a dedicated Eloqua object, keeping computed data separate from your master contacts.
• Target and personalize on Lytics data directly in Eloqua — campaign canvas, dynamic content, and reports can read the CDO.
• Keep records current automatically: one upserted record per contact, with membership fields flipping true/false as contacts enter and exit each audience.

How it works

• Runs server-side over the Eloqua REST API, batching every 5 minutes (or sooner when more than 1,000 records are pending).
• Reuses your existing Eloqua authorization — no new credentials to set up.
• Creates a lytics_{audience_slug} membership field on the object for each selected audience automatically. Create the Custom Data Object in Eloqua first; Lytics populates it and adds the membership fields, but doesn't create the object itself.

See Oracle Marketing Cloud: Eloqua for the full field mapping and configuration steps.