title: Twitter tracking pixel causing MIME type error
body: <p>I'm trying to load <a href="https://business.twitter.com/en/help/campaign-measurement-and-analytics/conversion-tracking-for-websites.html" rel="noreferrer">Twitter's tracking pixel</a> on my Meteor/NodeJS website.</p>
  
  <p>The code they provide is:</p>
  
  <pre class="lang-js prettyprint-override"><code>!(function(e, t, n, s, u, a) {
      e.twq ||
          ((s = e.twq = function() {
              s.exe ? s.exe.apply(s, arguments) : s.queue.push(arguments);
          }),
          (s.version = "1.1"),
          (s.queue = []),
          (u = t.createElement(n)),
          (u.async = !0),
          (u.src = "//static.ads-twitter.com/uwt.js"),
          (document.body.appendChild(u)));
     })(window, document, "script");
  
  twq("init", "MY-TRACKING-ID");
  twq("track", "PageView");
  </code></pre>
  
  <p>It loads fine but returns the following error in the console:</p>
  
  <blockquote>
    <p>Refused to execute script from '<a href="https://analytics.twitter.com/i/adsct?p_id=Twitter" rel="noreferrer">https://analytics.twitter.com/i/adsct?p_id=Twitter</a>...' because its MIME type ('text/html') is not executable, and strict MIME type checking is enabled.</p>
  </blockquote>
  
  <p>This is the exact same problem as: <a href="https://twittercommunity.com/t/analytics-tracking-pixel-error-was-blocked-due-to-mime-type-mismatch-x-content-type-options-nosniff/83583/2" rel="noreferrer">https://twittercommunity.com/t/analytics-tracking-pixel-error-was-blocked-due-to-mime-type-mismatch-x-content-type-options-nosniff/83583/2</a>, but while that thread is unresolved he's running the Twitter tracking pixel on that site now, which suggests it's a server configuration issue.</p>
  
  <p>Looking at the code, this <a href="//static.ads-twitter.com/uwt.js" rel="noreferrer">uwt.js file from Twitter</a> it requests a script from <a href="https://analytics.twitter.com/i/adsct" rel="noreferrer">https://analytics.twitter.com/i/adsct</a> which Chrome is preventing from running.</p>
  
  <p><a href="https://stackoverflow.com/questions/24528211/chrome-refuses-to-execute-an-ajax-script-due-to-wrong-mime-type">This answer</a> suggests it's either a MIME type config issue (I'm running Nginx) or a header issue, but removing <code>X-Content-Type-Options: nosniff</code> and restarting Nginx had no effect.</p>
  
  <p>Any idea how to fix or better troubleshoot this? </p>