Most people don’t actively manage their data until they have problems, especially in the Custom Data Object (CDO) area. This article describes how to get ahead of the curve with CDOs and proactively manage your old and unneeded CDO data.
You’re Up Against Eloqua’s Limit –Reason #1
This of course, is the ultimate reason. The limit for CDOs is very high, but it may not necessarily be out of your reach:
- The system limit on the total number of custom object records is 25 million across all custom objects.
- A single custom object should have no more than 5 million custom object records.
(Source: Eloqua Product Manager on Topliners)
True, this seems like a lot of records, but if you have a million contacts, and are a .com company pulling in eCommerce, or a large B2B company pulling in Data Warehouse data, this space can be used very quickly. We’ve run across a variety of other reasons as well. For example, a medium size B2B software company with a decade of product download history can burn through these quantities.
Getting rid of those old record records by hand can be a completely unrealistic task and what’s more, not a task that anyone would want to do every week or month.
Speed –Reason #2
We had a customer that got a huge number of inquiries every day and tracked them via CDOs so that multiple inquiries against a single contact could be measured. They also defined inquiries very loosely so that many web page visits also became CDO records. This combined with thir huge quantity of inquiry flow caused reports and dashboards to slow down after awhile.
A quick bit of analysis revealed that certain types of records didn’t need to be kept more than 24 hours and others didn’t need to be kept more than a month. Feeding these records into our CDO Deleter Cloud Connector solved the problem on a perpetual basis with no human interaction.
Improved Reporting –Reason #3
When you run a report and the valuable data you need is all mixed up with the old and junk data… you have the perfect reason to clean up your CDO system. Of course understanding what you’re reporting on, and how to separate the junk from the gold sometimes takes some thinking, but it can be done.
Bonus Reasons #4, #5, and #6!
There are other reasons too. Often old project/architectures will leave a trail of CDO structures and data that simply make your Eloqua life more complex than it should be. Sometimes testing a new system results in a bunch of CDOs that would be a real pain to manually delete. And sometimes you just want a clean ship… if you’re done with a CDO, why leave it around?
Is It Safe?
Whenever you’re deleting something programmatically you should double or triple your testing efforts to make absolutely sure Eloqua is doing what you want. It IS very easy to create a filter or a program flow incorrectly and while the 4Thought Marketing CDO Deleter does give you a manual path of recovery, it’s not fun.