Grant_Booth

Looks like great upgrades! I'm happy to see this package getting attention again. I particularly like the idea of event registration being listed separately - it's so important right now. Regarding displaying upcoming email campaigns, it's a nice idea but since it's displaying all email campaigns, rather than just those the lead/contact qualifies for, it seems like that will cause a lot of confusion and be more harmful than helpful. I'm struggling to see how it could be useful unless specific to the lead, contact, or account. However, it looks like I can just disable that in the new admin controls! ... View more

I use those all the time! But it's a little bit of a secret that those tools exist, and I suspect Marketo would want to make them a little more user-friendly before advertising them very much ... View more

I love Workato. But nevertheless my first thought is "Are you absolutely positive you can't use two separate Marketo instances instead?" I feel like that would (shockingly) be less expensive than maintaining an enormous custom integration. It seems odd to me that the business scenario would require two separate SFDC subscriptions but couldn't function with two Marketo instances. If the business units are so separate that they need different CRMs, it seems like they wouldn't want to share a single marketing automation platform. ... View more

Another function that could really use some cleanup/improvement is Webhooks. Some nice-to-haves: When I save changes to a webhook, it reloads the first webhook in the list (they're in alphabetical order) rather than the webhook I was working on. This has caused me to accidentally overwrite that webhook by mistake. Drafts and version control. When #1 (see above) happens, I can't just click a button to undo the mistake. Unless I had saved attributes of the webhook somewhere else (in a text file or something), I would have to rebuild it. It makes for a huge pain. For larger companies, I can only assume they end up with a lot of webhooks. It would be nice to be able to create a folder structure. ... View more

I made a special role that only includes Field Management and gave it to a couple of users, with very specific instructions not to edit anything. But View Field Management v. Edit Field Management permission would be nice to have. ... View more

Thanks Vikram! Yes, regarding the Used By list for a field, they are clickable, but are not regular hyperlinks so we can't open them in a separate tab. If I need to adapt to a major process change, we could be talking about hundreds of assets that I need to remove the field from before I can hide the field. ... View more

Thank you for asking this! 1. Salesforce integration is the section I dislike the most. You can edit some basic sync options, and see a timestamp of the last sync and whether or not it's in progress, but it gives very little other visibility, and that makes admin'ing the integration difficult. Would be great if some of the information (object schemas, field visibility and field types, sync logs) were available to admin users through non-secret and supported methods. It would be great to see a log of the sync cycle - how many records of a given object synced to and from Salesforce, how many were new, updated, a count of the how many records are pending sync for each object. An error log too please! FYI - I used to work in Marketo Support and I know that all of this information is already available to them, and simply needs some work to make it presentable and supportable for users. In my opinion, it would also deflect a lot of their cases related to the Salesforce integration. It would also be fantastic to have a "Field Mapping" tab where we can change the field mapping between Marketo and Salesforce on our own without having to go through Support. Additionally, it would be great if fields did not automatically sync down to Marketo simply because the sync user can see them - if the fields simply became available for sync in this hypothetical "Field Mapping" tab, it would help us tremendously with keeping our fields clean, giving us control rather than being at the mercy of our SFDC admins remembering to follow processes around permissions. 2. Field Management is the most used. For an agile team, there is constant change coming downstream from Salesforce. We have to adapt quickly to process changes in CRM by making sure new fields are synced properly and finding where old fields are in use to make sure there are no dependent processes. It would be really nice if we could (1) delete old fields rather than hiding them, (2) relabel fields even though they are in use. Our instance is 10 years old, and we have an enormous list of hidden fields. Also, when removing a field from assets, we find the field in Field Management and look at the Used By list - but the assets there aren't clickable links, which makes it even more painful trying to remove references to the field. 3. I think I covered this in #1 and #2 4. I'm not sure how I would apply an export feature of admin configurations. If other people have use cases for that I'd be curious. ... View more

Hey Austin - follow me and then shoot me a private message me with a link to your unsubscribe page. I can take a look and try to help you out. We recently deployed SSL without problems. ... View more

Also, let's not forget about the massive infrastructure and processing speed improvements that happened over the last couple of years. Remember how that smart list that now takes 5 seconds to load used to take 10 minutes? It hasn't been visible, so I don't think it's received the credit it deserves, but it's been a HUGE improvement. ... View more

I have to admit that getting charged for SSL, although a small charge compared to the overall contract, does sting. Security warnings on pages without SSL are now becoming standard across the web. It should be self-provisioning and default in new subscriptions. It's the kind of improvements they could use to justify that automatic contract increase at renewal... ... View more

Our experience has been the opposite, and I think this may simply vary by your CSM and/or their manager. When Marketo was owned by Vista, we felt like our CSM was very aggressive and we were being arbitrarily squeezed, where as our current CSM seems more focused on building a healthy long-term relationship with us. My impression was that while Vista was focused on flipping the company for sales (as venture capital firms tend to do), Adobe is more focused on the long-term health of the product. But acquisitions are chaotic, and it could take years to see the fruits of that. ... View more

Regarding the email program, I think it's a great example of how Marketo was struggling with its direction, and tried to hobble together a flashy new feature rather than continuing to improve on their core platform. It's useful primarily for two things: A/B testing and sending in time-zone. Why not focus on incorporating those things into smart campaigns instead? For example, a "Send A/B Test" flow step, or an "Emails in time zone" option in the Schedule tab of a smart campaign? ... View more

I was formerly a support engineer at Marketo before moving on to be a Marketo admin myself several years ago. From what I recall, each server will have several different customers on it, and each server has some extra resources that can be assigned to speed up an instance's SFDC sync. HOWEVER - if they have already done so for another customer or two on the same server, then those extra resources are tied up and can't be moved to your instance. It depended more on luck than your account size, and was certainly easier to get if you ask a couple weeks in advance of a planned mass update in Salesforce, compared to calling in with an emergency after the fact. I can't say with certainly that's what happened in your case (never rule out overwork or laziness as an explanation for anyone's behavior at any company), but I can say that it happened for other people. Basically, they can't pull the resources from someone else and screw up their planned deployment in a response to another customer's emergency request. And they don't keep a ton of extra processing resources on hand, because they would use them to make everyone's sync faster by default. All of this said, it would really nice if you could select which fields triggered records to sync with Marketo, to prevent such backlogs in the first place. ... View more

Update: they told me they had to roll back the last one and a fix is scheduled for August. ... View more

Update here: I managed to get this reported as a bug, and was told a patch would be deployed with the June release. However, it looks like the automapping only happens now for the right-most column that was blocked from updates, in the below example "Opt-In Implicit." I've reopened my support case. I'm guessing whoever wrote the patch was only testing with one field that was blocked from updates... ... View more

We've been scoping the work to replace our drupal forms with Forms 2.0 and this workaround helped! ... View more

There are a number of ways you can identify leads as part of an account list without using a product like Marketo ABM. For example, if you have a list of accounts for a certain industry, you could run a report in Salesforce to view those accounts and their website, Company Name, etc. You could take values from the account website field, change them to email domain format, and put them in the Email Address filter in Marketo. I.e. Email Address contains @company1.com,@company2.com,etc.  It doesn't have the "fuzzy logic" advantage of a separate product, but it's better than nothing. Also, don't forget that data enrichment products like DiscoverOrg  or   Dunn & Bradstreet already match leads to their own company records, which you can leverage to do some account matching. Key thing to remember is: I recommend developing an ABM *strategy* before putting too much thought into buying ABM tools. That way, you can approach buying a tool based on what you've decided your strategy requirements are. Get aligned with Sales, figure out which accounts / types of accounts you want to target and why. ... View more

Two things: 1. When you push the 60k in Marketo, they'll be created as leads, not contacts. That's an important consideration if you need them to be contacts in SFDC. 2. I don't believe they'll dedupe in SFDC when you upload them there. Operations in SFDC rely entirely on the record's SFDC ID - there's no built-in dedupe based on the email address like there is in Marketo. I recommend removing the people who are already in Marketo from the file before you upload it in SFDC (perhaps with a vlookup in Excel). If you need to update the records that were already in Marketo, do that separately. ... View more

Rereading your post, I see you haven't uploaded them to SFDC yet. Assuming you need them to be uploaded to SFDC as contacts associated with accounts...I have bad news. When you create new leads or contacts in SFDC, they will sync down to Marketo as new people, causing duplicates. Your best options in that case are (A) delete all your people in Marketo and start fresh there, or (B) pay Marketo's professional services team to set up something to merge the existing leads in Marketo with the new contacts in SFDC. If they can be leads in SFDC, rather than contacts, then your situation is much brighter. You can just sync them from Marketo to SFDC using a smart campaign like you described. Marketo treats SFDC as an authority when it comes to creating new records. If it sees a new record in SFDC, it creates a new record in Marketo, even if there was already another record in Marketo with the same email address. ... View more

Making sure I understand the situation: - you have 60k records in Marketo - the same people already exist as leads and contacts in SFDC - Marketo and SFDC are not yet connected Is that all correct? ... View more

I don't think there's a way to filter which smart campaign you want results for in the API request. I would try querying those activity types (sends, opens, etc.) and then see if the results return a value for the ID or name of a smart campaign that's responsible for the change: http://developers.marketo.com/rest-api/lead-database/activities/#query Apologies if that information isn't part of the response - I haven't tried it myself. Maybe also try the bulk activity API to see if it returns different data. http://developers.marketo.com/rest-api/bulk-extract/bulk-activity-extract/ ... View more

Hey there, Sales Owner = Lead Owner. They're the same field. I think this discussion provides good context: From "Lead" to "Person" A couple of years ago, Marketo engaged on a horribly misguided project to change standard field labels to use "Person" rather than "Lead". For example, changing "Lead Source" to "Person Source", "Lead Status" to "Person Status", and "Lead Owner" to "Sales Owner". The thinking was that because a "lead" in Marketo could be either a lead or contact in the connected CRM, it was causing confusion. Unfortunately, everything on the back-end - tokens, API names, form field names, etc. - still had to use "lead" (otherwise it would break integrations). So the change was only to labels and caused more confusion than it solved. I hope they just admit it was a mistake and change it back some day. Grant ... View more