Eloqua Data Dictionary Field Guide
UT Austin DEV metadata repository to help define data fields utilized in Eloqua.

Eloqua records are only updated with VIP data in the following scenarios:
> A valid active preferred email address must exist in VIP.
> The constituent must be an individual (i.e., company, foundations, etc. are not sync'd to Eloqua automatically).
> The constituent must be living.
> The constituent's email address must be unique (i.e., if an email address is associated with more than one record in VIP, the associate VIP data may not be updated in Eloqua as Eloqua considers the email address as the unique identifier.

Helpful Links:
> UT Austin Department System: https://utdirect.utexas.edu/dept/index.WBX

  • Picklist Values sheet can be used when the "Accepted Values" column references "Valid values are defined by the Picklist/Quicklist."
  • Picklist Values (PDF)




  • Note -- Only Activity/Involvement Codes marked as iModules/Email Sync as "Yes" in VIP are loaded from VIP to Eloqua.
Example seen here:



  • UT Austin Department System: https://utdirect.utexas.edu/dept/index.WBX
  • Notes regarding Gift data:
  • Gift data stored in Eloqua must have either a hard credit amount or soft credit amount
  • The CSU is not "DO" or "EX"
  • Gifts must have been made within the last 10 fiscal years
  • The gift status must be "GF" (gift finished) in order to be included.