SanfordWhiteman

What exactly do you mean "an external source"? You referred to a product page linking to a form on another page. If the product page "knows" the data you wish to push to the form, then you add it to the URL as I showed.

Alerts would be generated by a Flow step that looks for the form you're currently posting to.Maybe you're using a new form and your Flow looks for an older form name....

You're certainly on the right track. My question is: is the Segmentation literally called utm_source with options GuideA and GuideB? Because all of those would have to match up if you want the LP to take the seg from the query string.

If you don't have an SSL certificate bound to your landing page domain (which I agree, you do not) why are people trying to connect to the form of your site?199.15.212.17/443 --> this is a response from port 443, i.e. the default SSL portNo way is the RST in your packet trace coming from a standard...

Add a CSS !important rule:.mktoForm { width: auto !important;}

Field Actions >> Block Field Updates

Make sure that field is set to allow updates from form posts.

When posting to the Community, please provide your actual URL. There's no reason to conceal that info here, and it just makes issues harder to troubleshoot.Did you upload an SSL certificate to Marketo for your landing page?

If the segmentation is itself based on a (hidden) field you can add to a form, then yes, add the field and then use Visibility Rules to "segment" the form.

You can't really "embed" a survey in an email. Putting a functional HTML form in an email is a no-go.You can fake the look of a form within an email body by using images for checkboxes, radio buttons, buttons, et al., and then have each one link to a particular URL (meaning, in practice, you can't ...