Since Eloqua is primarily focused on email marketing and campaign management, SMS messaages are not included as a core, native feature. To address this, I developed a custom Eloqua application that integrates with three major SMS service providers:

• Inmobile
• SMSDK
• Sinch

In the Eloqua campaign canvas, marketers can easily select an SMS Cloud Connector component and drag it onto the campaign workflow. With just a few clicks, they can choose the contact field to merge and design a dynamic message template.

A key feature of this project was the integration of the Mustache templating engine. This was particularly valuable for Eloqua clients who had stringified JSON fields that needed to be dynamically merged into the SMS body. Mustache’s templating capabilities made personalization and dynamic content integration seamless and efficient.

The reporting of the message status was implemented via callback method. Contacts were flagged as successful or failed based on the message delivery outcome and then imported back into Eloqua for tracking and reporting.

This integration streamlined the process of adding SMS to Eloqua campaigns, providing marketers with a simple, effective way to incorporate SMS messaging as part of their multi-channel strategies.

This integration project enabled Eloqua to send push notifications through the multi-channel messaging platform Airship. The integration supported several key use cases:

• Send push message from campaign canvas (scheduled or in-app)
• Send push message from a segment (batch send)
• Send push message on form post
• Import devices to Eloqua
• Collecting and managing response activity

In the Eloqua campaign canvas, marketers could easily drag and drop the Airship Cloud Action component into their campaign workflow. With a few simple steps, users could authenticate, select a mobile app, choose a pre-configured message template from Airship, and target either Android or iOS platforms. Push messages could be scheduled for later or sent immediately to all contacts that flowed through the action step, providing flexibility and ease of use.

Appart from the campaign canvas, marketers can also send push notifications to an entire segment. In the segment view, after defining the segmentation criteria, the integrated Airship interface can be accessed to complete the configuration. Although the setup process is similar, there is a key difference: segment-based pushes are one-time sends to all members of a segment, while in ongoing campaigns, notifications are sent individually as contacts pass through the action step. Technically, this means that in the campaign canvas, the integration backend receives the contact payload directly, whereas for segment pushes, contact data must be fetched from Eloqua.

In addition to sending push messages, the Airship integration supports device import into Eloqua and response activity tracking. Imported devices are stored in Custom Data Objects, while response data is recorded as External Activities. Both data types are used in segmentation and help create more complex workflows based on user interactions.

“Få tiden tilbage” was an interesting projects that took almost 6 month to complete. The client was a public transportation company (DSB) and the concept was focusing on bringing back value to the passengers who experience delays, due to the maintenance work done on the railways.

The first release of the application was managing journeys, where a passenger is able to check in on the start of the journey, and checkout on the end destination, earning a certain amount of minutes based on the rules defined for that specific route. Every journey route had a defined award, and every journey was adding to the total of the credits saved.

Once the saved credits reached over a certain limit, the users were able to use those credits to make an in-app ticket purchase. In the second release of the application, users where able to choose from a specific set of destinations, select a route that they can afford, purchase and save the ticket for later use. The tickets with the QR codes where complied to DSB scanners so that they could be checked for validation while traveling in the trains.

For this project, Nordlid has recieved the Danish Digital Award in the category “Digital Activation”

The objective of this project was to integrate Rich Relevance Customer Experience and Personalization Platform as a standard Eloqua application. The content personalization was implemented using products Recommend and Engage. The main objective was to integrate personalized content into Email Templates by using ‘Cloud Content’ drag’n’drop feature in Eloqua. This would enable marketeer to configure a cloud service so that the content can by generated dynamicaly as email get opened.

There were two types of content types that could be integrated, which are related products and content promotion.

Recommend

Recommend content was handled in such way that the markeeter could search for a specific product (or category) in the user interfrace, while pulling data from the CDO in the Eloqua. The layout for the visual presentation are also placed in Eloqua select drop downs. This allows a marketeer to configure elements in the Eloqua instance and then used them in the Rich Relevance integration in order to construct necessary parameters which are used during the Email rendering.

Engage

Engage content is handled and configured in the similar way, it is slightly simpler to work with since it shows advertisement, banners and similar content.

The main objective of this project was to create an application which would help facilitate event management in Eloqua. In many cases managing events in Eloqua can be a repetitive task, requiring many hours of work in order to setup the necessary logic for an event flow. This application attempts to do exactly that, save the marketeer from manual work and create the assets and the pattern for the participation flow.

During the event creation process, many Eloqua assets are being created and integrated into the campaign canvas. Assets such as Segment, Email, Form, Landing Page, Custom Data Objects and Campaign are created and configured in order to support invitation, registration, unregistration and waiting list email notifications. When a Segment is ready and the Campaign activated on the campaign canvas, the Contacts on that segment would receive an invitation email and by clicking on the registration link, enter the event flow.

A participant can have different status changes such as registered, attended, unregistered and waiting. All these status changes can be initiated within the application and stored in the Custom Data Object in Eloqua. The change of participant status (registered, attended, waiting) are handled via processing steps.

In order to achieve a specific look and feel for the Emails and Landing Pages, Event application supports Assets Templates. This allows a high level of customization and re-usability.