Badges
Accepted Solutions
Likes Received
Posts
Discussions
Ideas
Blog Posts
I faced the same a issue a few days ago. One of my team mate put the token as the default value in the form hidden field. Just go to one of the lead with this source and look at the activity log. You should be able to see the source of this value.
Some of these might already be pointed out but here is my take: SFDC Field sync: As of now, Marketo sync all the fields visible to marketo user in SFDC automatically and if we already have a similar field existed in Marketo, it creates a duplicate. We have to go to Marketo support to merge those ...
I have used Zapier and confirm it only updates marketo based on email address. At the same time, agree to Sanford, why are you syncing data back in Marketo? Since you mentioned Zapier, assuming you are using Zapier email parser, why don't you send SMS from Zapier itself?Regards,Amit
Interesting, I believe you have created a middleware for the lookup using REST API, right? Or is there any way to directly lookup the data using JS (munchkin API or form 2.0)?
You can consider enabling a composite key for the lead records in Marketo. You can have a product_code assigned to each of your products and ask marketo to switch the de-deupe key from Email address to a composite key i.e. Email Address + Product Code. This way you will have a different records for ...
If the number of contacts are limited, you can try putting that in RCE as an filer on email address. I don't see any other option available for such reports.
Try putting the CSS "display:${variable};" into the section instead for each content block and add "!important" in the end, it will look like "display:${variable} !important;"
Hi Ankit,I guess the issue is with following lines: var customForm = document.querySelector("#commandDEsk2_form"),customFormButton = customForm.querySelector("input[type='button']");can you try instead: var customForm,customFormButton ;customForm= document.querySelector("#commandDEsk2_form");customF...
Hi Arpit, As Sanford mentioned, there is no CSRF (Cross-site request forgery) requirement for the marketo forms.For your information, A CSRF token is a unique, secret, unpredictable value that is generated by the server-side application and transmitted to the client in such a way that it is included...
Sorry I meant "Now" instead of "Not".. corrected now.