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.
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 Training: 101 Contact upload
1.1 Eloqua Contact Upload Overview There are two parts to a contact upload in Eloqua that that need to be considered: Contact upload Interest list association It is essential that you follow through with each of the procedures listed when importing contacts to the...
Eloqua Blog Question: What topics shall I cover next?
It's been ages since I last wrote an article and posted it to you but then again, I hope you haven't been chained to your desk all summer and you got to have some amazing summer adventures! I had a mixed summer but on the positive side am coming to the end of...
Eloqua Picklists – ISO Code, EN, NL, FR, DE & ES Countries
Recently I have been working on form migrations and whilst this post will concentrate on Eloqua and Eloqua picklists it should be noted that you can use this list for any platform really. In Eloqua as with any other system, a picklist is a list with two columns: Name...
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.