Countdown timers and personalized images for Oracle Eloqua

A countdown in an Oracle Eloqua email is a signed timer image with a fixed address, pasted into the email as it is. One address serves every contact, and each sees the time left at their own open. For a different deadline per region or per event, use Eloqua dynamic content with one timer per variant. A deadline per individual contact is not something Eloqua’s documented field merges can carry, and this page explains why.

That last sentence is the one most worth knowing before you plan a campaign, so it comes first rather than last. The rest is where the image goes, which Eloqua features can vary it, and what a corporate Outlook audience sees. For the wider decision, the enterprise guide covers what a vendor review asks; Oracle Responsys, Marketo Engage and Iterable have their own pages.

Why Eloqua cannot carry a timer per contact

On other platforms, a per-person countdown works by storing one complete signed address per person in a contact field and making that field the whole image source. Eloqua’s own documentation closes that route twice.

First, where a merge may sit. Oracle’s Field merge examples limits a merge used in a web address to the part “after the ? in the URL string”, and adds: “You cannot use field merges as part of the actual URL path.” A field that holds the whole address would put the merge before the question mark, which that page rules out.

Second, what a merge after the question mark would do. Every image address here carries an HMAC-SHA256 signature over its path and every query parameter. A value Eloqua writes into the query at send time is a value the signature never saw, so every contact gets a grey “image unavailable” card, at HTTP 200, with no error anywhere. The same Oracle page adds that “field merge values are always HTML encoded”, images included.

So in Eloqua, the timer’s address goes in exactly as it was signed. That is not a small loss, and I would rather say so here than let a campaign find out. A team that needs a deadline per contact, a renewal date for example, sends that email from a platform that can hold a per-person address, or shows the date as merged body text beside a shared timer.

The shared timer, on every plan

For a webinar, an event or an early-bird price, every contact counts to the same moment, and this is the case Eloqua handles well. Publish the timer, copy the signed address, and paste the snippet into the email’s HTML where the banner would sit. The free plan includes it. Because the time left is drawn when each mail client fetches the picture, one address still shows each reader the right number at their own open.

Personalize around the image rather than in it. In a link to your own page, Oracle documents a merge after the question mark. In the Design Editor, Oracle’s field merge page for the Design Editor says links use an HTML-compliant tilde syntax, ~~eloqua..type--emailfield..syntax--field_merge_name~~, and “does not use the <span class="eloquaemail">field_merge_name</span> format”. Outside it, a field merge is a <span class=eloquaemail> element, which is body text: an element cannot sit inside an HTML attribute, so the alt text stays plain.

One more note from Oracle, because it is the page an earlier version of this site cited. encodeFor=url is documented on the page for query string field merges, and that page says those merges “are not available for use on landing pages, in emails”. So this page does not rely on it for email, and neither should a snippet.

The dashboard’s snippet generator does not write Eloqua field merges. Eloqua is not one of the twelve platforms on its publish screen, so copy the signed address and paste it as above.

A timer per region or per event, with dynamic content

Dynamic content is how an Eloqua email shows different people different blocks, and each block can carry its own timer with its own fixed address. Oracle’s Creating dynamic content lists the rule types: compare contact fields, compare account fields, a linked record in a custom object, and a linked record in an event. It also says the full editor handles images and HTML: “If you want to add images, field merges, or hyperlinks, or edit HTML code, click Full to open the rich text editor.”

Two uses come up in B2B programmes.

A deadline per region. A promotion that closes at 17:00 local time in each region is three deadlines, not one. Publish three timers, or one template published with three deadlines, and give each dynamic content rule its own address. Oracle’s order matters: “Eloqua evaluates the rules from the top down. If a contact doesn’t meet any of the rule conditions, then the default content is used.” Set the default first, as Oracle says to.

A countdown per event session. The event rule type, “Has Linked Record in Event”, lets registrants for one session see that session’s timer. A three-session webinar series is three timers and three rules, and a registrant sees the one they signed up for. The webinar registration page has designs for it.

The limits are Eloqua’s. A rule cannot “search for a particular value in a large text field”, and this is a handful of groups, not thousands. A rule per contact is not a workable way to fake a per-contact timer.

What your contacts will see

B2B lists read on corporate Outlook more often than consumer lists do. Microsoft’s support page says, “If only the first frame of the animation appears, you have animations, or animated GIFs, disabled”, and classic Outlook for Windows shows the first frame regardless. The first frame of every timer here is a complete, correct countdown, so that contact sees a still with the right number.

Corporate Outlook also often blocks images until the reader downloads them, which is what the alt text is for. Since the alt text in Eloqua is plain, write it as the message itself, “Early bird pricing ends Friday at 17:00”, and put the same date in body text next to the image. The Outlook page goes through it by version, from Microsoft’s documentation rather than from a test in each inbox.

Test before you send

Preview the email against a contact from each dynamic content group, and against one who matches no rule, to see the default. Check the image address in the rendered HTML matches the published one exactly. Then send a test to an Outlook mailbox and a web mailbox.

Questions and answers

Can Oracle Eloqua show a countdown timer?

Yes, as an image from a timer service with a fixed signed address, pasted into the email. Every contact sees the time left at their own open. Eloqua has no timer block of its own.

Can I give each Eloqua contact their own deadline?

Not through a field merge. Oracle documents merges in a URL only after the question mark, never in the path, and a merge in the query of a signed address breaks its signature. Use dynamic content for a deadline per group, or send per-contact deadlines from a platform that can store a complete address per person.

Can a field merge go in the timer’s alt text?

No. Outside the Design Editor’s link syntax, an Eloqua field merge is an element, and an element cannot sit inside an HTML attribute. Write the alt text as plain words that carry the deadline.

Which plan does an Eloqua timer need?

The shared timer is on the free plan, which has 5,000 image opens a month and three live images at a time, so three regional variants fit. A fourth needs Starter, which has no template limit. Pricing has the rest.