Pre-conversion events for recruiting leads

[Anonymous]

Hi,

We want to see all of a user's activity on the website before they apply for a job (convert) – currently, on a user activity history in Marketo all I see is post-conversion (after conversion) activity.

Thanks

[Grégoire_Miche2]

Hi Ivan,

This question belongs to the Products section.

Read this ** PLEASE READ BEFORE POSTING YOUR MARKETO PRODUCT QUESTIONS HERE **​ to learn more.

I suspect you munchkin cookie is set to track only known lead activity. What is your website URL ?

-Greg

[Anonymous]

Yes, the Url is for example this https://www.wizeline.com/careers/apply?gh_jid=248895 but the thing is that i want to save when the user visit blog, solutions, products or any page before apply for a job and be able to see the logs in Activity Log in marketo.

Any suggestion?

Regards.

[SanfordWhiteman]

Munchkin is loading fine on your main document and shared across all subdomains of wizeline.com. But your job application forms are loading from (and posting to) a different parent domain, greenhouse.io.  Cookies are not shared across domains. This is an age-old browser security rule.

[Anonymous]

So if we change the greenhouse.io form by own one, we can save user's activity on the website with Munchkin? do you know some documentation that help me to achieve that?

[Josh_Hill13]

Sanford would know the details, but you could do a few things:

1. integrate Greenhouse and Marketo to pass back applicant data to match their email and therefore see their entire history.
2. match applicant data back manually or with a sheet.
3. do some fancy jquery/munchkin stuff and match the data at the time of form submission.

I'm sure this is where Sanford would tell me that at least #3 is a security risk.

[SanfordWhiteman]

3. do some fancy jquery/munchkin stuff and match the data at the time of form submission.

I'm sure this is where Sanford would tell me that at least #3 is a security risk.

Nah, not really. But the problem here is you're working with a system you don't control (Greenhouse) and passing data between frames requires complete cooperation between the technologies on both sides.  It can be done securely but doing it at all is going to be more difficult than using a Marketo form and/or the Forms JS API.

[SanfordWhiteman]

Ivan, Marketo forms are designed to be embedded on non-Marketo sites (as well as on Marketo LPs). Every form comes with an embed code out-of-the-box. The Forms 2.0 editor offers a nice set of code-free features (validation, visibility rules) and a JS API that you can use to create incredibly robust custom behaviors. (You can see myriad examples of the latter by searching the Community, most of them contributed by yours truly.)

That being said, trying to match an existing form feature-by-feature, pixel-by-pixel with a Marketo form requires an experienced developer.