We recommend watching this 40 second demo:
You can use eloqua.log("Message here...") anywhere in your code.
This built-in function logs whatever you pass to it. This message will be visible in 2 places:
When you test your feature, it will display in a blue info box
In the 'Logs' tab after your feature runs in a campaign or program
Every Custom Decision starts with eloqua.each(...).
This function will loop over all the contacts sent by Eloqua. The contact object properties & functions listed below are available inside this wrapper. The contact object inside this loop will refer to each contact, one at a time.
The contact.done function sends an outcome (true or false) back to Eloqua.
Send contact.done(true) to return a 'yes' decision-outcome, and contact.done(false) to return a 'no' outcome.
The contact.fields object lets you access the contact's fields from the Eloqua database:
Fields must be accessed using their internal field-name.
The editor's autocomplete makes this extremely easy. Just start typing and all the fields in the database (including custom fields) will be available & type-checked.
The contact.error function elegantly handles errors:
Specifically, it does 2 things:
It lets Eloqua know your function has errored (for that contact). If you chose a 'route errors' step in your campaign/program, the contact will be sent there.
The error message will be elegantly displayed when you test your function, or in the Log tab.
This basic example just creates a random 50:50 split. This can be used for split-testing.
The below example demonstrates using a Custom Decision powered by an external API. Specifically - this uses a tool called 'Yes or No' to randomly make the decision for us.
Note that the important part is still that we return either contact.done(true) or contact.done(false) for each contact, which sends the result back to Eloqua as yes or no decision outcomes.
In the 'Action' tab if you click on the more icon ('...'), you can select Advanced Settings. One of these settings is a config object. This is designed for a situation where you want to re-use the same code, but pass different "settings" into it each time. The entire config object is available as eloqua.config - therefore you can access whatever properties you give it:
Again - the config is unique to each instance of your app, and is designed to allow re-use.
You may want to have some values stored outside of your code. E.g. API keys. This can be useful for security (less visible), and also means they can be centrally maintained even if they are used in many functions. You can set global config through the Instant Marketing global settings. An object with all the global settings is available as eloqua.globals - therefore you can access whatever global properties you setup: