How to set aquisition with external form using Munchkin js

[Anonymous]

Acquisition isn't one of the fields in the field export.

How to set aquisition program when using Munchkin.munchkinFunction('associateLead', ...

Thanks ~

[SanfordWhiteman]

You can't set the Acquisition Program directly.  Send a custom field and then set the AP in a Flow step.

I would also recommend using the Forms 2.0 API to submit the form, rather than the Munchkin API, even if you are using a totally custom form. That'll give you an actual ​Filled Out Form ​event and will supply the URL that hosts the form, so you can take more conditional actions without having to create extra custom fields.

[Anonymous]

Or on visit page, kick off the actions

Seems like too much hacking to customize forms fully and sometimes, you want an embedded form.

[SanfordWhiteman]

Or on visit page, kick off the actions

Sure, you can trigger on Visit Web Page with various conditions if that's applicable, but Marketo's URL parser is unsophisticated (read: nonexistent) and you didn't say where you were deriving the Acquisition Program from.

Seems like too much hacking to customize forms fully and sometimes, you want an embedded form.

Not sure how that disagrees with my recommendation -- I'm talking about using a totally custom (non-Marketo, raw HTML) form but using the Forms 2.0 API to submit the data to Marketo.

When you use the Forms 2.0 API you always get the current URL sent as the Referrer, so you wouldn't need to look for the VWP event.

[Anonymous]

Is it me or is the javascript API too buggy to use?

I have an external form to synclead and visitweb to trigger campaign. the problem is, if different users use the same computer - there seems to be an identity issue. The only way it will work is if i click on an email from another campaign (i imagine which sets my identity) then fill out the form; however, if someone else fills the same form on my comp, no info is logged

[SanfordWhiteman]

Is it me or is the javascript API too buggy to use?

The Munchkin API or the Forms 2.0 API?

Neither one is too buggy to use, but you have to get to know the expected behavior. I try to stay away from the Munchkin associateLead API because there's almost nothing it gives you that a hidden form post can't (except a headache in having to fetch the hashkey separately). But I use the rest of both APIs profusely.

if different users use the same computer - there seems to be an identity issue. The only way it will work is if i click on an email from another campaign (i imagine which sets my identity) then fill out the form; however, if someone else fills the same form on my comp

Filling out a form and clicking an email have different consequences for backward/forward association, but the behavior is always predictable.

I have a feeling that having cookieAnon: false is tripping you up more than it's helping.  Why are you doing this, specifically?

[Anonymous]

Munchkin* API correct. I thought the cookieannon was to support those people that dont want to be tracked?

[Anonymous]

my issue - seems the email wasnt being sent ... html 5 type using jquery issue. Still woulda been great if an error message was returned. I dont see documentation for that. Thanks ~

[SanfordWhiteman]

That's another reason why the Forms 2.0 API is superior: it isn't fire-and-forget but is fully cross-domain with an onSuccess event.

[Anonymous]

I'd love to use but its a hurdle to fully customize the design. where abide or jquery validation seems more robust