Skip navigation
All Places > Champion Program > Blog > 2015 > February
2015

One of the biggest questions that we hear from our clients is how they should integrate Marketo forms onto their website.  There are several different options on how to do this, and each one of them has their own pros and cons. This post will focus on each option, so that you can make an informed decision on which one is best for you.

Marketo Landing Page + Form

What I really like about Marketo’s landing page editor is it enables Marketers who may not have HTML experience to be able to quickly and easily setup a landing page for their program. Some of you will be able to relate to this next comment, and those are the ones I would especially encourage to go the route of Marketo landing pages: no more waiting weeks for your web team to create a landing page for you, and then days for them to make edits once you’ve seen it live. I personally find that Marketo Landing Pages are the best option for any pages that require a form. They give you the most flexibility and control to do what you need to as a Marketer to succeed. They also give you the most benefits, like form pre-fill, conversion rate statistics and make it easy to integrate into scoring and triggers.

Marketo Form Embedded into iFrame

Now for some of you who have really great and responsive web teams, or who are running websites using WordPress or another user friendly CMS, sometimes this option can be just as good as Option #1. You don’t really lose a lot by using Marketo forms in an iFrame, other than A/B testing of your landing pages. So, you if have an awesome landing page that is optimized for conversion and its built in WordPress, then put a Marketo form onto this page using an iFrame and you’re good to go. There are a few customizations that you will need to make to make it responsive, blend into the parent page and open the follow-up page in a new window, but you can have Marketo forms up and running on your site in no-time.

Marketo Form Embedded using Embed Code

A lot of people, especially developers, were excited when the embed code came out as it made for an ‘easy’ way to post your Marketo forms directly into an existing webpage on your website. Although it makes the integration into your existing site fairly straightforward, it comes with several drawbacks. This includes the fact that your forms will not pre-fill with known prospects data, it is impossible to track conversion rates of your forms and equally as hard to track form submissions via smart lists. Until Marketo resolves these issues, I would not advise going down this path, even if it may make implementation easy.

Non-Marketo Forms Using Marketo APIs

Marketo has a number of API’s that can be used to either call or post data from. I have worked with some clients who will use these APIs to send data to Marketo when their non-Marketo form is submitted. This typically happens when there is another back-end system linked to the form that needs to spin up a trial account or send a confirmation email with third-party information. This can almost always be done using native Marketo forms and with the API’s pushing to these other systems instead of vice versa. Although the APIs are typically an option that are most sought-after when technical people are involved in the discussion, most of the time native Marketo forms with API’s calling information back and forth in the background can be used. Again, I typically do not advise using the APIs unless there is no other way to achieve the results required with native Marketo forms (and there is almost always a way).

Non-Marketo Forms

It’s one thing to use non-Marketo forms and then use API’s to send data into Marketo, and then it is completely another question when there is no communication method into Marketo. One client we work with did not want to use Marketo forms in case the Marketo servers went down or if they ever had to switch to another Marketing Automation vendor. However, they made sure that all data coming through their forms was passed over to Marketo via API’s and clearly indicated the source of all leads. They also integrated the munchkin API into their forms so even the non-Marketo forms could pre-fill and we could grab all the inferred information. Unless you are taking your non-Marketo forms to these lengths, then I would not suggest using non-Marketo forms. It is a lot of extra work just to get them up to parity.

Salesforce Web-to-Lead Forms

Please, just please do not do this. I have yet to encounter a good use-case for this. This is a recipe for creating a lot of duplicates and losing out on all of the great benefits that come from Marketo forms.

Here is a handy cheat sheet that you can use when thinking about which option to select:http://www.revenuepulse.com/wp-content/uploads/2014/11/Marketo-Forms-Table-4.jpg

Logic Lesson for Marketers

Posted by 2118 Feb 18, 2015

In the past few weeks, we covered basic logic lessons for marketers and the finer points of Marketo logic operators. Beyond this, there is a whole world of logic and languages out there. I have seen a lot of “marketing operations” roles that ask for database programming skills. These are typically at very large firms with very large databases. The more you know about these database languages, the more valuable you can become.

Other topic areas and systems to consider to deepen your skill set include:

  • SQL (structured query language)
  • NoSQL
  • “Big Data”
  • Hadoop
  • MS Access Operators
  • Boolean Logic
  • SFDC Apex Code
  • Pentaho/Revenue Cycle Explorer
  • Tableau

If you prefer to stay more of a marketer than a programmer or business intelligence analyst, then just take a few moments to become familiar with the above topics. Know where and when to call in an expert, and you will be sure to become a rockstar.

Marketo-Subscription-Center.jpg

With the launch of the new Forms 2.0 from Marketo, I wanted to update an oldie in Marketo Community; Subscription Management. A Marketo Subscription Center. Below is a presentation I did last February at the Boston Marketo User Group.

The old Marketo subscription center needed JQuery to check and unchecked boxes of the users unsubscribe and choices. This can be daunting to someone who does not have coding experience.

I wanted to focus around creating smart lists and smart campaigns to do the heavy lifting. Having a smart campaign trigger to listen to changes to static lists using custom fields of topics to subscribe to by opting in and opting out. And of course play with the new Forms 2.0. Feel free to download from SlideShare or attached PDF.

Originally written by Steve Moody

A reader asks:

“We use Salesforce and Marketo, and I’m a bit confused with the number of options for attribution. Should we use lead source? Salesforce Campaigns? Marketo’s Acquisition Programs? What is the best practice?”

I hear this question from many companies, and the short answer is “it depends”. I’ll see if I can unpack this a bit and provide a better model of everything without overwhelming you with information.

History of the lead source field

I first started using Salesforce in 2008, and at that time Salesforce Campaigns were not widely adopted, while the lead source field was a standard field on every lead object.

In 2008, there were many issues with the lead source field, and these haven’t really changed since. The fundamental issue seems to be the desire for every company to overload this field with data.

  • Is “Lead Source” the first source of a lead?
  • Is “Lead Source” the first meaningful action a lead takes?
  • Is “Lead Source” the last action a lead takes to become an opportunity?
  • Is “Lead Source” a channel, or a campaign, or something else?
  • Is “Lead Source” a field for marketing to run reports or a field for sales to review a lead before calling them?
  • Should “Lead Source” contain 10 values or 1,000 values?

These questions show the variety of uses that companies usually have for one field; I’ve seen most of these occur within just one company!

If the problem with this isn’t clear, consider these two rules

Field_-_Question_Rules.png

 

 

Salesforce Rule #1: one field for one question

A core rule I apply to Salesforce (and databases in general) is to match every field to one and only one question. With this principle, you can see the problem with the Lead Source field: there are at least five uses for it, and left unmanaged this is a recipe for disaster.

Salesforce Rule #2: don’t create more fields

Unfortunately the competing rule also is in play: in general, avoid creating more fields in Salesforce, as it adds complexity to the system. In Marketo, this is even more true, as you cannot delete fields in Marketo.

Alternative: Acquisition Programs (and Salesforce Campaigns)

When Salesforce announced Campaigns, and Marketo created acquisition programs, the paradigm shifted. Here, you now have an entire object dedicated to the question “What buckets of money brought the best results?”  Where a field like lead source is optimized to only answer one question, the campaign object allows you to both answer many questions, and group the answers without specifically programming the groupings. 

If that last paragraph doesn’t make sense to you, this comparison of lead source and acquisition programs might help:

 

Comparison between Marketo Lead Source and Acquisition Program

This table shows the advantages of using the object, but also the basic problem. The lead source field has the advantage of being understood by admins and executives, and so you’ll often hear the executives speak in terms of lead source, followed by an admin configuring lead source to match their requirements. Too often, the overwhelmed admin doesn’t take the opportunity to deeply understand what the executives really want, so you end up with an entire reporting architecture relying on the lead source field, even when it doesn’t match the executive’s goals.

Instead of simply following the vocabulary of the business stakeholders, we recommend taking the time to deeply understand their goals independent of any vocabulary to ensure they sincerely want to use the fields and objects they mention.

What else to do with lead source field

The lead source field is standard, so you can’t delete it.  What to do with it if acquisition program effectively replaces it?  Our favorite use case is to use it as a reminder to the salesperson of the last source where the lead came from.  For example, you might make a lead source “Attended Webinar on reporting”.  With a bit of effort, you can add a lead source value update to every program.  This is especially valuable for inside sales teams using the console, as it minimizes the time needed to research an inbound lead before follow up.  You may not be able to get meaningful reporting from this field, and thats ok: let the lead source empower the sales team to move faster, and save macro analyses for the more complex objects.

Technical Details

If you’re on the business side, the blog post is over! Check out our Guide to generating bounced buyers. For those more technically inclined, the rest of the post will provide more details you may find useful.

Technical overview of Lead Source and Acquisition Program

 

Askbeachhead_technical.png

Some of you may be wondering “why use Marketo acquisition programs when the SFDC Campaign is just as good?” I’m glad you asked. It turns out these actually sync nearly 100% with each other out of the box, so the information above for Acquisition Programs applies equally well to SFDC Campaigns.

I say “nearly 100%” because there is some syncing behavior worth noting. Here is a diagram provided by Marketo

Marketo data sync diagram.png

If you don’t want to remember everything in this diagram, an easier heuristic is this: “when in doubt, start your data in Marketo.” 

Summary

In conclusion, and to answer the original question, almost every company using Marketo and Salesforce should use the acquisition program object and ignore the lead source field. If you really want to keep it, we typically recommend using the lead source field as the last touch before conversion, but focus on providing values actionable to the sales team rather than the executive.

Originally written by Jeff Shearer

I’m a B2B company’s least favorite kind of prospect.

  • I ignore or unsubscribe from their emails (especially if I didn’t explicitly opt in )
  • I’m doubly likely to opt out if my information was clearly bought from a list (In fact, I’ll do this just out of spite)
  • I never answer or return their calls (and in the rare circumstance that they actually do reach me, the very act of doing so usually kills any chances of them getting a successful sale from me). I don’t hate talking on the phone, I just really hate getting called by salespeople unless I’m specifically requesting it.
  • I don’t click their ads (except to see if there are any creative ideas worth poaching from their landing pages)
  • I immediately see through any sort of automation and tracking they’re using: if they have a gate on content I want, I either disable javascript or view source to get to the content without providing my information, or I just give (cringe) fake information.
  • I used to sometimes respond positively to LinkedIn InMail when the volume was low, but nowadays find myself largely rejecting most InMail requests.
  • In the rare case that someone does get me interested in something, I’m terrible at staying in touch with them, and never stick to the timelines they set.

 

And yet, my job is to help  sales reps do the very things to prospects that I absolutely detest. So how do you sell to the most private of prospects? When I look back at how I’ve been successfully sold to in the past, some common themes emerge.

Content plays a big role–and I’m not just talking about white papers and webinars–product details, video demos, etc all are valued, depending on where I’m at in the buying cycle. I’m big into doing my research ahead of time, so I actually find myself consuming most of a brand’s relevant content before ever engaging with a salesperson. While I generally avoid gated content if possible, this isn’t a hard and fast rule, and I will give up some basic contact information in certain instances. The one thing I won’t do, though, is give up my phone number for a whitepaper.

When it comes to marketing technology, I’ll always vet a potential vendor with my professional network  for eputation. If I catch a whiff of a poor product from my peers, that’ll usually not only kill the sale, but cause me to warn others to steer clear as well. While references are an important part of deciding on a vendor, it’s actually how I first catch wind of many of them. I try to surround myself with very intelligent people, and if they’ve found a way to solve a problem I too am experiencing, I’ll listen.

Obviously, the timing also has to be right. When this doesn’t line up, even the most willing of prospects isn’t going to be able to make the purchase. But there’s more to it than that. I think most organizations tend to shoot first and ask questions later when it comes to determining the timeline of a prospect. The very fact thatthey are asking me if I’m in the market & timeline for whatever they’re selling, they’ve  already lost the sale. The salespeople who generally win with me are those who recognize that I will come to them when I’m ready to hear more.

Even though the average prospect in most industries probably isn’t as aggressively unreachable as me, I do respond well to content (when done right), referrals and reputation count, and timing is everything. The difference is that while you can potentially get my attention with direct sales tactics, I’m not likely to reciprocate. Instead, I’ll readily raise my hand when the need, want and timing are there.

On a side note: I suspect part of my stubbornness around sales engagement has a lot to do with my profession. Seeing how the sausage is made has a certain effect on one’s taste preferences. Part of me is thankful I don’t currently work in an industry where I’m marketing to marketers. We’re a tough group to please.