Have you heard the terms 'CDO' or 'data cards' mentioned here on Topliners and wondered whether they might be useful to you? Custom data objects (CDOs) allow you to store additional information for your contacts, such as product purchase history or event attendance data, without cluttering up contact records. This helps to keep your database clean and organized, and it provides you the opportunity to store data with which you can segment your contacts, build out more sophisticated lead scoring or send follow-up event communications.
This post compiles the most viewed Topliners posts on the topic of CDOs, so that you can quickly read up on the topic or learn about new ways to leverage this functionality in Eloqua.
Data card definitions, benefits and uses
Explains the concept and provides some common use cases. Be sure to check out the analogy in the first comment, too!
Provides definitions, multiple use cases, recommendations about the number of records to use with CDOs, and links to resources
Provides basic procedural information
Describes how to use the Data Card Evaluator app to write a value from a CDO to the contact record based on criteria you choose
How to import data from standard CRMs
How to import data from sources other than standard CRMs
Information for developers using the Eloqua API