Deprecate in favor of Marketo MA

Hey
The marketo munchkin module provides a way of injecting the munchkin js into your page and an API for associating the tracking cookie with data (e.g. from a form submission) that identifies a lead.

This module integrates marketo munchking with webforms, user profiles, and potentially other systems. It also provides an alternative means of communicating with marketo (via their SOAP API), which may be more reliable (we've had a lot of issues with the munchkin API just failing randomly).

Ideally, I'd love to see this integrated with marketo munchkin (once it's ready, we're still in pre-release development, and the latest commit is broken...) -- I was goign to post an issue in the marketo munchkin issue queue before promoting this to a full project. If you're interested in combining, let me know and we'll figure out the best way to do so...

Moving this to the Munchkin Issue Queue

Copying this over from the other thread -- For reference -- the other project is http://drupal.org/sandbox/wodenx/1891684.

Currently "Marketo" offers the following enhancements
- The ability to submit data to Marketo via their SOAP API (as an alternative to the Munchkin API)
- "Webform" integration - the ability to mark any webform component for inclusion, and send those data automatically on form submission.
Planned for the near future:
- Field integration - the ability to mark field instances, and to trigger their submission to marketo on entity save (will probably do this via rules).
- Marketo field validation - the ability to query Marketo via the SOAP API for a list of valid field keys, to ensure the accuracy of the mappings between Drupal fields and Marketo fields.

As it is, the "Marketo" module has no dependency on "Marketo Munchkin" -- it can be used exclusively in SOAP mode. But, if Munchkin is installed, it offers the option to use Munchkin to submit the data. So integration could be as simple as incorporating the munchkin funcitonality as another submodule.

However, I think there are some architectural advantages to a deeper integration -- for example, to retain independence "Marketo" keeps its own record of the marketo primay key email -- there's no need for this.

I do have a couple of architectural questions about Munchkin.
- Why do you store data that's queued for submission in the session rather than in a static variable? Are there cases where you'd want to collect data over several requests before submission? As it is, you inject the JS on every page build.
- What's the rationale behind storing a "type" key in "marketo-munchkin-submit'" and having a separate "hook_marketo_create_TYPE_data()"? Any module (including the one that set the initial value in "marketo-munchkin-submit") cab already add data via hook_marketo_create_data().
- The "Marketo" module takes a slightly different approach for accumulating data - it maintains its own key-value store (in a static variable), to which any module can add with a function call. It then passes the accumulated store through drupal alter to allow last minute alterations. What do you think are the disadvantages of this approach.

Again - I'm willing to integrate as deeply or as minimally as you like. We can even keep these as separate projects which refer to each other if you prefer. It's all up to you.

+1 for this idea.

I'm using both these modules together because I 1) need to post the data via SOAP to Marketo and 2) I want all my users cookied via Munchkin. Would love to see these two projects come together in the future :)

Just found this thread, guess I didn't do a good job searching.. I've been using marketo_munchkin for a while now and recently started working on a module that combines munchkin and soap capability. As I went to create the sandbox I found the project by wodenx which is very similar. Would love to combine all this together into a single package.

http://drupal.org/sandbox/jyokum/1949342