MKTO cookie question - known vs unknown visitor

[Anonymous]

Can someone please help me understand whether a visitor would appear as a known or unknown visitor to MKTO in this scenario:

1. Lead registers on a MKTO form and gets cookied into MKTO.  The form uses AJAX/Javascript to communicate with another system to create a userid to our knowledgebase using the information submitted on the MKTO landing page.  The only way to get a login to the knowledgebase would be through the MKTO landing page.
2. The other system has the MKTO tracking snippet embedded on it so if the MKTO cookie is in place, then when the user logs into the knowledgebase, we have visibility to the pages that the user visits.
3. What happens if the user deletes their MKTO cookie before they login to the knowledgebase?  The login screen to the knowledgebase is not integrated with MKTO, but the MKTO tracking snippet is embedded in the knowledgebase.  Does that visitor appear to MKTO as an unknown visitor?  Or does the MKTO cookie have some way to see the email address from the knowledgebase login field?  Basically, I'm looking for an easy way for MKTO see the email address of the user when the login to a third-party system occurs.
4. Related to this question, is there any way to restrict access to content based on being a known visitor to MKTO?

Thanks in advance for any advice.

[Jep_Castelein2 · Accepted solution]

3. unknown visitor. You could do an Associate Lead call with the Munchkin API on login to the knowledge base