Hey Mark,
I don’t think you’re missing anything, there are definitely some differences in how the new landing page builder collects and stores data, as compared to the older landing page and web form options.
So, there currently isn’t a “notifications” option for the new landing pages. (Though rumor is that they’re working on that)
The work-around solution is to add a sequence AFTER the landing page, and merge in the fields you captured, and direct that email to whomever needs to be notified.
The problem with this is that it exposes another shortcoming of the new landing pages - virtual fields don’t actually store their data anywhere.
So, you can collect info through a landing page in one of two ways - contact fields, and virtual fields.
Contact fields store the info back to the contact record, as you’d expect.
But virtual fields don’t actually store the info anywhere. They’re like temporary place-holder fields that allow you to collect info, without counting against your limit for custom fields.
But if they don’t store the info anywhere…then why are they useful?
The answer is tags.
The virtual fields (radio options, checkboxes, or dropdown fields) can all assign tags. That means that whichever option they select, can apply a corresponding tag. Then that tag is attached to the contact record, and can be used to start/stop automation, or to segment future searches and reports.
This means that, for now, the best practice is to apply a tag for any option you want to track - whether it’s checkboxes, radio options, or whatever. If you’re using a virtual field, then you should also be applying a tag.