Michael_Langell

Guess I am fairly late to this party, although I assume I am not alone when I say not everyone has time to watch community posts like a hawk.    There are two things I am very disappointed in.    Marketo's inability to migrate over community users' data.  This is the 2nd migration where I have lost my bookmarks and subscriptions to interesting comments/issues .  What is the point of using the community if every couple of years, these migration projects occur where you lose half of the most important information to you?  Marketo's inability to effectively communicate these changes.  Why can't an email get sent regarding a major change like this?       Imagine if Facebook migrated to a new platform and told all its users - sorry, but you need to friend request all your old friends because we need to migrate to this new platform.  All the companies you follow you will need to re-follow.  Anything you saved will get lost.  Even better, they post this message on their corporate facebook user group wall and do not email any of their billions of users.  It would be the end of their platform!      Anyways I've learned my lesson - google chrome bookmarks are more reliable way to use this community.   ... View more

What do you use now that solves this problem? ... View more

Geoff Krajeski​ - Agree this would be helpful and thanks for adding to my idea.  As a slight Salesforce workaround - instead of using a formula field, you could have the formula live in a Salesforce workflow updating a normal custom field or have a formula field trigger a workflow in Salesforce which then updates a normal custom field.  Certainly more complex than just having your constraint filter in Marketo, but thought I'd post if it helped out.   ... View more

Thanks Sanford.  You are right after some confirmed testing.  Re-reading, this article looks correct.  Going to delete my comment ... View more

Interesting idea. Only issue I foresee with this, is depending on how the duplication settings of your instance are set up, you could have issues.  I believe out of the box > if the same cookied machine submits a form with different email addresses, two lead records are created.  If you are anonymizng those records because of GDPR > you will not want the above to happen because you will want the tracking to stay intact across one lead record ... View more

Agree with what Sanford is saying here for anyone who continues to have this problem.  I do not think the email is that important.  You are ultimately trying to drive individuals to view the physical posts, so the link performance is more what matters and as long as your links are unique and organized in some fashion, you should be set to report on performance. You can probably change the email every once in a while to test subject lines for open rates, but I do not know if you need to do much more than that       ... View more

Hey Mike, Thanks for posting!  I did not realize you could use that token in flow steps.  So in my use case, you would have the above flow in all the different webinar programs pushing that value to a different field DS_WBR6 DS_WBR5 DS_WBR4 DS_WBR... Each of the fields would have the respective attendee link to the webinars they signed up for.  As long as those links are getting copied into those fields properly, that should work.  Would need to test, but very nice catch Mike!!    ... View more

Hi Greg, Thanks for the info.  Did you do any testing post-upgrade for emails with NO template?  A majority of our emails have no template, we have just updated the HTML ourselves on a one-off basis.  I would assume there were probably no code/content loss with these, although I will likely still test.    Thanks, Mike ... View more

It seems like section 1-tests and discovery, point 3 may be inaccurate now.  It looks like you can edit v1 emails after turning on editor 2.0 without needing to attach a 2.0 template to it (Marketo documentation below).  It will automatically switch to a v2 email, but the template will be the same (v1) and there should not be any code/content loss.  Is this what Gregoire is referring to in the June 18th fix?   Marketo Documentation: Turning On/Off Email Editor 2.0 - Marketo Docs - Product Docs  When you create a new email, the Email Template Picker will display and you'll be able to choose from either a v1.0 or v2.0 email template. Email Editor 2.0 is backward compatible, so using a v1.0 email template is an option. Email Editor 2.0 can create and edit emails using v1.0 or v2.0 templates. Email Editor 1.0 will only be able to edit v1.0 emails or create new emails from v1.0 email templates. Whenever you create or edit an email with Email Editor 2.0 enabled, the resulting email will always be marked as v2.0 (even if you used a v1.0 email template). Point 3 Opening v1 emails in the v2 editor without upgrading the template : Once the new editor is enabled, it remains possible to create or edit a draft on a v1 email event if it's templates has not been upgraded to v2 . All the email drafts you create will be flagged as v2, even if the template is still v1 (a little weird). If you approve these drafts, the email is upgraded to v2 and the v1 is lost forever. This might have an impact if you want to preserve the capability to revert to v1 (see point 2 above). So, at least at the beginning and until you are fully comfortable, we strongly recommend that you clone them first. Once you are fully comfortable that all your v2 templates are fully operational, you will be able to edit the v1s. Thanks, Mike ... View more

This is a big need.  Huge operational burden ... View more

Grégoire Michel​ You can still use tokens in Editor 2.0 correct?  Variables do not replace tokens, they are just a similar feature.  Thanks, Mike ... View more

Sanford Whiteman​ can you do the same for trigger.referrer?  The above is not exactly the use case I am thinking of.  Basically, there are a number of instances where the referrer url is empty, but there is data in the query parameters, so we do have some info on the actual referrer then.  I'd like to be able to pull that data either into the referrer url or into a custom field via token.  So in the below case, we know that this visit was actually referred by Marketo.         ... View more

Agree with this.  Strange why this is the only constraint without a token.  Another big use case for this token would be pulling the query parameter info when the referrer url is unavailable. This becomes more important when taking into account the below which came from Marketo Support: Google has some restrictions in place that can sometimes prevent the referrer URL being captured. In general, there are a few things to consider when using Referrer URL. Many websites don’t allow for that information to be passed along any more. It used to be very widely used and very common practice, but more and more these days that data just isn’t utilized and many sites have moved away from providing it, which means that even if you have everything set up properly to catch that data in the form, if the referring URL does not actually pass that data along, there isn’t anything to actually capture in the form field. Referrer URL is somewhat unreliable because of this trend. -Mike ... View more

Duplicate Idea: ... View more

Hi Gerard, Cannot say I have an answer to that question, have not tested opportunities.  I would do one of the following: 1.  Create a support ticket and reference this discussion or my BetterCloud case 00582509, (not sure if they can see that if you call in) and ask about how it relates to opportunities.  2.  The easiest way to test this would be to take a field on the opportunity that is tracked in Salesforce, pull an opportunity history report.  Pull a report that displays only contacts with contact roles for those opportunities that have had the field change.  Create a smart list in Marketo on the same Salesforce field that should have the corresponding data value changed.  Make sure the time frames are the same.  Compare the email addresses/SFDC IDs in both lists.  If they are not the same, then the answer is Opportunities have the same problem. If I have some time, I will take a look at this myself, but we do not use the opportunity in Marketo so it does not effect us. -Mike      ... View more

Hi Diederik Martens​ The trigger will not fire because there is no change data value activity to fire upon.  I probably should have been more clear in my title/description that this is the major problem here.  Any Marketo customer who uses the data value changes trigger on account level fields will experience a failure rate where the trigger does not process.  Without the logged activity, it is if the change never took place. -Mike ... View more