Marketo form on non-Marketo page questions

[Anonymous]

Hi,

Our organization is using different domains between Marketo i-frame (Contact Us) and company website. We encounter an issue to track whole lead activities if he/she has activities across two domains due to cross-domain cookie. Two leads will be generated separately. One of them is anonymous lead with activities on the company website, and the other one is identified lead with name with registration activity on Contact Us form.

We were suggested to use the concept of "Marketo form on non-Marketo page". We did review the article (https://community.marketo.com/MarketoArticle?id=kA050000000KyqgCAC) and would like to confirm our understanding. What we are understanding is that there is an another way to manage a Marketo form with this concept. In that way, by copying page source of landing page (HTML), we can make a Marketo form appear on the company website and can imply to have this form in the same domain as company website. The ability of Marketo form will be still remained to track lead activities with munchkin code, and the lead activities can be tracked for the whole session of single browser cookie. 

Our questions
1. Is our understanding above correct ?
2. Does the lead information still pass through Marketo channel and handled by Marketo database similar to what we are using Marketo i-frame now ?
3. From our research, will we lose functionalities of Progressive Profiling and Pre-Population ?
4. In terms of security perspective, how do we manage spam filtering on non-Marketo landing page form ? I understand that using i-frame, Marketo has protection with hidden field.
5. In the near future, if we implement SSL with all Marketo landing page, is it still applicable to use this concept of "Marketo form on non-Marketo page" with no conflicts and impacts ? Do we have to re-visit and correct page source (HTML) at every website we implement this concept ?

Thank you very much in advance for all of your responses.
Kind Regards,
Taworn D.

[Anonymous]

Hi Taworn,

Just want to clarify a couple things, and please don't take offense if this is too basic. I'd rather be on the safe side and give you too much information rather than not enough.

If they truly are on two separate domains such as such as http://go.marketo-domain.com vs http://corp-site.com and not subdomains, then yes you will have two cookies generated. The form submit will associate the cookie/activities for the domain the form is submitted upon. That being said, instead of using the form code on a non-Marketo page, you may want to consider creating a cname and a domain alias in Marketo for the corporate site. You could then have the iframe pointed to http://cname.corp-site.com. In this scenario the activity captured for the corp site would be associated upon form submit and you don't lose pre-fill or progressive profiling.

If you'd like to get really advanced you may want to consider associating both domains upon one form submit so you gather activity from both. Here are the answers to your questions:

1. Above response I believe answers this
2. The lead info will submit to the database and will show as a form submission on the lead record, therefore you can trigger flows off this action.
3. Yes, you will lose progressive profiling and pre-fill
4. Because it is essentially a basic html form at this point, you can do whatever sort of validation that you like from the standard Marketo validation script to implementing a captcha solution.
5. Using a landing page on the same domain as suggested above will resolve this as long as the SSL is set up properly.