Jerry_Yi

Jerry_Yi · ‎12-21-2017

Appreciate the quick reply. Yea, I ended up going your route of putting everything in smart campaigns as I built out the program. Just felt simpler and better visibility when all the flow and smart list logic were grouped in a single location rather than split between transition rules vs smart campaigns. Anyways, thanks again for your help!

Jerry_Yi · ‎12-19-2017

Hi Erik, Great article and super helpful. Just had a quick question regarding set up instructions under the section called "Entry to nurture and Custom Object." Based on your screenshots it looks like the smart list and the flow is being set up in a smart campaign. But could we also do the same thing under the first stream's transition rules/flow? If we have to use a smart campaign, is there anything special we need to do with the first stream's transition rule/flow or just simply leave it at its default? Seems like both ways work, just wanted know if you chose the smart campaign path for any particular reason. Best, Jerry

Jerry_Yi · ‎07-24-2017

Yup, this one works and delightfully silly too.

Jerry_Yi · ‎07-24-2017

Is there any way to configure/turn off Marketo's heavy-handed HTML validation? We use email scripts and my.tokens to generate a dynamic URL in our emails. The token's output is a full anchor tag (and only the anchor tag), i.e.: <a href="our.dynamic.url?ourparams=here"> In our email template, the code looks something like this: {{my.dynamic_url}}Hyperlinked element</a> The result is that Marketo's editor strips out the close "</a>" and essentially breaks the template. And there seems to be no way to keep that closing anchor tag from being stripped out. I feel like the top suggestion will be to modify script token to output the entire anchor tag + linked element + close anchor tag. But I don't think that's a workaround that scales well. For cases where including the linked element is too cumbersome for the template, or in cases where we'd want the linked element to be dynamic as well.

Jerry_Yi · ‎06-20-2017

Thanks for the doc link, but unfortunately I've read through it previously and wasn't much help in explaining why these two lead object fields are missing from the link field list for the "lead" link type. Both fields are string types, and both a part of the lead object, but doesn't show up in the drop down menu when trying to select a Link field. Is my understanding incorrect and that first/last name are no considered a part of " any custom fields in the list." mentioned in the documentation? RE: linking to unique ids and fields. I agree is the better route, unfortunately it's not quite a option for us in this case. Our data lives separately (and in this case, incomplete) we were hoping to use Marketo to join our two data sources together while relying on less than ideal join criteria. Our custom object would be keyed off of first and last name combined. We're looking to supplement our contact records with the additional meta data in this new custom object, which is unique per first/last name. Joining that to our contacts is a many-to-one relationship unfortunately due to legacy dupes. But I can't seem to even get started without being able to link the custom object on first/last name.

Jerry_Yi · ‎06-20-2017

I'm trying to setup a new custom object that would link to our lead/contacts on first and last name. Our lead/contacts all have first name and last name fields. But when trying to setup the link field, I can't seem to find those two fields in the list. Steps to reproduce: Create new custom object Create new field Set data type: link Set link object: lead Look under link field for first/Last name. Are there restrictions to link fields or am I missing something to allow links on first and last name? Unfortunately linking on email address isn't an option here.

Jerry_Yi · ‎05-30-2017

Haven't been able to find anything on this (or most likely haven't been searching correctly), but recently ran into something unexpected when trying to use scripting to dynamically set a UTM param value. The setup: My token: Name: {{my.utm_term}} Script: #if (${lead.Segmentation_Plan_1002} == "Asclepius" || ${lead.Segmentation_Plan_1002} == "Default") lead #else upgrade #end In email template: <a href=" https://marketo.landingpage.com/pagename.html?utm_term= {{my.utm_term}}"> When previewing the email above, the URL in the preview shows up correctly where {{my.utm_term}} is replaced correctly with either "lead" or "upgrade". However, it doesn't work at all when clicking from a sent sample email. Instead the value shows up as "${my.vUTM_TERM_4645}" where the last 4 digit number changes between emails as well. Not sure how to get this to work correctly or why it's showing up this way in the email send but not on the preview. My workaround: Instead of passing "lead" or "upgrade", I just constructed the full anchor tag in my token script and replace the anchor tag in the email with the token.

Jerry_Yi · ‎05-24-2017

Hoping someone else has figured out a solution to this. I'm trying to using a my.token to populate the body content of an SMS that's being sent via Twilio. This way we only need to set up one webhook and then set a unique message by campaign. The value of the token current passes through correctly, however it also includes double quotes around the whole text as well. Has anyone figured out a way to remove/not have my.token values not be double quoted?

Online Status	Offline
Date Last Visited	‎01-28-2020 02:05 AM

Date Registered	‎04-03-2017 04:22 PM
Date Last Visited	‎01-28-2020 02:05 AM
Total Messages Posted	8
Likes Received	1

Top Badges Earned

Re: Engagement Program Hacks for Variable Cadence ...

Re: Engagement Program Hacks for Variable Cadence ...

Re: Preventing Marketo Email Editor from stripping...

Preventing Marketo Email Editor from stripping out...

Re: Custom Objects - Link field missing lead field...

Custom Objects - Link field missing lead fields

Velocity scripting - passing a value to query stri...

Using my.tokens in Twilio SMS body results in doub...