Same Landing Page, Different Domain Alias, rendering incorrectly

[Anonymous]

Hi,

I'm encountering a strange problem.  We have an I've created a landing page (based on a knak.io template), and it looks great, renders correctly, etc..

The problem occurs when I go to view the same page using the domain alias we have set up.  It renders fine in all browsers but Chrome.  In Chrome, it looks as though I'm viewing it on mobile.

So the landing page is perfect on our regular domain, but when I go to the same landing page using our domain alias - the one I need to be using for this marketing effort - it is rendering incorrectly in Chrome.

Has anyone come across a similar issue?

thanks!

[SanfordWhiteman]

Please give us the links... that's how we look into problems like this.

[Anonymous]

Thank you.

Here are the links:

http://go.telerx.com/Physician_Social_Listening.html

http://info.c3ihc.com/Physician_Social_Listening.html

The info.c3ihc.com one is the one I need to use for this campaign, but is rendering incorrectly in Chrome.

thanks!

[Josh_Hill13]

What do you mean by domain alias? Did you test this page on your main site and then move it to Marketo?

Are your Chrome settings different?

[Anonymous]

Thanks Josh.
I may be using the terminology incorrectly.  Our main marketo domain is go.telerx.com.  We acquired a company a few years ago and have a new CNAME - info.c3ihc.com for use in marketing this new brand.  I created a Domain Alias rule for this, and have not had any trouble with other landing pages.

This is the first time I've come up against the issue of the page looking one way with the original go.teler.com URL, and differently with the new info.c3ihc.com URL.

[Grégoire_Miche2 · Accepted solution]

Hi Krista,

Just tested it on chrome on Windows and Mac, and it displays exactly the same on both environments, and in the normal desktop format.

Are you sure you do not have the Chrome Device toolbar activated? It enables testing the rendering of an LP on various devices.

-Greg

[Anonymous]

Thank you! That seems to have fixed the issue.  Thanks all for your help!