Skip navigation

Some weeks ago, one of our reporting teams needed to have an Eloqua Form submission report to be sent out every month containing the last month's worth of submission data. For people who use Insight Reporting on a daily basis, it’s very common to choose a time span date filter instead of a date range filter when running a report (e.g. Last 7 days). But what happens when you want to schedule that report for a distribution list to receive it containing the last month worth of data? Since it’s a scheduled report, there is no prompt option to select the date range, and usually when configuring a fixed filter on a report, the filter automatically gives you the option to use a range instead of a span. So, how do you do it? If you took the Insight for Analyzers course and have an Analyzer license, this solution will work for you.


When creating a date filter on an Insight report, these are the options that you usually see -- options to specify an exact date value for the report.


In our case, we want a time span instead of a date range or value, and to configure it we need to click the calendar icon beside the date box.


As you can see, bellow the calendar, there is an option that says, “Switch to dynamic date.” After clicking this option, you will be prompted to configure the dynamic date.


In this screen, you can specify the dates you are interested in, using simple math. For example, if you want to include the last 7 days of data, on this screen you will select Today “minus” “7” Day(s). After that you will notice that below there is a “Preview” box where you can see to which day the configuration will resolve to. Once you click OK, you will notice the “resolved” date appearing in the date box.


Now, it’s just a matter of changing the operator that validates this “resolved” date from “Equals” to “Greater Than or equal to” to obtain the last 7 days of data. After clicking OK, you will see something like this:


So now, every time you run this report it will check today's date, subtract seven days from it, and bring you back any record that has a date equal to or greater than the 7 day subtracted date.

Now, it’s just a matter of saving the report and configuring a schedule to send it every Monday. Now each Monday, you will get a report on the inbox of all the specified emails with a report containing the data of the last seven days automatically.


As you saw in the previous screenshots, this tool gives you different configuration options, so you can do different date spans using hours, days, weeks, months and years. This allows you to build more complex date spans. For example, if we want to send a report every month containing the data of the last full month, assuming that today’s date is September 29, we’d like the filter to bring data from August 1st to August 31st.


Such report configuration should look something like this:


So as you can notice, the report will provide you a resolved date for you to verify the span works as expected using today’s date, so this will dynamically change as time goes by.


In conclusion, by configuring this kind of dynamic date filters, we can save a lot of time running a report periodically and just programming it to be delivered continuously to a set of email addresses without worrying about including an excessive amount of data. Before using this approach, we had the business stakeholders go into Insight and run a report each week or month to pull the data they needed. Now they receive this report automatically in their inbox without the need to filter the dates in Insight or Excel. This is advantageous not only because of the time saved filtering the report dates, but also by being able to restrict Insight access to users that just needed to pull a periodical report, therefore putting less stress on the Insight’s server and having a better control of the User’s access level.


In order to learn how to properly use Insight and obtain the maximum advantage from this solution, I recommend you take the following Eloqua courses found in the Oracle Marketing Cloud Academy:

  • Insight for Reporters
  • Working with insight Reports
  • Customizing and Sharing Insight Reports
  • Insight for Analyzers

Our goal was to provide our sales staff the ability to add their prospects into custom nurture paths based on a variety of reasons – whether the lead is active but needs some extra nurturing or the lead is recycled and needs to go down a specific RTM path. Sure, we have other nurture campaigns and can create segments by filtering off Recycle Reasons, but this campaign gave us more flexibility into creating custom emails curated by marketing, sent by Eloqua (not Outlook), and delivered on desired timeframes.


We broke up the campaign into the following areas:


  • Defining success: There are two aspects to this. One, Sales adoption. Two, metrics. We were originally aiming for an easy 10% open rate and 1% CTR for our RTM emails.
  • Develop email content: We worked closely with both sales and our content team to come up with relative email copy and supplemental supporting assets.
  • Salesforce/CRM build: We created a custom field on the Lead Object in SFDC called “Email Nurture Campaign”.
  • Eloqua Campaign flow: Created the campaign flow, determined wait periods, and all assets involved.
  • ABT: Always Be Testing. We focused mainly on subject lines here.
  • Report: Identified key stakeholders and measure success.


Here is a detailed look at the steps we took to implement our sales-triggered nurture campaign:


  1. Determine how many and what tracks you want to create. We started off with only a couple to make it easy on both Marketing to build and Sales to adopt and later added additional field options.
  2. Create a custom dropdown field in Salesforce/CRM
    • We created a dropdown field that contains the variety of paths that are available for the Sales rep to choose from.
    • If you’re not familiar with how to do this in your CRM, work with your Salesforce admin or operations personnel.




     3. Integrate the custom field in Eloqua

    • Check your data source integration and fields to make sure the field is populated and your inbound syncs are working properly.




     4. Create personalized email content

    • Work with your cross-functional teams to come up with email copy and assets for each path.
    • The emails use dynamic signatures that pull in the lead/opp owner's contact information.





     5. Create a Segment to capture each new nurture campaign member for each of your separate nurture tracks.





     6. Create Nurture flow in Campaign Canvas

    • Build out a flow that makes most sense to your target audience.
    • In the example below, we had a 2-5-5 cadence and would run a "Compare Contact Fields" step to make sure the prospect still has the correct field populated. The Sales Reps are trained to remove their prospects from the nurture paths by selecting "None" or the blank field on the "Email Nurture Campaign" field. Another way to do this would be to remove if the lead converts.
    • At the end of the campaign, all prospects are added to a shared list, put into a program to auto RTM (if not already), and the "Email Nurture Campaign" field is reset to NULL.




     7. ABT: Always be testing.

    • Subject lines, email copy, From name, timeframe, etc. There is so much opportunity to test with this type of campaign.




Results/Challenges/Next Steps:


Our modest 10% Open Rate goal was hit for our recycled leads after a few weeks of testing several subject lines. Our CTR was also higher for short plain text emails as opposed to text-heavy html versions. Again, this was our audience, not yours, so test to see what resonates best for your company.


Sales adoption has been the biggest challenge with this project. Trainings and reminders are necessary for any sized organization, especially if you're asking your sales team to adopt a new process. We have about 50% adoption and are looking for creative ways to increase that figure in the future.


This is also a great area to test different email types (plain text vs html), copy length, subject lines, CTA’s, etc. With our audience, we’ve seen better CTR/response with very short plain text emails.







RPM: Effective Nurturing

BP: Advanced Lead Nurturing

E10: Fundamentals of Emails

E10: Testing Campaigns and Assets

E10: Personalizing Campaigns

E10: System Integration

A marketer´s greatest achievement is an engaged customer. Engagement, which used to be seen as more about branding and awareness, is increasingly perceived as key to the loyalty and advocacy stages of the customer life cycle: an engaged costumer is one who sticks around.

Since last year, our Digital Marketing team´s motto is “No Response Left Behind”; that means that every single response is of key importance to our company; and when we talk about assets downloaded, the importance is even bigger. I remember that some months ago, one of our stakeholder came to our configuration team presenting a plan: she wanted all those contacts that have downloaded at least 2 assets included in an email touch of any of her campaigns to be sent to our internal Telemarketing teams for qualification or to other campaigns for further nurture. In other words, her objective was to work on those contacts showing that level of engagement right away; maybe we could get a lead or even an opportunity, who knows? .

So we created a business case including a campaign canvas which was designed with 5 email touches and each one of those emails had 2 calls to action or assets ( in this case, 2 whitepapers)


# Touches: 5

# Assets offered: 2 per touch = 10 total


We encountered a configuration challenge; we were not sure about how we can create filters that cover all 45 possible combinations to check “at least 2 downloaded assets”. After some thinking, we got to a solution: a Campaign Custom Data Object field (a.k.a. CDO); basically, we thought on adding a new field on the campaign CDO that would dynamically count UNIQUE asset click-through. We called this new CDO Number of assets downloaded.


Let´s see which steps we needed to take to configure this in the system:


Pre-requisites (standard configuration):

  1. Each CTA (asset) has a corresponding CDO field that tracks click-throughs; in the picture below (taken from a CDO report), you can see that the names of the columns starting with “AS” are the assets.
  2. Each CTA is uniquely identified in the Hidden Landing Page (a.k.a. HLP) used for blind form submits, via query strings - and has its own routing case. This is valid for both multiple and unique hidden form scenarios.
  3. Each Campaign CDO has a Datacard Look-up for custom question prepopulation and skip gate functionality (if needed).




HTML Setup:

  1. Add Datacard Look-up in the HLP code to check the values existing in the CDO for the assets tracked.
  2. Add functionality that sends a value to the “Number of assets downloaded” CDO. The process is the following:


  • Check if the contact datacard exists in the campaign CDO according to the script response:


− If yes – move on with lookups;

− If no – send numberr of assets = 1.


  • Also, check if all Eloqua scripts are loaded asynchronously.
  • Pair with existing campaign CDO lookup to avoid adding extra unnecessary calls.
  • And finally, do a lookup on asset name to see if the value already exists for that contact in its datacard in the campaign CDO:


− If value does not exist, increment +1 in “Number of assets downloaded” field;

− If value exists, pass on existing “Number of assets downloaded” field unchanged (for form submission reports).


Please bear in mind that the function can be used only for the specific query strings associated to the assets indicated by the stakeholders as the ones being required for qualification.


Now, let´s talk about coding:



Registration Page implementation:

  • Add two variables in the same section as the other global vars:


var activate_increment_download = false; //activate increment function on form submit

var DLassetName = asset + '1'; // datacard asset name used for setting the increment value – this is added in case the HTML name of the field differs from the value needed for the lookup. Usually it is the HTML name and a “1” at the end. Change only if necessary.


  • Add the following hidden field to the form:


<input type="hidden" name="Number_of_assets_downloaded1" id="Number_of_assets_downloaded1" value="">


  • Add the latest hybrid js file.


Hidden Landing Page implementation:

  • Add two variables in the same section as the other global vars :


var numberOfAssetsDownloaded // sets number of downloads

var dataLookupAssetName //name used for asset in datacard.


This variable is used to activate the increment for each case individually, so please declare it on every case you want to do the increment, as follows:


Var dataLookupAssetName = asset + '1';


  • Add function:


function incrementDownloadLookup(){

                                         if(!dataLookupAssetName) {


                                        } else {

                                                       var script2 =


                                                                      jQuery.getScript(script2,function() {

                                                                                     if (GetElqContentPersonalizationValue || this.GetElqContentPersonalizationValue){



                                                                                                    numberOfAssetsDownloaded =



                                                                                                     if(!numberOfAssetsDownloaded || numberOfAssetsDownloaded == '0')


                                                                                                                    numberOfAssetsDownloaded = 1;

                                                                                                     } else if( !GetElqContentPersonalizationValue(dataLookupAssetName) ) {

                                                                                                                    numberOfAssetsDownloaded = parseInt(numberOfAssetsDownloaded) + 1;


                                                                                } else {

                                                                                                     numberOfAssetsDownloaded = 1;




                                                    }                 }


Please note that the campaignDatacardUniqueID value must be the datacard lookup key. Call the function after populateContactValues() finishes (instead of form submits). Test if the system works in both cases, for new or old contacts.


Campaign CDO setup:

You just need to add a new NUMERIC field called “Number of assets downloaded


Eloqua Hidden Form setup:

  1. Add custom field: “Number of assets downloaded” – Single line text with html name “Number_of_assets_downloaded1” which is to be mapped with the above CDO corresponding field.
  2. Each CTA is uniquely identified in the HLP used for blind form submits, via query strings - and has its own routing case. This is valid for both multiple and unique hidden form scenarios.
  3. Each Campaign CDO has a Datacard Look-up for custom question prepopulation and skip gate functionality (if needed).


Finally we need to create a Shared Filter which will check contact engagement based on the Business requirement and then add it to the campaign canvas with the emails in question. We configured the shared filter by selecting “Number of assets downloaded” CDO field which is “at least” 2 (for our example). Use same filter after each Touch on the Canvas for the Business qualifying question.




One note I want to add is that the suggested threshold for using this approach is more than 4 assets to track (>6 combinations).


After doing some tests, we were glad this was working as expected. We presented our work to the stakeholder and we got a positive response. We can confirmed that by doing this process, we are connecting with our engaged customers more rapidly. We generate a weekly report including those contacts that downloaded at least 2 assets and send it to our Telemarketing teams for qualification.

At the end of the day, the result is that we show to our customers that we really care about their needs and we can help them finding the correct solution they are looking for.


Thanks for reading!!



Eloqua Academy Course Reference:

Eloqua 10: Progressive Profiling

Eloqua 10: Effective Marketing with Custom Objects

Advanced Editing and Form Processing

Eloqua 10: Integrating Custom Objects with Campaign Canvas

Eloqua 10: Web Profiling

Topliners (Tag: asset_tracking)



We are a company that has 3 Business Units across 120 different countries. Working in different business units with different instances of Eloqua is not the best starting point to share best practices, information or a uniform governance model. Over the years, the different instances of Eloqua have experienced many users with varying levels of expertise and the company has gone through various brand changes. We have 3 different business units which has resulted in having no clear ownership of Eloqua.

It was very clear that we needed to do something about this if we want to move to the next level of marketing.




We have been using Eloqua over 9 years. Largely, this has been without any governance. It was clear this needed to change.

You probably recognize this phase -- you realize you need to do something, but what do you do and where do you start?


We currently have 4 instances of Eloqua. The big questions for us were:

  1. Are we going to clean or start over with new instances?
  2. Are we keeping 4 instances or do we go to a single instance?
  3. What is the best thing to do in a situation like this?
  4. How can we support the system including new governance and moving forward with a better managed and easier to use system?


First step


We decided to bring together the marketing leaders from all business units across all regions. We arranged a workshop where we got together with Marketing and IT, who is responsible for Eloqua and Salesforce.


The intention was to come up with a plan for all Eloqua instances and a roadmap of things we need to do or want to look into. We were looking at items we could pick up ourselves and assess where we might need to connect with a third party.


Two things became clear, we have to continue using separate instances for now and moving to a new “house” was too complicated for various reasons. So, we decided to do a big summer clean…


A few of the key points were:

  • What should users be able to do in the system?
  • Who owns what?
  • What else do we want to do with Eloqua?
  • What are our priorities?
  • Training needs


After the meeting, we walked away not only very energized from all the amazing plans and possibilities, but also with a road map for the next 3 years!



Our Goals


A system that is better managed with users that can only do what is needed.

We decided on:

  • Setting up users groups
    • Advanced users need to at least have their master certification
  • Permissions settings
  • Naming convention for
    • Folders
    • Assets
  • A training plan for all users including a minimum basic requirement
  • The need of a point of contact for questions or assistance


A cleaner system that has:

  • Clean user base
  • Brand compliance
  • Assets that can be shared Globally
  • Manageable number of assets


A process for managing contacts:

  • Hard bounces
  • Inactive contacts
  • Incomplete contacts
  • Deletion process to keep a clean contact base



From plan to execution


First, we started to identify our most frequent users. We wanted to set up end user groups and a global governance team.


We realized this was not going to be easy. History showed us that the Business Units  are rarely touching each other's business and, therefore, it was not really needed for them to work together. We wanted this to change for only one reason… Sharing information, best practices and experiences! Because we might not share business, but we do share clients!


We started with setting up regular governance calls.  With this group, we talk about our plans and items we need a decision on. Some of the topics we discuss during these meetings are:

  • Support
  • Governance
  • Cleaning
  • Updates to the system
  • New tools
  • Etc.


What did we decide on?


Short term items we want to look into are things like:

  • Cleaning
    • Templates that have never been used
    • Emails created but not been sent
    • Forms with no data
    • Pick lists – make sure they are still needed and if possible similar to our CRM
    • Images uploaded before the date of our new brand roll out
    • Contacts f.i. we are looking at:
      • Bad Emails: Contains any of the following: ‘dummy’, ‘ ‘, , ‘?’, ‘@test’, ‘test@’, ‘<’, ‘>’
      • No Communications in the past 6 months: Not been sent Emails, not submitted forms, not visited landing pages, not visited websites, not opened any emails
  • Direct impact for Marketing
    • Responsive templates
      • We made sure that everybody now has access to responsive templates that are on brand
    • Progressive profile forms
      • We are working with the business to replace some forms on internet with progressive profile forms
    • We are looking into apps that can be used. For instance, apps like:
      • Webex
      • LinkedIn
      • Brightcove


What happened so far?


We started with cleaning our users. Our governance meetings are set up and the 1st user group meetings are planned.


Next steps


Currently, we are primarily cleaning. We started with Users:

  • Finding out if all users are still valid users?
  • Which region are people
  • Who is responsible for the users

We added all the correct information to the users in Eloqua so we could reach out to the people responsible for each region to get confirmation.

We also moved users into the correct user group with the right level of access. This all was a big change to everybody as they were used to having full access for many years.


The next steps we are taking are:

  • Cleaning other assets like templates and pick lists
  • Looking at better integration between Eloqua and Salesforce
  • There is a huge need  from Marketing to have a global preference center. This is something that is moved up on our priority list with the new EU privacy legislation that has been announced.


Help from Eloqua


We could not have done this without the help of our Account team from Oracle. They have been a tremendous help in making some of the decisions. If we needed insight before we could make decisions they were always there to have a conversation, bring in experts or suggest some of the Oracle Marketing Cloud Academy training sessions.


Oracle Marketing Cloud Academy classes that directly influenced this project:


  • B2B: Progressive Profiling
  • B2B: Data Cleansing
  • Eloqua 10: Database Security
  • Eloqua 10: User Management
  • B2B: Custom Subscription Management


Prior to Eloqua, we were having to create unique forms for each and every campaign that we ran through Pardot.  As a global organization, we require our content to be translated into 10 different languages to support more than 40 countries, so a simple contact form would require a tremendous about of time and manual effort.  When we were implementing Eloqua, we made the decision to create Master Forms with each one supporting a category of content with standardized processing steps and actions.  Because of the flexibility to integrate external web forms with Eloqua, we were able to setup a process within eZ Publish were an editor can choose the type of form they would like to place on their landing page, provide a name for the form and have the data seamlessly integrate within Eloqua.  This has ensured consistency in how we capture data, as well as significantly decrease the amount of time and effort it takes to get a simple web form deployed.


Challenges and Goals

As an international business, we support countries who have strict standards for sending commercial emails, including Canada’s Anti-Spam Legislation (CASL) and Europe’s EU Opt-In Directive. To adhere to these strict spamming laws, we decided to create a Double Opt-In system. Another benefit of Double Opt-In is protecting our database against spambots, and fake subscribers. We noticed that contacts were using fake email address because we were not validating that the email was real.  Double Opt-Ins also increase our campaign open rates, lower bounce rates and unsubscribe rates because we are emailing contacts who would like to hear from us.


Documenting our Project Plan

To begin our project, we charted the steps of a new contact vs confirmed contact who comes to our site and downloads an asset.


This is the customer’s journey:

  1. The customer goes to our site and submits a form that contains legal language acknowledging that we will using their information for commercial purposes
  2. If the contact is not opted in
    1. They will be redirected to a page that says “Thank you for your interest. An email with a link to your content will be sent to the email address you provided. Please add the email domain to your safe sender list.”
    2. They will receive an auto-responder email that contains the content and has this legal language “By clicking on the link, you acknowledge that comScore, Inc. will use the information you have submitted to fulfill your request and may contact you for commercial purposes. You can unsubscribe at any time. For additional information, please read our privacy policy.”
    3. Once they click on the “Download” button, which is a blind form submit, they will be redirected to a page that contains the content and on the backend will now be opted-in to our email communications.
  3. If they have opted in, they will be redirected to confirmation page and receive an auto-responder email that contains the content.


We then charted the steps that would need to be executed in Eloqua and/or eZ Publish.


From Plan to Execution

We began by charting the different types of form submits that a contact could make, including content, product cards, contact me, and communication preferences. We broke it out into these four campaign groups because the email copy of the confirmation email would vary. We would begin with the English version of the copy and then work with our international marketing managers to translate it into the following languages: Russian, Spanish, Portuguese, French, Dutch, Japanese, German, Italian, and Chinese.


We took these below steps to implement our double confirmed opt-in plan:


1. Added a field to our forms in eZ Publish called Client Facing Form Name

This allows us to keep the content title in language and ultimately be used as a field merge to populate the auto-responder emails.



2. Added new CDO fields to our Forms record

Once someone fills out the form we created in eZ Publish, we then store the Client Facing Form name field in the CDO Form Name Client Facing field below.


3. Create a Field Merge for the CDO Form Name Client-Facing

This field merge will be populated is populated in the headline and body copy of the auto-responder email to bring in the Client Facing Form name which is the title of the asset.


4. Create Contact Fields called Email Opt-In and Confirmed Opt-In Date

These fields will be used later when creating Dynamic Content and to opt-in a contact through form processing steps. See more information below.


5. Update form processing steps

For our content master forms

    1.       Always Update Custom Object = Forms
      1. Every time a contact submits a form we want to update our auto-responder emails with the new CDO Form Name Client Facing Field
    2. Redirect to Web Page
      1. For this processing step, we place rules that evaluate if that customer has opted into our program, we will redirect that contact to a thank you message that include a link to the asset.
      2. If they have not opted in, we will redirect them to a message that says:  “Thank you for your interest. An email with a link to your content will be sent to the email address you provided. Please add the email domain to your safe sender list.”
    3. Add to Campaign
      1. Note: This step was added after the campaigns and emails had been created
      2. Based on the form field called Form Language, contacts will be added to the same language auto-responder email on the campaign canvas


           For our Blind Confirmed Opt-In Form

We created a new Master Form called Blind Confirmed Opt-in that is used in the auto-responder emails as a blind form submit.

    1. Update Contacts – With Custom Values
      1. This step is used to update a new contact’s Email Opt-In field. Once a new contact clicks on the Download Now button we will update their contact record Email Opt-In with a 1, which means that they have been opted-in
    2. Redirect to Web Page
      1. Once they click on the Download now button, we will redirect them to a confirmation email that contains the content.


This below chart explains the steps that are executed in Eloqua and eZ Publish.


6. Create dynamic content

  • For each of our markets we created dynamic content that contains rules for an opted-in contacts vs a contact who has not been opted in.
  • The only difference in copy, is the addition of the legal language for contacts who have not been opted in (see screenshot below)




7. Create auto-responder emails

  • The header of the email was the field merge that brings in the title of the asset and the body of the email is the dynamic content section




8. Create campaigns for auto-responder emails

    1. As I said above, we created 4 campaigns for this program because the language contained in the auto-responder emails differed
      1. The 4 campaigns are: Content Download, Product Card, Contact Me and Communication preferences
    2. Make sure contacts are allowed to re-enter the campaign more than once and Allow emails to be resent to past recipients


9. Testing, testing and more testing!



Next Steps

For phase II of this project, we are looking to populate our auto-responder emails with suggested content to further nurture engaged leads.


Classes that directly influenced this project

  1. Best Practices: Email Deliverability
  2. Data Cleansing
  3. Custom Subscription Management
  4. System Integration
  5. Blind Form Submits
  6. Effective Marketing with Custom Objects

Describe the marketing challenge you were trying to solve with your campaign or strategic initiative.


Lead Record Type is nothing but queue in SFDC which assign leads accordingly. There are certain Lead Record type values causing integration errors. To normalize the SFDC Lead Record Type values. We were using name  instead of 15 or 18 digit code(ID) and that was causing integration issues.


What goals did you set at the start of your campaign to validate success?


The goal is to allocate right leads to right sales people and also to automate the SFDC Lead Record Type for the contacts. First, find the contacts that have invalid SFDC Lead Record Type or name instead of 15 or 18 digit ID. That we found by going in Field and Views option and population the values in this field.


How did you benchmark or document your current state?


Benchmark not applicable.


Describe your campaign or initiative and the steps you followed to implement.


I have created the segment  where I can use the filter criteria “Compare Contact Fields” with the contact field value “SFDC Lead Record Type” with the condition “ exactly”  matches the specific Lead Record Type value which will give you the no. of contacts with that Lead Record Type value. Once found the contacts, run them through Update rule to maintain the consistency. And also updated all related form those are passing wrong Record Type value in contacts for future. Replace the Lead record type name with the 15 or 18 Digits IDs.


I have created the update rules for SFDC Lead Record Type to normalize the SFDC Lead Record Type values. Also in SFDC I asked users to create Queue.

To create update Rule, click on Contacts -> Data Tools -> Update Rule

  1. Select the field to update as “SFDC Lead Record Type
  2. Update action should be “Set to value” for this criteria
  3. Make this rule conditional where “SFDC Lead Record Type” is Equal to “EU Dublin Sales”…


adipala 1.JPG


Created no. of update rules to meet the specific criteria.

Update Rules used in Program canvas to automate the routing of Lead Record Type.

Steps to Create Program Canvas,

  1. Click on Gear icon after “Preview New Menu” button in Eloqua RHS (Top)
  2. Click on Program Builder or Canvas
  3. Then click on “Create a contact Program”


adipala 2.JPG


Which Oracle Marketing Cloud Academy courses have directly influenced this campaign?


Eloqua 10: Program Builder Overview, B2B: Data Cleansing Oracle Marketing Cloud Academy courses were helpful to create update rules. Also some part of integration with SFDC.


How has this campaign impacted your business?


The impact on business is we are able to pass SQL leads to correct sales team and that helped us to convert more prospects to customers and also minimize the closed/lost no. of leads.

Filter Blog

By date: By tag: