Tired of building Contact status checks into every step of your Nurture Campaigns? Now, you can remove Contacts from some or all Campaigns based on the criteria identified. For example, if you have a Contact in several Nurture Campaigns and submit a form, you can remove them instantly from any other campaigns! Or, you have a business rule that says when a Contact becomes a customer, they should be removed from Nurture Campaigns. Now you can do that for all Nurture Campaigns from one process.
Ever want to automatically create or update a CDO for an event, or for purchase information under Campaign Canvas or Program Builder control? Now, you can!
Also known as our “CDO Updater”, this Cloud Action uses parameters you set, to determine the name and fields mapped to your CDO. Now, you can automatically use Eloqua to store transactional information, like purchase history, multiple products of interest, webinar attendance, all as part of your normal campaign processes.
Tired of seeing “ASDF”? Both bots and people tend to use the same strings over and over when putting junk data into your forms. Now, you can detect and address large quantities of junk entries easily or deal with it as it comes in.
Automatically compare the values of the name fields with a customizable list of text strings to determine if the entry is garbage. If invalid text is found, this Cloud Action will enable you to eliminate, data-score, or flag those entries for correction.
There are many fields that are clearly garbage if they are too short. Phone numbers, Campaign IDs, and Salesforce IDs also all have a minimum required lengths and even company names really shouldn’t be shorter than 2-3 characters.
Use this Cloud Action to compare the length of the value of a field with a pre-determined value. If it’s too short, flag/route/score the problem appropriately!
Delete custom data objects in an automated way when you run this Cloud Action with Program Builder. For example, get rid of all CDO records created within the last hour in the case of a bad data upload. Or maybe you’d like to delete all CDOs older than a year! Perhaps you want to create CDOs for a short term need, and then want to remove them after the function has completed.
Bad company names show up prominently on internal reports and lists. Now, you can detect and address them before they flow into your main database.
Like the Garbage Name Cloud Action, you can compare the values of the company field with a list of known garbage text strings to determine if the field is bad. If any of the text strings are found in the value of the field (“qwerty”, for example), you can decrease its datascore, delete it, or route it for manual processing.
This Cloud Action compares two Eloqua fields and determines if they have equal values – which may be evidence that someone is copying and pasting nonsense text to get past your forms! Also use it to avoid robots that submit the same value in multiple form fields.
Beyond Data Quality, this functionality is also useful in an integration, to compare a temporary campaign ID to the original campaign ID. If they are the same, you can determine whether anything had changed on the contact. There are a variety of uses for this Cloud Action!
Deleting Contacts by hand is time-consuming! Now, you can delete old contacts, garbage Contacts, or just because you want to reduce database size, all under automatic Campaign Canvas or Program Builder control.
This Cloud Action is useful if your forms tend to be abused by robots or others. Use it in combination with our other Cloud Actions to create business rules to move bad data out of your system automatically!
Create a third field from the value in any two contact fields. For example, combine the Firstname, space, and Lastname fields to create a Fullname field, perhaps so that your CRM system can have a company name. Or create a multiselect field from several single selects.
This Cloud Action will determine if the phone number in the specified field matches the standard US/Canada phone format. If so, it will format the number as (AAA) PPP-NNNN.
Check to see if the value of one field (e.g. Firstname) is wholly contained in a second field (e.g. Company).