Removing Assets from Eloqua – Recommendations #
Key features for Asset Dependency Manager #
- Identify or View dependencies of Eloqua Assets
- Export dependencies report of Eloqua Assets
- Remove dependencies from Eloqua Assets
- Replace dependencies from an Eloqua Asset to another
- Deleting Assets by clearing out the dependencies
- Cruise Control for clearing or deleting dependencies
Best Practices and Recommendations #
This section provides recommendations on how to proceed with cleaning up your Eloqua instance by considering the types of dependencies that the Eloqua assets can possess and the complexity of clearing out the dependencies.
As a framework to remove dependencies so that assets can be deleted from your Eloqua instance, dependencies get removed by dependent asset type. For example, if you remove dependencies for Contact Fields, these dependencies can exist in Segments, Contact Views, Campaigns, BULK Import/Export definitions, etc. The table below recommends that you remove the dependencies of Contact Fields from Bulk Import/Export definitions, then Contact Views, then Segments/Shared Filters, etc.
| Execution Order | Asset Type To Remove From Eloqua | Asset Type To Remove Dependencies From | Recommendation Reasons |
|---|---|---|---|
| 1 | Programs | Form Processing Steps Programs Campaigns | In an Eloqua instance Programs have the least types of dependencies. They usually appear in Form Processing Steps, Programs, and other Campaigns. Having the least type of dependencies makes it easier to remove dependencies. Dependencies in Campaigns should be the last type to be cleared because of challenges with processing completed Campaigns. |
| 2 | Campaigns | Form Processing Steps Programs Campaigns | In an Eloqua instance, Campaigns have the least types of dependencies. They usually appear in Segments, Form Processing Steps, Programs, and other Campaigns. Having the least type of dependencies makes it easier to remove dependencies. Dependencies in Campaigns should be the last type to be cleared because of challenges with processing completed Campaigns. |
| 3 | Contact Segments | Programs Campaigns | It is likely that an Eloqua instance will have Segments that are usually not used in other assets such as Campaigns and Programs. These asset types can grow over time and are a good qualifier to be removed. Dependencies in Campaigns should be the last type to be cleared because of challenges with processing completed Campaigns. |
| 4 | Shared Filters | Contact Segments Programs Campaigns | Dependencies in Campaigns should be the last type to be cleared because of challenges with processing completed Campaigns. |
| 5 | Emails | Forms Segments Campaigns | The order for removing Email dependencies is based on the path of least resistance. Updating Forms to remove Email dependencies is least likely to run into any validation rules. Dependencies in Campaigns should be the last type to be cleared because of challenges with processing completed Campaigns. |
| 6 | Forms | Segments Shared Filters Landing Pages Campaigns | Dependencies in Campaigns should be the last type to be cleared because of challenges with processing completed Campaigns. |
| 7 | Landing Pages | Forms Segments Shared Filters Programs Campaigns | The order for removing Landing Page dependencies is based on the path of least resistance. Updating Forms to remove Landing Page dependencies is least likely to run into any validation rules. Dependencies in Campaigns should be the last type to be cleared because of challenges with processing completed Campaigns. |
| 8 | Contact Fields | Bulk Imports / Exports | An Eloqua instance will have the highest number of dependencies for Contact Fields and should be the last asset type to be cleared. For clearing dependencies for Contact Fields portQii has found that Bulk Import/Export definitions take up over 70% of the dependencies. The order of operation here follows the path of least resistance thought process. Dependencies in Campaigns should be the last type to be cleared because of challenge with processing completed Campaigns. |
| 9 | Pick Lists | Segment Contact Field | Recommended Reasons: Most of the dependencies should have been deleted if the recommended execution order is followed |
Identification criteria for assets to be removed from Oracle Eloqua #
The below outlines the benchmark recommendations based on Oracle Eloqua data retention policy. However, this recommendation should be evaluated for each instance to ensure that it does not have a negative impact to the use of an Oracle Eloqua’s specific instance.
Campaigns #
| Qualification Analysis * Completed campaigns with an end date of more than 25 months * Campaigns with no responses |
| How To Execute a Campaign Analysis report ensuring that the Eloqua Campaign ID and Campaign Name are exported from Insight. Use the CSV export to create packages within Asset Dependency Manager. Refer to the following images: Screenshot 1:  Screenshot 2:  Enter the following Expression in the Expression text box: TIMESTAMPADD(SQL_TSI_MONTH, -25, CURRENT_DATE) |
Contact Segments #
Emails #
Forms #
Landing Pages #
| Qualification Analysis * No page visits with the last 25 months (Primary Condition) * Only included in Campaigns older than 25 months * Only included in Emails older than 25 months |
| How To Extract a list of all landing page assets (through PortQii Workbench). Exclude all returned landing-pages in the below Insight report from the list returned from PortQii Workbench NOTE: PortQii Workbench is a free application that is capable of extracting a full list of assets from an Eloqua instance.  |
Picklist #
| Qualification Analysis * Picklists with no dependencies in Eloqua |
| How To Extract list of Picklist using PortQii Workbench. Use the list to run a custom script that calls the dependencies endpoint for each Picklist ID returned to check if dependencies exist for that Picklist. NOTE: PortQii Workbench is a free application that is capable of extracting a full list of assets from an Eloqua instance. |
