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.
Looking for some Eloqua help?
Schedule a call 📅
Let's talk Eloqua!
Eloqua Blog: New Topics
It has come to the time of year where I need to ask you all what you want me to write about next. Please use the poll below to vote for the topics you want covered, you can also add your own topics... so...
Eloqua Development: Automatically add Query String to all pages links
Background to the problem One of the big problems that marketing has when it comes to using their analytics platforms is that essentially what they have found is that the way they have been setting up their web analytics software means that whenever a contact hits one...
Eloqua Devops: Free Eloqua devops certification course
Eloqua Devops crash course (DISCLAIMER - The examples used in here are satirical; past, present and future employers – I really enjoy my job and it’s more than a job to me but I have to let my sense of humour out once a while) By the end of this post you will be able...
Eloqua Blog: Developing an Eloqua naming convention generator tool
The Eloqua naming convention generator I had a reader ping me a message asking me if I could give them some advice on how to develop and Eloqua naming convention and a tool that they could use time and time again to generate the right name for any Eloqua asset every...
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.