Robert_Kelen3

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!

How do these extra steps (the MktoForms2.whenReady listener, and the empty cookie) differ from the built-in "Disable Munchkin Tracking" template action? Thanks.

Thanks Greg!

Thanks Dan for that last note. The back and forth on Non-trackable landing page is still identifying me was quite a read; I'll have a to give a try to see if I correctly understood all the fine points.