Grégoire_Miche2

Grégoire_Miche2 · ‎06-05-2019

When using link tokens in emails, the formatting is rendered based on classes and CS that was included in the definition of the token at program level. This triggers various issues: the user who is setting the token and inserting it in the email is not necessarily versed in CSS If you need to use the same token in different emails places with different formatting, you are stuck with one rendering only. You could use some classes, but it gets very tricky and anyway will not work for email clients that support only inlined CSS So we need a way to be able to set the styling of a link token at email level, rather than at token level. it would take the form a new mktoLinkToken element that one could insert in the template and that would take as an input and link token, but that would be styled using the email template code. The element would enable to select only link tokens in a token selection list. The element would take some attributes such as "mktoTokenClass" and "mktoTokenStyle" to provide the template designer with a way to define the classes and styles to use, and "mktoLockTokenStyle" or "mktoLockTokenClasses" to enable or disable changes to what is set at the template level. And of course, the element would render correctly on HTML AND TEXT versions. -Greg Justin Cooperman‌

Grégoire_Miche2 · ‎06-05-2019

I wanted to add this idea: https://nation.marketo.com/ideas/9818 but I can no longer edit the post. -Greg

Grégoire_Miche2 · ‎06-05-2019

The new "Link" type of program token do not render as expected in the text version of the emails: Instead of rendering the display text and the URL, it renders the whole <a> tag: <a href="http://engage.awe.fr/G0Y0R4000T0pY0oY00000h0" target="_blank" title="This is a title" class="mchNoDecorate" id="2356" Display text</a> Not good! Justin Cooperman‌

Grégoire_Miche2 · ‎06-05-2019

In such cases, search the Ideas section of the community. Existing ideas will tell you what you are looking for is not possible, and often, comments to the idea will give you the workarounds, if any. And vote here: https://nation.marketo.com/ideas/8219 -Greg

Grégoire_Miche2 · ‎06-05-2019

Hi Osman, The point is, these features that require additions or changes to the UI will not be done on the old interface, for various reasons (including cost of dev and complexity). It's one of the promises of Sky UI to makes these changes easier and cheaper, and therefore more likely to be done. So wait and see. and let's keep voting -Greg

Grégoire_Miche2 · ‎06-05-2019

+1 on the point, too.

Grégoire_Miche2 · ‎06-05-2019

The difficulty with these very widely spread acronyms is that the definition of "Qualified" is multifaceted: when you talk to various people, you get a different definition each time... Plus the fact that the A in MAL / SAL stands sometimes for "assigned", or for "accepted". The last drawbacks with the MQL/SAL/SQL acronyms is that the next step is not straightforward. This is why we prefer and usually implement: Conversation Ready or Call Ready (Meets the criteria to be qualified and called. Next step is picking the phone and calling) Sales Ready (Meets the criteria to be managed by sales, lead is handed over to sales) Opportunity (= Sales accepted, an opportunity has been created). Greg

Grégoire_Miche2 · ‎06-05-2019

He use an LP with a form with the 2 fields (old email, new email) locked. The person has to visit the page and just click the summit button. We could just fire the validation on web page visit, but usually, customers will go for that secure validation. -Greg

Grégoire_Miche2 · ‎06-04-2019

In theory there is no limit. Practically, over 1Millions leads, you need to start paying attention to performance optimization (and even above 700k, from my experience, if you are running a lot of smart campaigns). Adobe is pushing Adobe Campaigns rather than Marketo for customers who need to have 10 millions + leads in their database. Keep in mind that the licence cost is directly linked to the number of leads in the database, though. -Greg

Grégoire_Miche2 · ‎06-04-2019

The best practice is indeed to provide a "change email" functionality to your preference center. The way we usually do this is with a process that also checks the new email address. So, when the user enters her/his new email address into the "change email" form he/she is sent and email with a link to be clicked in order to validate the change. And to prevent false (phishing software) clicks the person has to come back to an email change validation page and revalidate the change. This seems heavy a process, but GDPR is at this cost : you cannot allow someone to change their email address and provide that of someone else, lest a serious potential GDPR breach be created. Greg

Grégoire_Miche2 · ‎06-03-2019

Hi Monique, Have you searched the community for "SugarCRM" keyword ? Quite a lot has been written on this. Bottom line being that the custom integration works better on V7 than it did on v6, but still has some weaknesses. Also, search the launchpoint for partner solutions, some exist that do a better job. -Greg

Grégoire_Miche2 · ‎06-03-2019

Hi Elin Pedersen‌, This might work in email editor v1, but not sure it will in email editor v2. I would rather use different modules in email templates v2 than this kind of hack. One module with the intro and another without the intro. It will also have the positive advantage of generating a slimmer code, without unnecessary comments when the intro is not used. -Greg

Grégoire_Miche2 · ‎06-03-2019

Hi Nicole, Make sure you are using the latest version of the MSI package in SFDC. Run an upgrade (simply reinstall the package) to make sure. -Greg

Grégoire_Miche2 · ‎06-03-2019

Excellent post, thx Grace Brebner‌

Grégoire_Miche2 · ‎05-29-2019

Hi Agatha, That's not that easy. You will have to use subprograms. When you do this, you actually send the content through a smart campaign. You can use that smart campaign with choices to manage at each step of the stream what content should be sent. Here are some readings: https://nation.marketo.com/community/champion/blog/2016/03/14/conditional-sends-in-an-engagement-stream https://nation.marketo.com/blogs/marketowhisperer/2015/10/22/engagement-programs-with-nested-programs-when-do-you-really-get-that-email https://nation.marketo.com/community/champion/blog/2017/07/14/engagement-program-hacks-for-variable-cadence-and-more -Greg

Grégoire_Miche2 · ‎05-29-2019

You are welcome -Greg

Grégoire_Miche2 · ‎04-29-2019

Hi Riz, With regards to web personalization for anonymous leads, there are many solutions on the market, and it is difficult to establish a best list, as most provide roughly the same set of functionalities. When it come to known leads, Marketo WP being tightly integrated with Marketo Lead Management, that create a substantial differentiator for Marketo, as, though list sync, you will be easily able to exchange targets between the 2. -Greg

Grégoire_Miche2 · ‎04-29-2019

You are welcome

Grégoire_Miche2 · ‎04-23-2019

Running the merge through the API is the only alternative. When running it manually, this is the only possible behavior. Vote here: -Greg

Grégoire_Miche2 · ‎04-23-2019

Acuqisition program ID is supposed to be a number, length 18, number of decimals 0. Anyway, asset ID's in Marketo are most of the time 4 or 5 digits, and I have never seen more than 6 digits. So do not bother too much on this. -Greg

Grégoire_Miche2 · ‎04-21-2019

Then vote for the ideas listed here: -Greg

Grégoire_Miche2 · ‎04-21-2019

Also remember that if you really want to get rid of fields, once you have hidden them, you can ask support to "deep hide" them. This will remove them event from the admin -> field management section. -Greg

Grégoire_Miche2 · ‎04-21-2019

Hi Amanda, Remember Marketo does not duplicate contacts when they come from SFDC but does merge on import into Marketo. So migration scenarios should always be in this order: Dedupe as much as you can from your old Marketo and SFDC. These will be the enemy, as any dupe in the old system will create uncontrolled reassociation on import in the new Marketo. Migrate leads and contacts from SFDC to SFDC Sync the new SFDC with the new Marketo. This will push the whole SFDC database to Marketo Export the remaining data (additional fields, non-sync'ed/Marketo only records) from the old Marketo and import it into the new Marketo Export and import all static list you need to reconstruct legacy (static lists, program membership, ...) information in the new Marketo. When doing so, I usually limit the exports and imports to email addresses. Greg

Grégoire_Miche2 · ‎04-12-2019

Hi Luben, What simpler solution are you referring to ? Using lead tokens as default values ? It will work but relies a lot on user making no mistake and forgetting nothing when creating the forms. The other solution in the comments is the same one as the oneI refer to and requires some JS. -Greg

Grégoire_Miche2 · ‎04-12-2019

As already written there, all the power of the editor is linked to the quality of the template you are using. There is still room for improvement, though. Read this: Email editor 2.0 is leaving room for a v2.1 -Greg

Grégoire_Miche2 · ‎04-11-2019

I suppose most of you have seen the warning about form prefill when login in to Marketo today. If you have not read the related article, you should do it as it has a major impact on one of the most used feature in Marketo... Honestly, I am surprised by the suddenness of the announcement. Has any of you been warned ? Obviously, the issues with prefill on computers that are shared or when people forward emails to each other have been known for a long time. But yet, why such a sudden change with such a short notice ? I suspect there are some legal concerns behind this, a far consequence of the GDPR and similar regulations, as all actors in the chain might become liable in case of data theft. if you want to keep getting the same behavior as before, it will be time for everyone to master Sanford Whiteman's technique described here : https://blog.teknkl.com/pre-fill-any-site-any-form/ as it will become necessary on Marketo landing pages as well. - Greg

Grégoire_Miche2 · ‎02-27-2019

And BTM, I see 2 solutions : Use a token that post the list of values in a hidden place in the landing page and some JS to modify the droplist values using this list. Use a web service that you call on form load to retrieve the list of values. This second way would also work on embedded forms. The web service you use will have to provide very fast response time. -Greg

Online Status	Offline
Date Last Visited	‎07-19-2021 12:24 PM

Date Registered	‎11-26-2014 12:29 AM
Date Last Visited	‎07-19-2021 12:24 PM
Total Messages Posted	9,470
Likes Received	13683

Top Badges Earned

Link token formatting in email editor: have a spec...

Re: Email editor 2.0 is leaving room for a v2.1

Link token in text version of the emails

Re: Block Edit Code Option from Some Users

Re: See Tokens used by

Re: Preventing Reports from being sent if no data

Re: Guide to MQL, SAL, SQL Tracking and Definition...

Re: Workaround for unsubscribe with an email addre...

Re: Leads in Marketo

Re: Workaround for unsubscribe with an email addre...

Re: SugarCRM > Marketo integration

Re: Email template: mktoText inside a mktoBoolean ...

Re: Has anyone using Marketo switched to SFDC Ligh...

Re: 5 Email Myths You Need to Dispel

Re: What is the best way to prevent a lead from re...

Re: Align Checkbox to the left in Forms 2.0

Re: Marketo's Web Personalization

Re: Merge contacts in SFDC

Re: Merge contacts in SFDC

Re: Acquisition Program ID Field Length

Re: Marketo's email editor is obviously terrible

Re: Will hiding fields in Marketo speed up SFDC sy...

Re: Migrating Static Lists to New Instance

Re: Important Change to form Prefill

Re: Marketo's email editor is obviously terrible

Important Change to form Prefill

Re: "Select Value List" program token type