Hi Bonnie,Short answer: triggers act as OR operators (so it would look to see if someone has either filled out form.) What you can do as a workaround is set up a trigger with the s...
Hi Jay,From what you're describing, it sounds like this email is coming out of your Marketo instance--and since this is something that's made by users rather than by Marketo themse...
Hi Sherry,This can be done, but it may not be in as traditional a manner as you'd think. If you make A. xxxxB. xxxxlinks, you can assign them unique IDs (i.e., <a id="optionA" href...
Hi Sheena,A couple of ideas since you mentioned that everything had worked prior to this week:If you can take a look at the records that are coming through with your form, see what...
Hi Marisa,Just a quick follow-up: while I'm waiting for Part 4 of an ongoing Google Analytics + Marketo series I've been writing to post to be put up (so I can, in turn, combine th...
Hi Ariel,In this case, you're going to want to set up twin fields: one to record the value stored the first time and then map the data into your "real" field in the backend. For in...
Hi Malik,Generally, the recommended way of recording assets that don't inherently have the ability to be tracked is to have a go-between page firing JS that quickly records a faux ...
Hi Kelly,First off, thanks for taking the initiative to share this! I feel like Marketo's own documentation is a little weak in this respect, since it only lists permissions withou...
Hi Phillip,I suppose it depends on whether it's human error or bots performing this behavior, but I've been using mailcheck.js to handle instances like this when it's human error a...