Robert_Kelen3

I think it would be worth it if I could get it work, but alas, I can't seem to stop it from re-appending the "extra stuff".

You've gotta get the fallback page to be just /pagename.html. The UI will change this to http://pagename.html. So you need to replay the request and take out the extra stuff.Actually, even with the replay (UI hack) the system still appears to append the 'http:/' in a way that prevents this approach ...

But in the Marketo LP example here, pagename.html (which let's assume was successfully and forcibly placed by the UI hack) is still the same content whether it's being viewed from info.brand_a.com/pagename.html or info.brand_b.com/pagename.html.What's still needed to give the user an actual brand_a ...

Makes sense. Then the JS from your original post is somehow adapted to sort whatever one calls the middle part of the domain name instead (choosing the .brand_a. or .brand_b. part)? Even still, aren't we talking about the same single page in Marketo?

Well, I'm no programmer, but that all made sense to me, and I do understand what you mean about hacking the UI now. Thank you!What sort of hack is required to achieve the desired effect in this example?

Is "hacking the UI" something you've written on elsewhere? Where does this fall on the "lots of work" to "a little Javascript'll do ya" continuum?

Sanford Whiteman, can this approach also be used where there are different top level domains for the multiple domains in question? For example, megabrand.com (and their megabrand instance) has two different Domain Aliases set up for brands they own (let's call them brand_a.com and brand_b.com, with ...

>Thanks Greg. I was so focused on the form-based approach, I missed theobvious.-- --Robert KelenDirector of Partnerships & ServicesLeadous (a Marketo Certified Services Partner)<>612.298.0944 mobilewww.leadous.com | schedule me <>

Thanks Sanford!