Dan_Askin

With the code fixed, expected OR has been restored. Thanks, Sanford.

Thanks for looking out, Sanford. Appreciate it as always. Check out line 18. I think I need to close the IE conditional comments.Here's the end of the code (incidentally, the original markup doesn't have that many tags):Will have another chance to test on Thursday morning.

Same deal with today's game preview. 60% CTO, standard clicks and a bizarrely low OR. A full list send (different template) that went out Wednesday had no issues.

Sanford, I thought you were a Saints email subscriber. Code hasn't changed from last season, but I'm going to go through it and see how things go Friday.

It's was consecutive Fridays (2 sends total) -- again with just one email template. And would a blacklist cover 75% of clients, which coincidentally were also the poorest engagers, ie OR was gutted, but CLTR and click metrics were in line with expectations for each send. My gut tells me it has somet...

Thanks, Josh. We've sent subsequent emails with no issue in OR. This seems like an outlier -- especially given the CLTR is entirely within an expected range (there's no saying that expected range hasn't always include bot clicks, of course). We haven't seen the erratic click activity you reference i...

You got it, Sanford -- politeness is where it's at. Good call on the hidden field attribute/aux fields approach. Appreciate the insight.