Badges
Accepted Solutions
Likes Received
Posts
Discussions
Ideas
Blog Posts
There is no built-in ability to do this. You also have to realize you're fighting a losing battle: if a recipient's mail server is intent on flagging your emails as spam even if you only sent to 17 addresses in an entire school district (which I'm assuming has at least 1000 email addressses, right?...
@Laura K if you export a list of suspect addresses it'll be simple for a techsavvy person to see if the domains have MX records. That would quickly have detected the @gmail.com.com error. You could also build a webhook to do the same thing on the fly -- I'm sure there are some paid webhook service...
That's right, they do not go in the URL. The form is submitted using the POST method so they go into the body of the request.
@Megan R are you still experiencing the earlier behavior, even with the cookie being overridden with that script snippet and the Munchkin tracking code not loading?
The import procedure should not have used Web2Lead at all. Perhaps you have a Flow step that is calling the Web2Lead endpoint for some reason?
The POST URL for a form is https://
Like any URL param, this can be captured into a hidden form field. You can then automatically submit the form (the user doesn't need to know this happened!).
Where are you publishing this schedule so it can be accessed via the web? That's the first question. Bringing it into the LP follows from that.
[a] You are not using whenReady() on that landing page now.[b] You are still trying to use loadForm() but the call to MktoForms2.loadForm() actually appears in the HTML before the Mkto forms.js is loaded, hence the loadForm() fails (you can see this in your Web Console).
I meant the actual URL. Unless you are working for that porn site, which is fine, but the page does not exist.