SanfordWhiteman

@spogula please return to your thread and check responses.

You don’t really have the mind-reading ability that’s suggested here. Yes, some people may not mean to opt out of all your brands. But there will also be people who absolutely did mean that, and choosing the broader option is standard. In any case, it is possible to transform the Unsubscribed via Li...

Don’t know what you mean by “get CDN URL” as the Forms 2.0 library is already served via Cloudflare. 2-3 seconds is highly aberrant. This is the typical waterfall for an uncached forms2.min.js one of our instances. It’s never over 200 milliseconds: What is the actual URL you’re loading (don’t obfusc...

PHP’s own documentation explicitly warns against unserializing user-submitted data (PHP Warning) due to the potential for exploits through object instantiation and autoloadingWell, this isn’t fully untrusted data, as by definition each field name and value is stringified by the form listener. You ca...

2) Also, Velocity is case-sensitive and field API names must be exact.From your image:You wrote: $lead.Expedia_Hotel_Id__cBut the field shown is labeled: Expedia Hotel IdIn Marketo’s Velocity context*, it’s not possible for keys on the $lead object (i.e. Velocity API names) to have spaces. So the k...

1) If you’re embedding the URL in an tag directly with a Velocity token, ensure you don’t use curly brackets inside the href. Do it like this:TestingIt’s the absolute opposite! You should use ${formal.notation} for output as OP is doing here. You shouldn’t use it inside #directives. Did you even te...

3) Please add a null check in the Velocity script: #if( $lead.Expedia_Hotel_Id )Access Your Portal#elseAccess Your Portal#endThis check is useless. The lead field will always pass the check because it’s always a string. You will never enter the #else branch! Let’s let the OP make a decision about w...

What prompted my original post was the practical issue we encountered when using some standard CSV parsers — notably PHP’s native fgetcsv() and SplFileObject in CSV mode. In our case, rows containing checksumFields inside the Form Fields serialized data led to the parser treating the comma-separated...

I've seen interesting issues in CSV files for a global company with different delimiters being used, and different characters being used to denote 10^3 multipliers in numbers. An import CSV parser wasn't handling this well at all. It wasn't the fault of the people generating the CSV files, but the...

Serialization outputs : and ; characters which don't interact well with CSV exports.While the unfamiliarity of PHP serialization is undeniable, can’t see how this claim is defensible. : and ; are child’s play for CSV parsers, as they have no special meaning. (And of course they exist in JSON as wel...