I'm a web, database, and network architect based in NYC, with specializations in the financial services, publishing, and SaaS sectors.
I build complex Marketo integrations for companies large and small... and can make Marketo forms and emails do things you never thought possible!
Check out my blog at https://blog.teknkl.com, which has Marketo-specific technical insights you won't see anywhere else, along with wider topics from my programming and systems work.
There doesn't seem to be a if "person is created today" option.
Of course there is (Person is Created [in time frame] = Today). But you don’t need that filter, because you want the...
This process marks the email as invalid even if the person actually received the email.
No, it doesn’t.
Delivered doesn’t mean the person received the email. It means the person...
I mean this feature is already present in many e-comm platforms of deduping based on email id.
Yes, but the OP‘s e-commerce team has consciously chosen not to do that. So the cur...
...there might be many cases which will have same first/last name using same generic email.
... but again, this is the situation the OP is already facing and trying to work around....
Not sure I understand the question. What is it about your current filter that’s tuned for unreliable data instead of reliable data?
It looks like you’re already looking for people...
CSV, no. But JSON, sure! You can populate a Velocity {{my.token}} with a JSON array* of your content, parse it using another Velocity token, and output it anywhere you want.Alterna...
It’s possible to have a compound lookup key using First Name + Email Address or Last Name + Email Address (Marketo Support can set this custom config for you).
But you certainly s...
You might’ve just groaned, “A whole post about the [in time frame] = Next Month filter? Ugh.”
Hey, give me a little credit. You might think you merely haven’t used it, but the r...