Like Jay says, if you can name the images in a URL-safe and consistent fashion, then you don't need additional logic to figure out the URL as you can simply reuse the fields. However, if you try to do it this way, I definitely wouldn't use the first/last names, but rather the owner's email address, for 3 reasons: Only a tiny fraction of the characters that are valid in those owner names are also valid unencoded in a URL, and the moment you have any exceptions the setup can't work (while the same is technically true of the "@" and "+" in emails, in reality those characters do not need to be encoded in files hosted on Marketo) Owner email addresses are relatively static, compared to first names and last names (even nicknames and name changes due to marriage/divorce usually keep the old email address around as an alias) Owner email addresses are unique, first and last names are not (when you work in large global orgs and set up your 5th account for an Ankur Sharma, this becomes top-of-mind!) I still approach such projects with trepidation and bookmark them as relatively fragile, no matter what. Using Velocity allows you to properly percent-encode URLs, which a lot of people don't realize is even a thing.
... View more