Munchkin Strategy

[Anonymous]

Hi Everyone,  Has anyone ever really nailed a solid Munchkin strategy?  We all know the basics ... but does anyone have a particular approach with which they decided where to and where not to deploy munchkin?  This is especially important to clients with A LOT of traffic.  The mass deployment of the code is just not the right thing to do.  I have a few thoughts, I was hoping to crowdsource some more:

1.  Yes where ever there is demand Gen Opportunity or where the digital body language is valuable
2.  No in high transaction not buying behavior pages like Support, Customer Logins etc
3.  Some places are debatable like the careers page

Other thoughts? . . . Thanks!
M

[Josh_Hill13]

Maneeza,

Your approach is good. I'd think it would depend on the situation. At a saas firm that wants to integrate in product behaviors, keeping code on Support and Login is necessary.

I agree to keep the code off low value or negative value pages - then you don't have to score them at all.

[Anonymous]

A counterpoint would be to have a Munchkin on low value pages in terms of Marketo because it can help with lead scoring. For example, if somebody is visiting your jobs page it might be a signal that they are not a good prospect. That said, I just wanted to provide a balanced prospective, and I do not have a strong opinion on this.