We would like to add custom activities via the API based on user behaviors in our native mobile application (which is geared toward providing content).
I'm curious if anyone has done this and what type of activities you're logging. I know it's very app-specific, but I just want to make sure I am considering the possibilities.
Really good discussion here. We're in a similar situation. Our events team has built a custom mobile app to be used at select off-site events (it's a "Digital Dinner" app that allows users to register for the event, select their menu options, check into the event, and engage with campaign-specific content (when they click on this content, they are taken to our website)).
I'm meeting with our development team this week to discuss how we can integrate this activity into Marketo. Is all of the information needed contained on the Marketo Developer site? Sanford Whiteman, how is Munchkin integrated within the app? I couldn't find this on the developer site. Also, are you saying when a user taps on an item - e.g., a link to the content page on our website - that's not considered a regular "click"?
Is all of the information needed contained on the Marketo Developer site?
Depends. If you simply run Munchkin in a (hidden) web view, it's a straightforward use of the Munchkin API. If you make your own HTTP requests to the Munchkin endpoints, it takes some tinkering. But the API is very simple. Like any analytics API, once you get rid of the browser-compatibility chaff, the async Ajax library, the event listeners, and so on, you find a standard tracking pixel.
Sanford Whiteman, how is Munchkin integrated within the app? I couldn't find this on the developer site. Also, are you saying when a user taps on an item - e.g., a link to the content page on our website - that's not considered a regular "click"?
A tap within a native app wouldn't be logged as a Munchkin hit by itself, unless that tap were within an embedded web view (just like in a Windows desktop app: standard UI buttons aren't connected to the web, but if the app happens to use an embedded IE instance, it's more like clicking on a web page).
If the app actually opens a page in the device browser (Mobile Safari or Android Browser) then you don't need to do anything within the app at all, as the logging would happen in the browser as it usually does.