About Courtney_Grimes

Courtney_Grimes

Imagine a scenario where lead IDs 4 and 5 are merged together in a Marketo instance. 5 is the "winning" ID, so querying the lead via the REST API returns data. However, if you query for data on lead ID 4, a successful API query is returned with no data in it. This means reconciling that 4 was merged into 5 difficult, and leaves a stray ID. Would it be possible to update results on merged records so that they pass something like "mergedInto" : 4 when this occurs? Bonus points if the winning record also got a note like "mergedWith": 3,4,7 -- something that concatenates all records which have been merged into this winning record; this would be nice to help verify on both ends that a merge was successful.

Courtney_Grimes

As of today, using /rest/v1/program/members/describe.json will return default Program Member fields in addition to whatever custom fields have been defined. Although items like Acquired By and Success are present, the field for Success Date is not. Could this be added to the list of extractable fields, both when describing and exporting?

Courtney_Grimes

Straightforward request: I am a big advocate of using Marketo's description fields when using any sort of asset that's in a Marketo tree—a local asset, program, campaign, folder, template, etc. This area allows you to put in key details, link your work back to ticketing systems, provide context for colleagues, and so on. However, as of today you can't search any data that's been put into a description inside the UI. For example, if I wanted to note that a certain Smart Campaign uses the form named A Cool Form with ID 1000, I might put in some text in the description like: "Processes A Cool Form (ID: 1000), assigns values, and sends an alert". However, if a user just searches in the tree for "A Cool Form", they'll only see the actual form asset named "A Cool Form". If the description data was also indexed in the search, the user could see not only the form but all related assets in one go. Could this data get additionally indexed into tree searches?

Courtney_Grimes

Beth, if I could like your comment five times over, I would—this solves several pain points I have. Still would like to see that in the UI (or at least explained somehow that this technique is possible), but this saves a lot of little time that adds up. Thanks to you and your colleague Cam!

Courtney_Grimes

There are times when a user may send a record a sales email from Marketo Sales Insight, only for the recipient to be uninterested in the email and unsubscribe if the option is available in the footer and/or they send a list-unsubscribe signal from their email client. However, when the Unsubscribe Email activity is written into Marketo for unsubscribing from a Sales Insight email, there's no way to understand that's what's happened. This is because the details on the activity don't explicitly say the email came from Sales Insight, and there's no way to use the "Unsubscribed from Email" activity filter in the UI to grab just Sales Insight emails. I recognize that tying unsubscribes to Sales Insight emails sent 1:1 is likely too technically complex to pursue, but could a filtering parameter get added to Unsubscribe from Email for "Sales Insight Email" true or false? This would address the problem without requiring big data analysis for this statistic.

Courtney_Grimes · ‎01-08-2021

It looks like there's been some recent improvements to Marketo Engage's form accessibility around validating fields. This is great! However, there are some small tweaks that need to occur in order for these new items to perform in a way that's stricter to WCAG standards. 1. The aria-describedby attribute for inputs should only be inserted at the time that the validation message itself is added to the DOM; otherwise, the attribute has nothing to reference. 2. Items displayed in .mktoErrorMsg should additionally have aria-live set to assertive. 3. This isn't strictly accessibility-related, but when looking at validating form fields against behaviors, I'll also use setCustomValidity() and set the required attribute upon validation if validation fails for required fields. This can help with CSS/JS presentation if the Marketo customer uses custom behavior/visuals elsewhere.

Courtney_Grimes · ‎12-23-2020

In theory, Marketo should not have duplicate records with the same email address, but this is often not the case in actual use. This means when choosing a record to emulate for sending a sample email, there can be multiple results returned when looking for an email address. If there are three example@test.com records, all three will be listed in the Send Sample dialog box—but there's no good way today to quickly understand which of the three options you're choosing correlates to what record. Would it be possible to add an additional identifier, such as Marketo ID, Unique Code or Unique Name that could either be displayed in the UI or used as a secondary search criteria? This ensures when there are material differences (such as one variant having custom objects attached) that testing can occur quicker and with less confusion.

Courtney_Grimes · ‎11-13-2020

This isn't something I'd normally think about, but I was doing some basic explanation on how Marketo works to someone and they encountered some frustration around how deleting assets work. As a general rule, if there is an approved version (for emails and landing pages) or if an asset is referenced elsewhere (such as for forms, smart lists, social assets and so on), the asset can't be deleted. That makes total sense from a development point of view, but it's disorienting for new users to not be able to understand why they can't remove the asset—they must click on delete, get the error message (that isn't clear for beginners) and then understand that they must either: a. Go to Used By, find the asset references, remove them, and then delete and/or b. Must unapprove the asset first, then are able to delete The messaging shown in response to an invalid attempt to delete today works but also assumes you understand the meaning behind it. Most new users just don't have that understanding yet. What I'm suggesting is a better user experience for this: either don't show the delete option until the asset can truly be deleted, or ideally create contextual options. For example, two separate changes that could happen in the drop down are: "Unapprove and delete" (if no asset references--perform this task on behalf of the user in one go) "Prep for deletion" (show the Used By panel contents and explain that references must be removed) However, I'm not a UX designer by trade; I'm just suggesting looking at more user-friendly ways to approach removing assets.

Courtney_Grimes · ‎10-29-2020

There are some good use cases for needing to query records that start with apostrophes: for example, a common list upload error that can occur involves improperly-formatted CSV files, resulting in records with email addresses like 'example@hotmail.com' instead of example@hotmail.com. Currently, the Marketo platform doesn't properly return results for these queries because the character is improperly escaped. If you do a search for "Email Address: begins with ' ", you will return all non-empty email addresses. Attempting to use common SQL escape patterns (\', '') does not fix the problem. If this behavior could be fixed so the search correctly looks for apostrophes, it would be appreciated. (I am aware there are other ways to retrieve this data and have done so; I just wanted to note this specific bug.)

Courtney_Grimes · ‎10-13-2020

Just a side note here that RCE does calculate complaint rates—I'm not sure if it's just looking at Cat 1 bounces or Unsubscribe Reasons with certain keywords populated or what have you, but there is some precedent for breaking this out separately. While there are definitely other ways to pull this data out, it's a bit unfortunate that it's not as readily available anywhere else like Email Insights.

Courtney_Grimes · ‎09-10-2020

Straightforward request: I would like to have an API endpoint that allows for automated import of programs from trusted instances into a given instance. Currently, only UI controls allow you to import between trusted instances, which causes considerable slowdown and does not allow you to change conflict rules in bulk(Allow custom conflict rules when importing programs ). Having API access both to set import conflict rules AND the ability to queue imports would be a big win for technology partners looking to deploy standardized programs as well as handle enterprise sandbox->production migration in a smooth way.

Courtney_Grimes · ‎07-15-2020

This is a bit of an odd question, but one I realized I have no idea on: when you use a filter such as In Time Frame: Today or In Past: 2 Days, how is the "day" itself calculated? That is to say, how is a day determined for a given datetime? Is the calculation done by the Location set in Marketo? Is this done at the server level? Is "day" just a human-friendly shorthand for the most recent 24-hour period? For example, if I have "today" as a time frame filter, does this mean if something is stamped at 11:59 PM and isn't able to be looked at for triggering a Smart Campaign until 12:00 AM, will that Today filter exclude it?

Courtney_Grimes · ‎07-14-2020

When doing program imports, there is a chance with each program import to define how you'd like to handle conflicting information. This is great, but doesn't necessarily scale well when you need to do a lot of imports. For example, if I need to import 20 programs from Instance A to Instance B, there may be a specific rule like "Ignore Program Tags" that I want to set for every import. As it stands, that currently has to be done by editing the conflict rules every time. I'd prefer to have either an instance-wide or user-level setting that allows these rules to be altered and thus prevent having to do this catch every time.

Courtney_Grimes · ‎07-14-2020

Not necessarily--in this case, the variable has been set, and it's showing that to the end user. You just more typically run across 365 doing this when there's nothing set in the link.

Courtney_Grimes · ‎07-13-2020

Of course. 365 and Outlook.com are pretty fussy about links in general—in fact, if you've ever tried to do something like <a href="">Test 1</a> or <a href="#">Test 2</a> this used to fail and make links break up until recently. I even wound up just switching to using "#tbd" in order to get around this problem when I didn't know what a link was going to be. Basically, if the software can't understand that the link is in fact a link, it errors out and shows the end user bracketing similar to the following: In the case of that screenshot, the link is wrapped in something very similar to <a href="https://${ctaLink}">${ctaText}</a> So, it was just the straw that broke the camel's back on this method for me.

Courtney_Grimes · ‎07-13-2020

Hi Cahan, This actually isn't a malformed link, but instead a specific setup issue: when you create an email template and choose to use variables for links (such as the CTA link) in editable areas, some problems can occur—while the majority of email clients will receive the email with the properly formed link (so http://${CTA-url} is a real link in the email), but not all. Additional issues can come up when you use both the link and the link name as variables, notably in Office 365. I'm at the point where between the lack of copying to text versions of emails, the breaking in Office 365, and the issues it causes in links for Smart Lists/reports that I can no longer recommend anyone use this technique for links in emails. You'll need to restructure your email template so the user has to add the link in themselves.

Courtney_Grimes · ‎07-09-2020

A quick note on this method and booleans in general: when you send data to a Marketo Custom Object, the exact value that you give for a boolean is actually what is stored for accessing with Velocity. This fact doesn't change a ton, unless you're explicitly formatting the data for your booleans as 1/0 rather than true/false or similar. When using 1/0, it does explicitly write the 0 value into the field rather than being processed as blank. As such, if you plan on using the $mtkoBoolean map mentioned here, you may need to account for that distinction.

Courtney_Grimes · ‎07-09-2020

Hi there, So, this Selfridges email is using a common technique that's done in B2C and retail emails, but it may not translate really well into Marketo. If you look at the design itself, you can think about it as table rows and columns rather than the slants you see visually: 1. Full column width for knits to know, then a second full column for the angle 2. Two columns for the footwear and handbags 3. Another two columns for coats and trend Rather than use image maps, what they're doing in this case is setting the images seamlessly next to each other as big, clickable split-up images. That way, when you click on each individual image, it takes you to the correct corresponding link. This also allows the developers to play with media queries, so they can dynamically show and hide the appropriate images (that will adjust the diagonal designs) based on screen size. That doesn't always translate well for Marketo, because the modular design doesn't really work in the same way--you can, of course, write a template that does this, but what'd you also need in your back pocket is existing Photoshop templates that would have this angling. This design also has the disadvantage of not having live text on it--all the copy is on the images themselves, so you'd have to update the image and re-upload it if you wanted to change something. This says nothing to the lack of accessibility as well. Again, you could write a template that does allow you to use live text, but this starts to get complex and difficult for anyone but advanced email developers. If you like the visual style of slants, one way you can work that in is to actually use slants as backgrounds as part of a module. For example, I've done setups in the past where at the end of a module, there's just a diagonal image that acts as a transition into the next module color/style, or used gradient fades to make that same effect happen. This also has the advantage of scaling nicely for mobile and systems that can't support modern HTML development techniques.

Courtney_Grimes · ‎07-09-2020

(Apologies in advance if a similar idea has been filed—I tried searching and couldn't find this ask.) Right now, users are given two binary choices when setting up an engagement program that sends emails: 1. Add the email directly to the nurture stream with the ability to send in recipient time zone 2. Add the email as part of a program to the nurture stream with the ability to screen out recipients based on Smart List, program status, etc. However, if you want the ability to send an email in recipient time zone (due to being global, for example) and want to exclude certain records from receiving a nurture email (due to having consumed the content of the email another way, for example), there's really no good way to do that today. There's already a solution in Marketo architecture for this, though: the Email Send program, which can both handle local time zone sends and setting up exclusions. If we were able to reference Email Sends the way Default programs can be used today in Engagement programs, that would cleanly solve this issue. Otherwise, you're stuck making a traffic cop just to be able to use both features.

Courtney_Grimes · ‎06-18-2020

While standard Marketo fields are already blocked from having API names that start with numbers in the UI, this restriction is not in place for Marketo Custom Objects. This causes knock-on issues with Velocity scripting being unable to reference the field. The ability to create fields starting with numbers should be blocked from the UI.

Courtney_Grimes · ‎06-05-2020

Updating this idea to note that Person Time Zone is now exposed as a field you can use. Thank you for implementing it.

Courtney_Grimes · ‎05-27-2020

When using the / rest / asset / v1 / files . json endpoint, being able to use MIME type as a querying parameter would be useful, especially when dealing with Design Studio instances where foldering has not been properly used. Being able to pull all PDFs with application/pdf or PNGs with image/png would be helpful for paring down results to just certain types of files. The MIME type today is already returned when using this endpoint.

Courtney_Grimes · ‎05-27-2020

Right now, there is no accurate way to determine if a file is identical, but uploaded with a different name inside a Marketo instance. While you can pull file size and try to 1:1 compare sizes to understand if a file is identical, this is an imprecise method. By storing some sort of checksum hash (MD5, SHA-2, etc.) with an asset, there's now several options for handling duplicate files. Uploads via API or UI could use the checksum to prevent duplicate uploads, and exposing the checksum via API (or even UI in some way) would allow for faster and more accurate detection of existing duplicate files.

Courtney_Grimes · ‎04-30-2020

You're in luck--the User Management API was recently released. That said, there's not a plug-and-play integration with Okta yet, but you can at least put something together manually.

Courtney_Grimes · ‎04-16-2020

Without seeing the full email template, this is going to be hard to diagnose, but I wanted to at least offer a bit of guidance. Some things you can look at to help deduce what might be the problem include: Do extensive tag closure checks. The most common reason a module will fail is that it isn't properly closed in some way with a stray missing </td> tag or what have you. You can use an HTML linter for this, but a site like HTML Tidy Online or Closing Tag Checker can work in a pinch. Ensure your module setup works with your container setup. Every module must be within your .mktoContainer parent and all of your module children must be at the same hierarchy level—so if your container is a <table>, the modules all must be immediate <td> children; if your container is a <td>, they all should be <table> children, and so on. Try pulling your modules one-by-one from your code to see where there may be issues, then re-introduce them once they've been known to work.

Courtney_Grimes · ‎04-10-2020

Hi Sev, Strictly speaking, Twitter should be able to read og:image tags—it's the fallback that it uses if Twitter's own twitter:image isn't being used. However, you do need to at least define twitter:card (as either summary or summary_large_image) and twitter:title. If you have those already set up, what may have happened in this case is a caching issue; are you testing using https://cards-dev.twitter.com/validator? You can also try defining twitter:image and see if that changes anything in terms of what you see when testing against the validator.

Courtney_Grimes · ‎04-02-2020

So, there's actually several things to unpack here because your code actually does center forms by default: the form itself is what's having issues. You'll first see that there's an imbalance here because label widths have been defined, but they don't show anything, causing a skew. However, even when we fix that, the form is still skewed because the length of the fields have been defined compared to the width of the form: You'll want to use the following CSS to correct this: label.mktoLabel.mktoHasWidth, .mktoOffset, .mktoForm .mktoGutter { display: none; } .mktoForm, .mktoForm .mktoFieldWrap, .mktoForm .mktoHtmlText, .mktoForm input, .mktoLogicalField .mktoCheckboxList {width:100% !important;} @media only screen and (min-width:480px) { .mktoFormCol:first-child:nth-last-child(2), .mktoFormCol:first-child:nth-last-child(2) ~ .mktoFormCol {width: 100% !important;} .mktoFormCol:first-child:nth-last-child(3), .mktoFormCol:first-child:nth-last-child(3) ~ .mktoFormCol {width: 50% !important;} .mktoFormCol:first-child:nth-last-child(4), .mktoFormCol:first-child:nth-last-child(4) ~ .mktoFormCol {width: 33.3333% !important;} .mktoFormCol:first-child:nth-last-child(3) ~ .mktoFormCol {padding-left: 0.3em !important;} } @media only screen and (max-width:480px) {.mktoFormCol {width:100% !important;}} .mktoAsterix{display:none !important;} .mktoForm .mktoGutter {display:none !important;} .mktoButtonWrap {margin-left:0 !important;} .mktoButtonRow {float: right;} .mktoForm input[type=text], .mktoForm input[type=url], .mktoForm input[type=email], .mktoForm input[type=tel], .mktoForm input[type=number], .mktoForm input[type=date], .mktoForm textarea.mktoField, .mktoForm select.mktoField {padding: 0.3em; width: 100% !important;} .mktoForm {clear: both; margin-bottom: 0.3em;} .mktoForm .mktoRadioList, .mktoForm .mktoCheckboxList {float: left !important; width: auto !important;} .mktoForm .mktoRadioList > label, .mktoForm .mktoCheckboxList > label {display: inherit !important;} Finally, you'll want to actually update your template as well: change the line " @import url(http://fonts.googleapis.com/css?family=Lato:100,300,400,700,900);" to "@import url(https://fonts.googleapis.com/css?family=Lato:100,300,400,700,900);" in order for your custom fonts to load correctly.

Courtney_Grimes · ‎03-17-2020

Hi Crystal, There aren't bigger images that I know of—because those are the assets that are used inside Marketo itself. Now, if you were looking for larger and more modern images, Sky uses SVGs in its UI, meaning those assets infinitely scale up and down correctly, and grabbing those are pretty straightforward.

Courtney_Grimes · ‎02-28-2020

Update: As of 2020-02-28, this behavior no longer occurs! Sending samples of templates actually does exactly what this ticket suggests—it sends the code itself as expected with all mktoAddByDefault modules. Thanks, whoever fixed this.

Courtney_Grimes · ‎02-24-2020

ContentAI currently tries to generate an image (with or without content title, CTA, etc.) for placing content in an email. However, this results in the predictive content failing to have much customizability in display, and more importantly, causes the predictive content to be inaccessible. The final code output is an image with no alt text or identifying title in the link. Rather than trying to dynamically generate an image with all content included, could the setup be changed to retrieve the image, URL, title, and call to action as separate items? This both prevents having to create more image template styles or customization for customers and allows developers to code to standards for accessibility compliance.

Online Status	Offline
Date Last Visited	Thursday

Date Registered	‎10-29-2014 04:04 PM
Date Last Visited	Thursday
Total Messages Posted	656
Likes Received	1069

Top Badges Earned

Return data on losing merge records when queried v...

Add Success Date field to Bulk Program Member Extr...

Allow tree item descriptions to be searchable with...

Re: Add Unique Identifier to Person Selection on E...

Provide UI-Friendly Way to Track Sales Insight Uns...

Improve Marketo Form Accessibility: Validation Beh...

Add Unique Identifier to Person Selection on Email...

UX Improvement: Display Deleting Assets Only When ...

Fix Smart List queries that start with apostrophes

Re: Wanted: Method to identify spam complaints

Add API Endpoint for Importing Programs

How are days determined with "in time frame" and "...

Allow custom conflict rules when importing program...

Re: Malformed links?

Re: Malformed links?

Re: Malformed links?

Re: Yet another way to make Velocity's Boolean-fla...

Re: Slanted modules in email template?

Allow Email Send Programs to be nested inside Enga...

Prevent Marketo Custom Object Field API Names from...

Re: Expose calculated time zones from Recipient Ti...

Add MIME type as an optional parameter to files.js...

Add checksum hashing to files stored in Design Stu...

Re: SSO User Provisioning

Re: Invalid Module: #template-wrapper > table:nth-...

Re: Issues sharing our landing pages on Twitter, a...

Re: How to center a form on a landing page?

Re: Marketo High Resolution Icons

Re: Fix code alterations that occur when sending e...

Make ContentAI Accessible When used in Emails/Allo...