Badges
Accepted Solutions
Likes Received
Posts
Discussions
Ideas
Blog Posts
Happy to help, Elicia.
Hi Greg,You can do this with the Company Name smart list filter. You can grab your list and add it to the filter by following these directions(https://community.marketo.com/MarketoArticle?id=kA050000000LGFwCAO). This will match against any lead or contact with the corresponding company name.
Hi Elihn,Can you clarify what you're trying to retrieve? Are you trying to see what fields a lead filled out during a form fillout? If so, you can view this by going into the lead record, and finding the form fillout event in their activity log, then drilling into it by double-clicking. This will...
Hey John,Can you give an example of example of generated XML which is giving this bad parameter error? It's diffuclt to determine from trying to inerpret code.
Hi Dane,When a wait step completes, the flow will execute whatever currently exists in the flow of the campaign, so in your scenario a lead that entered the wait step when the flow was in version 1 but leaves when the flow is version 2 will have the behavioral score reduced, not the activity score.
Hi Biao,I'm not certain why the WSDL is not available at the public URL, but you can access it for your instance specific SOAP URL. You can access it at the following: https://***-***-***.mktoapi.com/soap/mktows/2_7?WSDL
Hi Katie,Do you have any -webkit or moz specific CSS in your page? This would explain the difference in behavior.
Hi Melissa,The send email flow step will always send the current version of the email as it is approved, so you can safely edit this. Anyone who unsubscribes before the second send executes will not receive the email either.
Hi Anders,I'd highly discourage you from executing rest calls in Javascript on the page. This exposes your access token publicly, which can allow your session to be highjacked. It's far safer to execute the REST call on the server and then put the needed results into the page which loads for the u...
Hi John,Segments cannot dynamically update on date ranges, since segment changes trigger on data value changes. Date functionality is still preserved for certain use cases like birthdays, but fields like this cannot work the way you expect. To manage this, we usually suggest create a second boolea...