After looking into your query, I can assure you your error is related to an outside issue from the Twitter tracking pixel. I verified on both Chrome and Firefox (52.0.1 64 bit) as well as queried logs to make sure our front ends received the pixel data. See screenshot of tag fire with 200 response ->
There could be an extension running or some other code on the page that is altering JS type to an invalid type. Which would have made it look like our tag type was setup incorrectly.