SanfordWhiteman

You can already do this, pass {segmentation}={segment} in the query string (like country=US).

Right, you've set up an OR condition as it's always OR.

I shudder at the storage overhead of such an idea (which amounts to storing infinite snapshots of lead changes).

VRs are OR. What are the exact conditions -- are they 2 conditions on the same field?

They must not have read https://blog.teknkl.com/multiple-forms-multiple-times/While I wouldn't expect the everyday Marketo user -- like you! -- to have read it, if they're touting a Marketo integration, they have to go the extra mile and learn the well-established tricks of the platform.

It's possible to have the same Marketo form, multiple times. It's Wistia's problem that they don't understand how to do this.

Can't say I agree. This could cause massive resource utilization on the server side as you're tuning your filters. I prefer that nothing be run unless it's approved.

Can we just say "Velocity Script Editor in Sky is broken"? 'Cuz that's the way I'd put it, given that it seems to read the token from the API and not realize it's supposed to, like, parse the JSON.

This can't really be an "Idea" until the Marketo database itself supports per-lead images. You're forgetting that there's no database support for this object type. So it doesn't matter that there's no form input type because there's no place for it to go.In any case if you search the Community for "...

s "this is v@lid!"@example.com. Yes, that is valid per protocol. No, you're probably not going to get much email to it with today's setups. Caveat emptor.Well, a standards-compliant mailserver must process that fine. The older the server software, the more likely it supports it, not less. I guarante...