Skip navigation
Teiu Codrin

Cloud Action: Form Submit

Posted by Teiu Codrin Jun 14, 2016

There is an app that represents an alternative to the "Send to Cloud Connector" step in Canvases.

The use of it is quite similar to the Cloud Connector one, for doing a form submit. The main visual difference is that the configuration takes part in a pop up window within Eloqua.


This app can be used to generate an artificial form submit within a canvas, for the contacts that pass through the step. See below the configuration window. Fields can be mapped, but also Static values can be set up. The documentation is here.


The app, once installed, can be found in the canvas under the Actions menu. You can also set up a wait step and a list for contacts that have problems when being ran throught the app.

Teiu Codrin

Canvas journey cleanup

Posted by Teiu Codrin Jun 14, 2016

As you noticed, sometimes is hard to troubleshoot contact journeys in canvases that deal with large number activations, because many contacts excluded from email sends from various reasons (master exclude, opted out, bounceback, etc) are remaning stuck in the email boxes along the canvas.


A possible way to keep this neat is to enable the email setting "Automatically route contacts excluded from email send". You can add an unlinked Wait step and a Move To Shared List step on a side of your canvas. Once enabled, the email option will allow you to select a step to tap into and you can select the wait step. This way, excluded contacts will be addded to that list and taken out of the canvas.


This can be used in a few ways, from simple to more fancy:

- one master list for the whole Eloqua instance. This way you will obtain 1 shared list to contain all excluded contacts from email sends along the whole platform;

- one shared list per campaign. This way you can track the effect of this on a campaign by campaign basis;

- by groups, like you make email Groups for Software, Hardware, etc. Each category can have a series of campaigns under it, and you make 1 exclusion shared list per category;

     - these can be later added into a segment for an instant overview;


Another use for the above process would be to use the resulting list(s) for platform related projects, like contact deletions of unreachable contacts in order to keep your database clean and of manageable size.

I find program builder to be a little daunting at times to find issues and how to fix them. I have started using some best practices which may be of use to troubleshoot a problem. Here are a few of my tips for troubleshooting in program builder.

  • Try to break your programs into mini programs with less steps- easier to find errors.
  • Don't be afraid to be overly descriptive of each step function. I will use descriptions like step 998X:Denied Party List
  • Put programs with the most steps into priority mode to speed up integration


  • When encountering an issue start in sequence with the first program and run either "entry history" or "exit history" reports to see where the contacts left the system.

  • After discovering the step where the problem occurred you can reference the description (tip two above) to see what should happen at that step and refer back to the source (a feeder or loaded list or form) to see any anomalies. For example, I had some contacts that were not integrating with SFDC, the step where the problem occurred was step 992x add lead score-  the contacts were not getting a lead score for some reason. It ends up the lead score was never assigned to the contacts because the list I uploaded into Eloqua had a date that was set to a future time ( it actually was accurate but set in EMEA style showing 12/3/16 instead of 3/12/16 in North America) that told the system not to score until after that date. Easy fix but tricky to find.

    Feel free to add a few of your own. I am sure I am missing some great tips from the community and would love to learn more.

Filter Blog

By date: By tag: