SanfordWhiteman

No, it’s not possible to have a link be click-tracked but excluded from aggregate reporting on clicks. (Within the UI, that is. You could pull the data via API and report on it yourself however you want.)

A few important questions:1. Your app is generating the entire HTML (and presumably text) body of the email?2. What is the max number of personalization fields you'll be using, say to the nearest 20? (Across all such emails and leads.) 3. What are the datatypes of the fields (Boolean, Number, String...

When posting code, you must use the syntax highlighter (“Insert/Edit Code Sample”) for it to be readable. In any case, you must output the entire tag (through closing ) from Velocity for this to work, as noted in many earlier threads.

I like the idea of breaking from the template, assuming the relevant emails can be “flattened” from this point onward. Unfortunately, afaik there’s no way to mass-break emails using the API, so like you said it’s not quick.

This works only on Marketo hosted pages.To be pedantic, the source is expected to be a Marketo-hosted LP, but the redirection target can be any URL. And in fact the source URL need not be in Marketo anymore, it just needs to have existed when the rule was created — if it’s been deleted, you can use ...

Once the new brand landing page is ready, is it possible to redirect the old landing page URL to the newly branded version? Alternatively, could I unapprove the old page and then reuse the exact same URL for the new landing page?You can do either of these.

Also note the Velocity code you posted has fatal syntax errors. There’s no way it ran like that (missing leading # in 2 places).

@GroovesMcFly you seem not to have returned to your thread. Remember to read responses from our volunteer community.

I might be misremembering, but I recall hearing that you can’t have two Marketo instances connected natively to the same SFDC org at the same time, since the real-time sync for the second instance won’t function until the first one is disconnected. My understanding was that the second instance could...

Naturally id is not a required column when using email as the lookup field. id is not writable, and you’re not using it to look up, so it should not be in the CSV at all! Why are you including empty lookup fields? You know those will fail, and it’s trivial to strip them out of the CSV before sending...