Update August 5 2014: fixed bug that was causing jquery.validate to fail in some situations. Fixed bug causing problems when the channel field field is not specified - now you can just set channelField=0 and it will ignore the channel tracking feature. Also added a version number (previous versions were not numbered) - the current version is 1.5.

Update May 5 2014: fixed critical bug in prepop which caused the callback function to fail when the visitor has no cookie.

Update July 31, 2013: Critical update with two crucial bug fixes: fixed the script comments to give correct instructions for the theseFields array, and added a parameter visitorEmailField because apparently different instances of eloqua use different field names for the visitor data lookup email address. I also added a line to the instructions that shows how to set it up so that if the visitor is new (has no Eloqua cookie) and they fill in their email address, the whole script runs again, populates the form according to the new email address, and runs progressive profiling accordingly.

To find out what your visitorEmailField should be set to, you'll have to look at the data lookup scripts for the cookie data lookup and see what the field names are. It should be something like V_Email_Address or V_ElqEmailAddress.

Update July 25, 2013: I have posted a new version which fixes several critical bugs in the previous version. Please get the latest version below if you're still using any of the older versions.

Update July 19, 2013: this script has been updated to use the new Eloqua tracking scripts. I have added support for radio buttons and for using any field (not just the first field) for the email address. Also note that skip rules are now indexed by field name, not by number.

----------------------begin original post-----------------------

First post.

I'd like to share with you a script I call Progress Pro - a script that uses jquery and data lookups to implement advanced progressive profiling for Eloqua 10.

You can download the script by clicking on the attachment at the bottom of this post.

Progressive profiling is a technique whereby visitors are asked different questions each time they fill out a form.  The idea is to start by asking a few simple questions, for example email address and name, and gradually learn more about the visitor as they perform subsequent registrations. This reduces the barrier to entry into your marketing campaign, while still allowing you to collect detailed information on your most interested prospects.

The Problem

Eloqua 10 has a cloud component for progressive profiling. If you want to implement progressive profiling on an Eloqua-hosted landing page, I suggest you start with that. See this post: http://topliners.eloqua.com/community/do_it/blog/2013/02/05/how-to-do-progressive-profiling-in-e10-using-the-cloud-component

However, this solution only works for forms hosted on Eloqua landing pages. It also has some limitations, although it is generally pretty good. But if you want to do progressive profiling on your own forms, you will need to implement some sort of custom solution.

The desired solution would work for visitors from any channel, use only one form, and enable advanced dynamic skip rules while still allowing easy implementation for simple use cases. It would dynamically pre-populate the form based on browser cookie or email address and ask questions conditionally according to the prospect's previous answers. Incidentally, it would also be useful to track the incoming channel and store it in a contact field. Progress Pro implements such a solution.

Methodology

Eloqua has an amazingly awesome feature called Data Lookups. I won't go into the details, as the feature is well documented. This feature allows you to access data from your Eloqua database using javascript. Once you have data on the visitor, you can use javascript to manipulate the form accordingly. The methodology is:

•     Create a long form, beginning with email address, containing all of the questions you want to ask in the entire profiling process. Set the email address field to prefill, but don't make any of the fields required.
•     Create two data lookups: one for looking up the email address by tracking cookie, and one for looking up the rest of your data by email address. These lookups are performed by Progress Pro using jquery.getScript to load a script with appropriate parameters from Eloqua.
•     If the visitor comes in from an email, their email address will be prefilled. Progress Pro uses this to perform the lookup by email address and prefill the form with data accordingly.
•     If the vistor comes from another channel and has an Eloqua tracking cookie, Progress Pro performs a data lookup by cookie to get the email address, then performs another lookup by email address to get the rest of the data and prefill the form.
•     If neither of these is the case, the visitor will begin by filling in the email address field. Progress Pro attaches a jquery.change handler to the email field, and performs the lookup by email address once it has been filled in. If the visitor is not in the database, the rest of the form obviously stays empty.
•     Progress Pro then hides some of the questions on the form according to parameters you specify. In the basic setup, you simply specify a number of fields at the top of the form that should always be shown, and the number of unanswered questions you want to ask. Each time the visitor returns, they will be asked a new set of unanswered questions until they have completed the entire form.
•     For more advanced use cases, you can specify an array of conditional skip rules; e.g. if the prospect indicates interest in a particular product in the answer to one of the questions, skip all questions having to do with other products. These rules are implemented dynamically - as soon as the prospect selects an answer to the question on which the rule depends, the form immediately alters accordingly.
•     Progress Pro uses jquery.validate to validate the form. This is necessary because only visible fields can be required, or the form will always fail validation. You specify an initial set of validation rules, which are modified dynamically according to which fields are shown.
•     To track the incoming channel, you can use an optional URL parameter called "ch" - your form needs to contain an hidden field called "Channel History" which will be populated with whatever channel you specify in the URL.

Usage

To use this script, first upload it to your website (or wherever else you want to host it). Then, in the <head> section of your landing page, add javascript code similar to the following:

//---------begin code-------------

<script type="text/javascript" src="https://ajax.googleapis.com/ajax/libs/jquery/1.6.0/jquery.min.js"></script>

<script type="text/javascript" src="http://ajax.aspnetcdn.com/ajax/jquery.validate/1.8/jquery.validate.min.js"></script>

<script type="text/javascript" src="http://ajax.aspnetcdn.com/ajax/jquery.validate/1.8/additional-methods.js"></script>

<script type="text/javascript" src="http://www.mydomain.com/assets/js/progressPro.js"></script>

//-----------end code--------------

This is to load the necessary script files. Obviously replace "mydomain" with your domain, and replace "assets/js" with the path to your copy of Progress Pro.

You should also make sure you have installed the Eloqua visitor tracking code, which you can find in Eloqua under Setup->Website->Tracking.

Then you set up a document.ready function to call the function prePop and prepopulate the form. You will need to specify which field to use for the email address. As a callback from the prePop function, optionally call addChannel() to record the incoming channel in the Channel History field, and call the function progressiveProfile to hide fields as appropriate. Be sure to call the latter two functions as callbacks from prePop or they will not work.

In the most basic usage, just specify the number of unanswered questions to ask and the number of fixed questions to always show at the top. For this example we will set both to 3. For basic usage, just specify the skip rules as an empty array.

You will need to provide the data lookup keys for your data lookup by cookie and by email. These will be generated by Eloqua when you set up the data lookups. You will also need to provide an array of form fields (indexed starting at 0) with the names of the database fields corresponding to each question. These names can be found in the fields setup in Eloqua. Also provide a set of jquery.validate validation rules (see http://docs.jquery.com/Plugins/validation). In this example, all fields are required.

//------------begin code--------------------------

<script type="text/javascript">

  $(document).ready(function() {

  var elqDLKey_Cookie = escape('###');

  var elqDLKey_Email = escape('###');

  var theseFields = ['C_EmailAddress', 'C_FirstName', 'C_LastName', 'C_Company','C_Primary_Interest1', 'C_BusPhone', 'C_Website1', 'C_Lead_Role1', 'C_Function1', 'C_Title', 'C_Company_Type1', 'C_Project_Time_Frame1'];

  var popFields = ['C_FirstName', 'C_LastName', 'C_Company','C_Primary_Interest1', 'C_BusPhone', 'C_Website1', 'C_Lead_Role1', 'C_Function1', 'C_Title', 'C_Company_Type1', 'C_Project_Time_Frame1'];

  var openQuestions = 4;

  var fixedQuestions = 1;

  var thisForm = 'form21';

  var channelField = 0;

  var emailField = 'C_EmailAddress';

  var visitorEmailField = 'V_ElqEmailAddress';

  var myValidationRules = { rules: {C_FirstName: {required: true}, C_LastName: {required: true},

      C_Title: {required: true}, C_Company: {required: true}, C_Website1: {required: true},

      C_Primary_Interest1: {required: true},C_Project_Time_Frame1: {required: true},C_Lead_Role1: {required: true},C_Function1: {required: true},C_Company_Type1: {required: true},

      C_BusPhone: { required: true, phoneUS: true }, C_EmailAddress: { required: true, email: true } } };

  var mySkipRules = {};

  prePop(thisForm, theseFields, elqDLKey_Cookie, elqDLKey_Email, emailField, visitorEmailField, function(){

      progressiveProfile(openQuestions, fixedQuestions, thisForm, theseFields, popFields, elqDLKey_Cookie, elqDLKey_Email, emailField, channelField, myValidationRules, mySkipRules);

  });

  });

  </script>

//--------------end code-------------

For advanced usage, the skip rules are specified as an array. You set which field (by name) is to be hidden or shown, the field value the rule depends on, an operator, and a condition to match the "depends" field against. In other words, the rule states something like "hide this field if this other field contains 'California'" or perhaps "show this field if this other field equals 'yes'". You can specify multiple skip rules for each field. As a simple example, suppose we want to hide field 'C_HR_When1' if field 'C_Product_Family1' has the value "yes." The skip rule for this looks like:

//---------begin code-----------

var mySkipRules = {'C_HR_When1': {1: {action: 'hide', depends: 'C_Product_Family1', operator: 'eq', condition: 'yes'}}};

/----------end code ---------------

The possible actions are "hide" and "show" where show takes priority over hide if the rules contradict. The possible operators are "eq" for equals, "neq" for not equal to, "contains" and "always" - always means the action will always be taken regardless of the values of other fields.

Et voila! We have progressive profiling that works for all visitors, uses a single form, and supports both simple cases and more advanced conditional rules.

I hope you find this useful. If you have any questions, comments or problems with this, please don't hesitate to contact me: freejung@gmail.com

[EDITOR'S NOTE: As this is custom code, the Eloqua support team will not be able to provide support or help you troubleshoot this code if you implement it. We recommend that you take Eli up on his offer and add a comment to this message and/or email him directly if you run into questions.]

All Eloqua assets are stored in folders in their corresponding areas of the application.  Accessing your files and folders is accomplished using the Eloqua 10 Asset Choosers.

Navigating through the Emails, Landing Pages, Campaigns, Forms and Lead Scoring Choosers

To access and navigate the Asset Choosers in Eloqua 10:

1. For Emails or Landing Pages, navigate to Assets> Emails or Assets> Landing Pages.  For Campaigns, click Campaigns from the navigation toolbar, and for Lead Scoring Models, navigate to Contacts> Lead Scoring.
2. In the corresponding Launchpad:
   • For an Email: Click Open an Existing Email.
   • For a Landing Page: Click Open an Existing Landing Page
   • For a Campaign click Open an Existing Campaign.
   • For Lead Scoring Models, click Open an Existing Model.
3. By default the All Files folder is selected on the left-hand (navigation) pane.
4. To change the search location for your assets, select one of the following:
   • To view only those items created by you
   • To view only those that you recently accessed
   • To view ones that were recently modified (by anyone).
5. On the right-hand side, the breadcrumb (folder) icon displays All as your current location.  All folders and files are shown under that heading.
6. To open an asset (file), double-click on its name, or highlight the asset and select Choose in the bottom-right corner of the Chooser window.  Double-clicking on a folder displays the contents of that folder, including any subfolders and files contained therein.
7. As you navigate through the folder structure, the breadcrumbs indicate your position within the file hierarchy.
8. Hover your mouse cursor over the breadcrumb to highlight your navigation path as you look through the folder structure.
9. Click on the folder name to return to any folder which you have visited.
10. After you have opened the asset, the Chooser closes.
11. For the current session only, when you reopen the Chooser for the same asset, your previously viewed location is remembered and the Chooser automatically opens to that folder.  However, after logging out of the application, the inital view in that Chooser will return to All Files (All folder).

Using Favorites

You can now create a list of folders and files (assets) that you access on a frequent basis using the Favorites heading on the left-hand side.

To add a folder or file to the Favorites list:

1. On the right-hand pane of the Chooser, navigate to the folder or file you wish to add to the list.  Once you have located the asset, left-click on its name and drag the item to the left-hand pane under the Favorites heading.
2. Release your mouse button and the asset is added to your list.
3. As you add (drag-and-drop) more items into your Favorites list, a horizontal line indicates where the item will be added in the list, just as if you were adding a bookmark to your browser's favorites.  To add the new asset to your Favorites, release your mouse button once the horizontal blue line is where you want the asset to be added.
4. Favorites can be repositioned at any time.  To move an item up or down in your Favorites list, single-left click on the item, and while holding down your mouse button, drag it to the position when the blue horizontal line is at the desired location.
5. There is a maximum of ten (10) items that can be added to the Favorites list.  If you attempt to add an eleventh (or more) item(s), an error is displayed alerting you to delete one or more from the items in the Favorites section before attempting to add others.

To delete a folder or file from the Favorites list:

To delete a folder or file from your Favorites list, hover your mouse cursor over one of the items in the Favorites list and click the x to the right of its name.  The item is removed from the list, but not from Eloqua.

Notes:

• You can only add a file or folder once to your list.  If you attempt to add a folder or file that already exists in your Favorites, an error is displayed.
• Only the folder that you add to your Favorites list is a Favorite.  This means that files and subfolders contained within that folder are not marked as favorites; you must manually add them one by one.

Moving Files or Folders

There are two methods for moving files or folders within your folder hierarchy in an Asset Chooser.

To move files or folders:

Method A:

1. Search for or navigate to the file or folder you want to move.
2. Select the item and drag-and-drop to the desired location.  The item is moved to the new location.

Method B:

1. Search for or navigate to the file or folder you want to move.
2. Right-click on the file (or folder) name and select Move to Folder.
3. In the folder list that opens, left-click on the name of the desired folder and click the Move button in the lower-right corner.  The file (or folder) is moved to the new location.
4. If you want to move more than one item at a time, you can Ctrl- or Shift+Select multiple items and drag-and-drop them simultaneously.
5. Once selected, right-click on any one of the selected items and click Move to Folder on the drop-down menu.  Your complete folder structure is displayed.
6. Highlight the folder to which you want to move your item and click Move in the lower-right corner of the window.
   Your files or folders are moved to the new location.

Hi,

as the new lead scoring system in E10 stores the contact's lead score in the metadata instead of in a Contact field,

how can I take a look at a particular contact's score? It's really annoying that you can't add it e.g. in a Contact View

defined under Settings>Fields&Views>Views.

Help anyone?

wbr,

-tatu

Overview

Contact Security allows you to restrict users' access to contact data.  One of the concepts that changes when using Contact Security is the activation of Eloqua 10 campaigns and Program Builder programs. When a user activates a campaign or a program, only contacts the user who activated the campaign/program has access to are processed in the Campaign. This feature ensures that security permissions and access rights are respected during an automated marketing Campaign.

Eloqua 10 Campaigns

There is no change when activating a newly-created campaign. The changes for when you are activating a previously activated Campaign and/or when you are an administrator are as follows:

• When activating a campaign that was previously activated by a different user, you will receive a warning that you are about to activate this campaign as a user other than the user who previously activated the Campaign. This is important because if you have different contact security permissions from the previous user, it will impact the contact currently in the campaign and any Contacts that will flow into the campaign as it progresses.

Eloqua 10 Campaign	Program Builder Program

• There may be instances in which you are doing work for another user who has specific contact security access that will be applied to this Campaign. As an Eloqua Administrator, when you begin the Campaign activation process, the Run As setting is available, where you can select to activate the campaign as your user account or as any other user in your Eloqua organization. .

E10 Campaign	Program Builder Program

Bonus Tip!

As an Eloqua administrator, you can see the name of the last person to activate the Campaign.

To see the name of the last person to activate the Campaign:

In Campaign Canvas:

1. From the Action Menu (gear icon), select Settings.
2. On the Settings tab, the name of the last person to activate this Campaign is indicated at the bottom of the panel, labeled Last Ran as User.

In Program Builder:

• On the Program Details window, the name of the last person to activate the Campaign is shown in Programs Run As field.

E10 Campaign	Program Builder Program

Campaigns can be assigned a security permission called Activation. This permission allows customer administrators to determine if a user has the ability to activate, view and/or edit a Campaign. A good example of its value is if you have a partner or basic level user to whom you want to give permissions to create and setup campaigns but not the authority to activate. This is only available for Eloqua 10 campaigns.

Existing Campaigns

This allows you to change the activate permissions for campaigns that already exist.

To change the Campaign Activation permissions for pre-existing Campaigns:

1. Click Campaigns at the top of the navigation toolbar.
2. Select Open an Existing Campaign.
3. Select the Campaign you want to modify.
4. In the gear drop down click Permissions...
5. In the Activate column, check or uncheck the box corresponding to the user or group of users to enable or disable Activation permissions, respectively.
   
   
   
6. Click Save.

Now only the selected users or security groups have users have the ability to activate a campaign. If a user does not have the ability to activate a campaign, the activate button is disabled.

New Campaigns

This section explains how to modify the permissions for a security group  and define if their permissions to activate a campaign by default when created. It also allows you to define what other users or security groups have permission to active campaigns created by them.

To assign Activation rights when creating a New Campaign:

1. Navigate to Settings> Setup > Users.
2. Select the Security Groups tab and click on the security group containing the users you want to change.
3. Click Default Asset Permissions.
4. Click Edit.
5. In the left hand list of asset types, click Campaigns.
   IMPORTANT: Only asset types the select security group can create will be displayed. If you do not see Campaigns, follow the above steps for enabling asset creation of campaigns.
   
6. In the Default Asset Permissions page, Asset Creator is shown. Set the desired View, Edit, Set Security, Delete, and Create permissions for this security group. Once saved, when a user in the security group you are editing creates a campaign, they will only have the level of access you define here. For example, if you enable every checkbox except Activate, when a campaign is created the user can edit and delete it but not activate.  This can be useful when you want to go through an approval process within your organization before activating a Campaign, and allow only certain people this right.
   
7. Use the type-ahead search for users or groups that you want to assign Activate permissions to. These users and/or security groups will also have permission by default when new campaigns are created by users in the security group you are editing.
8. Click Save.

Introduction

6. While viewing the Identity Provider you have configured (in view mode, not edit mode), click to download the IDP. This will produce a metadata xml file. You now need to upload this file into your Identity Provider system as a Service Provider. This process varies depending on the SSO vendor you are using.

7. While viewing the Identity Provider you have configured, click the link under Service Provider Certificate.

8. Download the certificate and upload into your SSO vendor system.

9. To test that your setup has been successfully completed, navigate to login.eloqua.com and click Sign in using another account. Enter your company name and press Enter.  This should redirect you to your SSO vendor's IDP login page. If your browser already has a SAML session with your provider, then you will be logged in directly to Eloqua.

Setup is complete.

Hi

I have created an Eloqua Cloud App with an Action Service.

To test it I created a campaign and added a couple of members but for some reason it seems like the notification url is not called at all.

It set the service up exactly like described here:Develop an AppCloud Action Service

My Notification URL is: http://URL/apps/components/notify?instance={InstanceId}&asset={AssetId}

I had a look in the log file (for the app) and there is no outbound call for the notification url either.

So the question is what am I doing wrong?

thanks,

Simon

Hi Topliners -

There are a lot of conversations on TL about this, and after two weeks of trying to figure it out on my own by reading and taking EU classes as fast as I can, I'm closer to figuring out the step-by-step but not entirely.  I got really close with one class that presented how to do a Welcome campaign but before I could really study the sample forms in the class, it was over and the samples wiped away for the next students. So in a nutshell, this is all I want to do (I say "all" because it should be SO simple like any other email marketing tool).

We have five email groups - news and events, media relations, and our three major business units. I've got that set up.

If your email address is in our Eloqua database and you get an email from us, the out of the box subscription management landing page is connected to the footer and you can edit your subscriptions (those five groups).

Here's where I'm not finding an answer. I want to let people subscribe externally from Eloqua. I want a small form on our web site (or could be a button to a landing page/form on E) which lets them enter email address, first and last name, and check one or more of the five boxes for those aforementioned groups.

So I started building this little form.  I naturally thought it made sense to connect the groups already set up in Email Groups to the form but can not figure out where to access them to place on the form. I attempted making custom check boxes which I could process to the email groups but couldn't figure out where the processing step to write the preference to the contact when its added to E. And then further reading on TL said to use Shared Lists - which I can see how to write to from the form processing. But then I had this question. When my colleague wants to send an email to people subscribed to information about Business Unit B, does she segment by the email group? or by the shared list? or both? Do they operate separate from each other? Do they need to update each other? Ack... every answer I find on Eloqua generates 20 more questions

I know people are doing this. The Welcome Campaign in the Personalizing Campaigns has for its first step a Newsletter Sign Up form but like I said, I can't actually go back and SEE it to see how it was done. I see a lot of people asked for help on this topic but not a lot of answers on how they accomplished it. Can anyone point me in the right direction or better yet, provide steps to make this happen?

THANK YOU

I've been following this thread How many form processing steps are too many?  It looks at the technical side of how processing steps trigger... but the comments started to have a bit of competition for most processing steps... What about you? What are the most form processing steps you've ever used on a single form?

Hi,

I am pulling our suppression list for a vendor. In E9, I would pull the "Overall unsub - all time" or something like that. I don't see a similar report in E10, any ideas?

I could export a filter? Not sure that would give me unsubs we've deleted though.

Stacey

It’s that time of year again! Eloqua is pushing its Summer 2014 release over the next two months. Here is the schedule and some of the features we are most excited about!

• POD 2 is scheduled for June 17
• POD 3 is scheduled for July 6
• POD 1 is scheduled for July 27

Don’t know what POD you are in? Here’s how you find out:

Check out this quick list of the features we think are most exciting coming out of the Summer 14 release:

Use External Systems to Drive Campaigns (Cloud Actions, Cloud Decisions):

• This means you will be able to trigger actions in external systems from a campaign step (instead of ‘send to cloud connector’ step, there will be a specific action for that installed app, i.e. register with WebEx – that action will be listed along the left of the campaign canvas). It also means you will be able to use external data to define branching logic ‘decisions’ in a campaign and you can allow external systems to put contacts into campaigns.

Template Design & Management:

• Eloqua will now have new template capabilities to create emails with lockable sections and propagate changes to all emails using the template; no more “save as” or “copying” emails to create ad hoc templates. Now you (or your designers) can define editable sections in HTML and enforce when things are uploaded as a template.

Improved Editing & Design Experience:

• What used to take designers, HTML and marketers lots of time will now be streamlined. In the new release you will be able to make inline visual edits to uploaded emails or landing pages, as well as getting a new mobile preview that renders content on a standard 960×640 screen.

Marketing Operations Center:

• No one ever liked having to answer to IT for system problems, lack of logs and service issues. Now Eloqua is providing a slick set of reports and dashboards with key service instrumentation, monitoring and alerting; actionable views of logs and system messages (lead scoring, Bulk API usage), and the ability to enable/disable services in the system.

Integrated Sales and Marketing Funnel (Controlled Beta):

• Marketers are getting one step closer to a full closed-loop reporting system that can be sliced and diced with ease. Right now, this is in a controlled beta, but we are very excited to see it rolled out!
• Currently supported for SFDC only, CRMOD coming in Fall.
• Stages are set up in Revenue Architect; report is based on Stages, not stage type.
• Data in the report runs by ETL process, so there is a bit of a lag; however, the report shows date/time of last/next update.

Oracle Content Marketing

• For users of Oracle Content Marketing (formerly known as Compendium), there is a very slick and functional calendar update coming! The calendar will include ALL activity (not SRM/Responsys yet):
• Emails scheduled for a certain date/time; draft emails/campaigns
• Campaigns that are less than 30 days in length will appear on the calendar for the duration of the campaign
• Campaigns that are more than 30 days will only show the campaign on the start date
• You will also be able to manage across business units/multi-division: manage multiple workflows/projects/personas/content.
• The app will feature multiple approval workflows: improved role-based access features and commenting on assets to allow for in-app collaboration.

For a full listing of the new features rolling out and documentation, visit the Release Overview on Topliners: http://topliners.eloqua.com/docs/DOC-2524?sr=tcontent

Originally posted at: http://www.pedowitzgroup.com/blog/eloqua-summer-2014-release/

As part of our data health we remove records from Eloqua for a number of reasons (inactivity, unsubscribe, etc). Once removed the contacts are no longer in the contact table and can not be pulled into segments via filters.

We needed an overall current unsubscription list overtime for an upcoming system integration.

If you are trying to access this same information it can be found under Setup > PowerTools (Screen shot from our specific license of Eloqua, thx for heads up Vickie Le Sellin that some licenses may have different options.)

Then Select Overall Current Unsubscription List (All Time)

This will allow you to download a spreadsheet containing all of the data. Note: Records removed from the system will likely only contain the email address and removal date. Unsubscribes still in the contact table provide greater detail.

HIGH FIVE to @Michael Green on my team for figuring this out. I couldn't find it so I wanted to document here for next time.

cc Leyla Farah -

Is it possible to peruse the job listing by locations?

I regularly schedule reports for email subscription delivery in Insight and I'm wondering if there's a way to check whether those reports were successfully delivered. In E9 you could run a delivery history report, but I'm not seeing anything similar in Insight. Am I missing something? Any help would be much appreciated.

In today's post, we're going to share a C# library that simplifies interactions with Eloqua's REST API.

The client is open source under the Apache License and currently supports the following objects :

• Email
• Sending Email
• Account
• Contact
• Custom Object
• Contact List
• Landing Page
• Microsite
• Contact Activity
• Content Section
• Dynamic Content

We're sharing this with the community in the hope that you'll help drive its development. We've started with a few basic types and welcome suggestions from the community for more.

This is an open project, so please feel free to submit any requests or changes.

Getting Started

The project is available here on Github. To get started, build the project and reference the following dll in your application : Eloqua.Api.Rest.dll

Usage

Create Client

var client = new Eloqua.Rest.Api.ClientLibrary.Client("site", "user", "pass");

GET (item)

int emailId = 1;
Email email = client.Assets.Email.Get(emailId);

GET (list)

List<Email> emails = client.Assets.Email.Get("searchTerm", pageNumber, pageSize);

POST

Email email = new Email() { ... };
email = client.Assets.Email.Post(Email);

PUT

Email email = new Email() { ... };
email = client.Assets.Email.Put(Email);

DELETE

int emailId = 1;
client.Assets.Email.Delete(emailId);

License

The project is intended for both open source and commercial environments.

Please note that the REST API is not yet public and the code samples available here are my own work. I'll be glad to help support and fix issues in the code, but please understand that Eloqua will not be able to support this - as it is my own.

Thanks,
Fred

We are working with a client who has mandated that all forms will be Eloqua-hosted forms. In the event that I need to create a registration on one of our websites but need to post within Eloqua as well, I've been told it still needs to be an Eloqua-hosted form. Has anyone else found themselves in this position and if so, are there work arounds? I was thinking maybe I could create a second form behind the scenes so that we'd actually be submitting 2 forms, one to Eloqua and the other to our registration database. Any thoughts?

If you’ve had a good SmartStart, it’s very likely that everything is fine with your Eloqua system.  But over time, there are processes that you don’t always look at, and those things might not be responding the way you need them to. 

Systems and processes degrade over time. Data degrades over time. New people may not have gotten adequate training, and sometimes, you just don’t know what you don’t know.

And just like a finely-tuned engine that you haven’t looked at for a while, Eloqua can get out of tune.

That’s why an Eloqua “Health Check” can be so important. A proper “Health Check” can answer so many questions for you, and help put you on the right footing to move forward confidently.

We invite you to watch our video and learn the importance of the ‘Health Check’ for your organization:

For more information visit www.4ThoughtMarketing.com, or call 1-888-ELOQUA4 (888-356-7824) or email info@4ThoughtMarketing.com

Does anyone else have problems rendering responsive emails in Android clients? We seem to be having various issues with this, and I wonder if you have found any solutions.

Thanks!
Andrew

Eloqua will soon be exposing our web services in the form of REST Resources. Eloqua already provides a web services API, well suited for integrated development environments like Eclipse and Visual Studio. These IDEs provide toolkits that can generate service proxies, making web services easy to use. The problem is that web services can be a challenge to work with when we don't have these proxies. REST APIs offer a lightweight alternative to web services and are easy to use with languages like Ruby and PHP.

In this post, we'll walk through a simple example in PHP to demonstrate how easy it is to work with the REST API. The only prerequisites are PHP + cURL. The code sample invokes an HTTP GET request with basic authentication to retrieve a list of Emails from the Eloqua application. The use cases vary, but we’re essentially providing a hook for retrieving a list of Eloqua Emails and displaying their Content. In future posts, we’ll discuss how to manage the content and deliver the email using the REST API. For now, let's get started with a simple request to Eloqua's REST API :

First, you’ll need user credentials for the API

// Basic Auth API Credentials
$user = "CompanyName\User.Name";
$password = "xxxxxx";

Now let’s provide a function that given a URL endpoint will invoke an HTTP GET request decorated with basic HTTP authentication headers and returns the API response.

function get_request($user, $password, $url)
{       // create the cURL resource       $ch = curl_init();       // set cURL options       curl_setopt($ch, CURLOPT_URL, $url);       // basic authentication       curl_setopt($ch, CURLOPT_USERPWD, $user . ':' . $password);       // execute request and retrieve the response       $data = curl_exec($ch);       // close resources and return the response       curl_close($ch);       return json_decode($data);
}

Now, let’s get some data...

// Search for Emails with name containing *Demand*
$emails = get_request($user, $password, "https://secure.eloqua.com/API/REST/1.0/assets/emails?search=*Demand*&page=1&count=50&depth=minimal");

And display the results

// Display the name and id of each email
foreach($emails['elements'] as $item)
{       print ('Email:'. $item['name'] . $item['id']);
}

Invoke another get request to retrieve an individual Email

// Get an Email
$email = get_request($user, $password, "https://secure.eloqua.com/API/REST/1.0/assets/email/111?depth=complete");

Finally, let's output the body of the Email

// print the Body of the Email
print('Email HTML Body : ' . $email->htmlContent->htmlBody);

I hope this was a helpful introduction to the REST API and how easy it is to work with. We'll explore more of the REST API in future posts.

Thanks,

Fred

Getting ready to turn off Marketo. We have a separate sub-domain set up for each, and I would like to set up 301's to redirect the Marketo landing page visitors to the Eloqua version.  My web developer is saying that this is not possible. Just want a sanity check to make sure that is the case. Anyone have experience with this?