Agreed with Sanford--why not use the existing link ID setup? I do something in a bit of reverse where I assign all of an email's standard links (logo, social icons, whatever) a specific link ID prefix so they may be screened out for reports, Smart List triggers, and so forth. There's an appropriate link ID constraint on anything involving clicks. ... View more

So, what you're describing is essentially an ETL tool's responsibility, and there are plenty that work with both Marketo and Azure SQL DWH/Azure Data Lake; both on-prem (Boomi, Alteryx, et al.) and SaaS (Fivetran, Stitch, Alooma, et al.) ETLs can handle this sort of work on a scheduled, automatic basis. ... View more

The offset you receive in the response from the endpoint lets you page through total results per the max return you've set--so you'd continue paging through the results via offset until you hit a number under 200. At that point, you'd have your count of folders. There's no meta "total" value, as the results themselves are what you're supposed to tabulate to figure that out. ... View more

On a basic level, Marketo writes cookies to the domain .example.com, meaning that the cookie should be readable from any given subdomain. Now, there are complications with two-letter TLDs, and if you have a non-standard deployment of how your cookies are recorded, that can cause issues. But, by default, everything should work according to your example without issue. Now, there may not be Munchkin.js initialized on store.example.com compared to example.com, and that could explain the lack of visibility in the activity log. But it's not because Munchkin.js can't read the cookie. ... View more

Based on the information you've given so far, it's actually pretty hard to tell why this might be happening. I would at least start by seeing if there's discrepancies by source (form integration vs. upload), because it sounds like the object setup itself is fine--it's getting the data in. Look for patterns and work backwards. Although I'm a little suspicious of any sort of form integration as it relates to custom objects, because that needs to be set up correctly to its own external server-side service in order for that to work. ... View more

Yes, this can be done--I personally do a variant of this using fieldsets to determine pages rather than multiple forms--but it does require some JavaScript development. ... View more

In a case like this, your best bet is probably to handle such a redirect at the DNS level. Now, while it's strongly discouraged because you're doing two lookups, it's totally possible to do something like info-old IN CNAME your-instance.mktoweb.com. info IN CNAME info-old So when you look up info, it goes to info-old, then to your-instance.mktoweb.com. However, what you're describing sounds more like swapping the root domain rather than the CNAME. Same concept applies, though. Depending on your DNS provider, you may be able to set up redirects rather than chaining CNAMEs, but it's a non-standard thing and depends on who you have. ... View more

Again, I'm a little confused--how is that different than the existing description aside from UX/placement? I'm not trying to be obstinate but just trying to understand how that differs from today's description, which can be added under the field name per my screenshot. ... View more

I'm a bit confused on this ask—are you referring to something separate from the existing description today on individual fields? (The UI to add descriptions and its locking of lines for multi-line descriptions is wonky, I'll give you that.) ... View more

Agree with Sandy that this should work as expected if the form is on a Marketo LP for labels and the like, but one minor word of caution for the token-happy/anyone stumbling upon this later: while you can also place tokens in other parts of a form, such as with picklist values, know that using them there can cause some glitches within the form editor UI due to the way that's set up. ... View more

My understanding (and correct me if I'm wrong) is that it is only the domain the cookie is setting from when third-party that needs to be secure (e.g., if you go to an HTTP-only site but the third party is HTTPS, you can still set a secure flag on the cookie)—strictly speaking, the secure flag only provides confidentiality and not integrity. That would only put the onus on marketo.net to be secure, and it already is. What you're implying—that there's no way to implement secure;SameSite=none while being insecure—would be a much larger implication of "oh hey everyone using any sort of adtech must have TLS by Chrome 80 for first-party or it'll break", and I just don't see that as the case here. ... View more

So, I'd actually like to advocate for two items that were previously on the Marketo roadmap but seem to have gone missing: Field Metadata API and User Provisioning API. The two most common things I do when in the Admin section are either creating fields or handling users—and the idea behind both of these APIs were to solve common pain points around both. By having a Field Metadata API, third-party integrations could add/update fields as needed rather than forcing the end user to enter fields by hand. Likewise, the ability to mass hide outdated fields would be a big boon--I once spent nearly 20 hours hiding ~700 fields from a client instance, and I could have just as easily done that in 20 minutes with an API call that would let me review fields and then post an update to hide them from UI.  Likewise, with most enterprises onboarding/offboarding marketing employees, there's automation for adding and removing Exchange inboxes, Salesforce users, HR software logins... but no way to hook Marketo into this setup. As such, you're stuck adding and removing users manually, which is a pain. There's no reason a user API couldn't just hook into Workday or other HR systems to make this part of the onboard/offboard process. These things don't sound cool or appealing, so they tend to die on the vine--but the convenience they afford when given context makes them worth it. ... View more

So, I wanted to post an update to this idea because it's been sitting with the "Working On It Now" label on it for over a year.  I recently checked in on the instance that originally found this issue because I noticed the trigger for it had been automatically deactivated—and it turns out there hadn't been any more occurrences of this behavior since August 2018. Out of curiosity, I recreated the issue again and this time the record stayed unsubscribed upon changing the email address. This bug looks like it's resolved. Someone from the Marketo side should mark this as Done! to get some credit for accepting user feedback. Thanks, whoever fixed this. ... View more

Hi Keerthana, I would be tempted to start by analyzing your logs and seeing the details of the incoming requests. One thing that I like to do is actually add custom headers to my webhooks so I can verify that the request actually came from a specific Marketo instance, then keep that as part of logging. This should at least tell you if Marketo is misfiring and requesting the webhook twice, or if something else is erroneously invoking it once Marketo calls the webhook. For what it's worth, I've deployed quite a few webhooks and have yet to see two requests back-to-back, especially one with no JSON payload afterwards. ... View more

Hi Amanda, As Jackie mentions, you can view Tasks and Events as Activities in Marketo, but be aware that there is a limitation where only the standard fields on that object (Subject, Description, Assigned to, Date, etc.) are viewable or filterable--any custom field additions are not exposed, unlike other Salesforce standard objects. ... View more

When you use the "contains" syntax, it acts effectively as an or operator, so to translate your screenshot, it's saying: When looking at activities where someone clicked a link on an email, look at any of these 19 options and see if they've got at least three activities that match. As a result, the scenario you're describing where if someone clicks A 2 times and B once, they'd be caught by this. Unfortunately, you'll probably need to either break these filters out (as you alluded to) or use another constraint such as time or link IDs to figure out how to best approach finding people who click at least three times on a given email. ... View more

I've yammered about this about 100 times to any Adobe employee who will listen, but please please please don't forget about Brackets! I would be over the moon for an integration that used the REST API to pull emails and landing page templates (or possibly the assets themselves), let you edit them in Brackets, and then publish them again in Marketo. This would greatly improve frontend dev workflow (coding in the UI is painful), and Dreamweaver isn't used by any modern web developers at this point. CID generation and auto-tagging to URLs for Adobe Analytics integration. UI-friendly Typekit integration for emails and landing pages--basically, allow users who are less technically savvy to license and use Adobe Fonts in their emails and landing pages without any friction. Font gets added to the editor UI, @import and the like are automatically added to templates, etc. Bake a real solution for PDF tracking and analytics that plays nicely with Document Cloud—this is a common point of confusion for users ("How can I see who looked at my PDF?") and there's some cool functionality that could be done. For example, think of a marketing department offering a beta to some of their customers: they could send out an Adobe Sign document with the NDA for the beta and then be able to trace who opened the document, signed off (or left comments) and report on the success through Marketo progression statuses. No reconciliation needed. You know, there's this whole Magento product and there's no ecommerce integration at all in Marketo as of today... ... View more

Hi Vinay, In this case, you should add whatever CRM you're using as a data source into Tableau to pull the opportunity data, then just reference it accordingly. That's all RCE is doing in this setup as-is. ... View more

Hi Stephanie, Without knowing exactly how "Stop Sync to Marketo" was set up, it's difficult to give specific advice, but know that when you do that kind of hard stop, it does by association do a hard stop of synced data, which then leads to this sort of orphaned data. Generally, if you put some sort of process delay so Marketo can sync down the data saying "hey, ignore this record from here on out/remove it from Marketo/etc." before the record becomes inaccessible, that's the best way forward. ... View more

From my experience with Klipfolio, the way they set up their endpoints for calling data from Marketo is a bit problematic and tends to timeout once you've got something that needs more than 4 or 5 calls' worth (~1000 data points) that needs to be visualized. The solution to this has been to use either BigQuery or Snowflake to extract the data you want and store it there, then just actually use those datasets the same way you would do for Google Sheets. The data still shows up in the Excel-esque table method that Klipfolio uses, but it's much easier to query and scale. Moving the data into Sheets proper is possible, as Sandy alludes to, but it's probably not the best tool to get the job done.  The initial set up of transfer of data to a database is a bit of lifting, but once that's done it's pretty straightforward to integrate into your Klips. ... View more

Hi Kana, There's several things to unpack here in this code: One of the first things that jumped out to me was your CSS order—you generally want your MSO declarations under your normal declarations.  Most of the selectors here are written in an older style that was previously needed for Yahoo, but no longer needed--and more importantly, when they're marked up this way, they cause any rules written that way to fail for Gmail/Gmail App. Essentially, you want to translate selectors like table[class="table600"] to  table.table600 , *[class].main  to .main, etc. If these are being used, they'll cause everything inside that <style> block to be ignored. Thus, you want to avoid using them where you can and when they're truly necessary, place inside separate style blocks. Because you are using a custom web font by default and not providing a proper backup, Outlook is failing and defaulting back to Times New Roman. If Outlook doesn't know the font, it won't go further down the family list. Adding the style property mso-generic-font-family:swiss; will force it to default to sans-serif instead. I can't tell exactly why the responsive design isn't being honored as the parent tags look correct and debugging it would take a chunk of time, but I hope that at least helps you get on the right path. ... View more

As far as I'm concerned, this is the real way to handle this—not creating anything inside the Marketo platform. Similar things are done all the time for things like validation rules, minimum viable records, etc. ... View more