Add favicon and page title in the Eloqua responsive landing page builder
I am currently creating some Eloqua landing page templates for a client using the new (today is the 13th May 2019) Eloqua responsive landing page builder.
First of all the new Eloqua landing page builder is really pretty cool – so well done to the Oracle Eloqua development team for coming out with this! Five stars for you!
The Eloqua landing page builder makes it really easy for non-technical users to create bulletproof landing pages. It has lots of features, a nice drag and drop interface, offers a load of flexibility and best of all is actually responsive. You may laugh but the old editor was awful and the templates Oracle offered us were nasty. I don’t like to trash talk the Eloqua platform but I feel that now the old landing page editor has nearly been resigned to the dustbin it’s ok.
Enough of the praise. It does have two things I noticed straight off were lacking. First of all it has no way of setting the page title and secondly it doesn’t allow you to set the favicon.
Since I am on the train back home I thought I would share with you the way I managed to set the page title and the favicon in a real quick blog post.
Background: Hopefully you know what a favicon and a page title are but just in case you don’t here goes. A favicon is the little image that shows up in your browser tab. It is mainly a branding thing. The page title is the text that shows up in that tab.
Disclaimer: I searched topliners initially and found three posts with different solutions. I tested the two that looked more advanced but for me they didn’t seem to work – therefore I have given you the simplest solution that I know for sure works.
Step 1. Add a Custom Code content area at the top of the landing page
Click on the Custom Code content area in the Eloqua responsive landing page editor then drag it over on to the empty cell
Step 2. Click in to the Custom Code content block that you have just set
Click into the Custom Code content block and an editor will appear
Step 3. Modify the code below and drop it in
<title>Page Title – Site Name</title>
<link rel=”shortcut icon” type=”image/x-icon” href=”https://your.link.to/your/favicon.ico” />
Conclusion:
This simple three step process will set both your title and favicon every time on your Eloqua landing pages.
Let's talk Eloqua!
Eloqua Feature: Eloqua form spam protection
There is hell and then there is another place below hell. That is where those pesky little spambots live during the day coming out at night to wreak havoc on your forms filling your lead que with promises of bitcoin riches, SEO expert claims and other such nonsense....
Designing an off the shelf lead nurture engine for Oracle
A few years back Oracle asked me to design an off the shelf partner lead nurturing engine that they could use to enable their partners to market to their own databases on a shared instance of Eloqua. They essentially wanted me to architect what I had created when I...
Eloqua Blog: Lead Nurturing Markie – Runner Up
I am going to switch tack with some more theoretical posts rather than the technical ones. Before I begin though I feel it is appropriate to establish my credibility though in the field as a marketer. It was 2011 and I returned to work at Axios Systems back up in...
Best time to send email: Eloqua Send Time Optimization
As a marketer you have so many decisions you need to make when planning your Eloqua email campaign, namely: The subject line The call to action Content personalization Send time Email send time is the one decision that is a problem for even the most experienced email...
The title tag is set by the title of the page so not necessary to set it twice. Since the favico is set using code that is embedded in the body, it’s not a cross-browser solution. Appreciate the effort though.
Unless I am mistaken manipulating the title tag wasn’t an option until the last update. The favicon is the best I could get it.
Greg, have you experienced incompatibility lately with favicons not rendering in Chrome? If so, how have you resolved that? Our pages work fine in FF, but show default icon in Chrome.