I have blocked resources in Google Analytics

I have placed your code on roughly 150 pages

39 of of site pages are blocked

IS THERE A VERIFICATION CODE i MUST PLACE IN THE HEADER??

It states:

Recommended: HTML file uploadUpload an HTML file to your site.

Can you please tell us which of your form have the Google Analytics widget on it? 

I checked your website and I found the pop-up form https://www.jotform.us/form/62794506158161   on it. But the form was not using Google Analytics.

We will check further once we have a better understanding of the issue.

Thanks.

There are three pop ups

1) social media buttons

2) Blue bar at the bottom of the screen which allow people to click to request information

3) 4.5 delayed pop up for a Free Consultation

<script src="https://form.jotform.com/static/feedback2.js?3.3.REV" type="text/javascript"> new JotformFeedback({ formId: "62804356902153", buttonText: "CEO's Take Actionable Steps | Request Info Now", base: "https://form.jotform.com/", background: "#2c3184", fontColor: "#FFFFFF", buttonSide: "bottom", buttonAlign: "center", type: false, width: 680, height: 880 }); </script>

<p>

            {C}<!-- Go to www.addthis.com/dashboard to customize your tools --><script type="text/javascript" src="//s7.addthis.com/js/300/addthis_widget.js#pubid=ra-57fbe7a7107101bf"></script><script src="https://form.jotform.com/static/feedback2.js?3.3.REV" type="text/javascript"> var JFL_62794506158161 = new JotformFeedback({ formId: '62794506158161', base: 'https://form.jotform.com/', windowTitle: 'Request Consultation Contact Form', background: '#FFA500', fontColor: '#FFFFFF', type: 'false', height: 1200, width: 675, openOnLoad: false }); </script></p>

<p>

            <a class="btn lightbox-62794506158161" style="margin-top: 16px"> Business Owners | Request your Free Consultation </a><a class="lightbox-62794506158161" id="lightboxdelay" style="cursor:pointer;color:blue;text-decoration:underline;display:none;"> Business Owners | Request your Free Consultation </a><script language="JavaScript">var delayseconds = 4.5;    function pause() {    myTimer = setTimeout('whatToDo()', delayseconds * 1000)    }   function whatToDo() {document.getElementById('lightboxdelay').click();    }window.onload = pause;</script></p>

<p>

            &nbsp;</p>

The homepage of your website is having only one popup embedded form, it does not have any forms in the header nor the codes you have copy pasted. This is the homepage we were looking at:

http://peakperformancesalestraining.us/

However, when inspecting the warnings you have copy/pasted from Google's site for webmasters, there is actually nothing wrong with the warning you are seeing.

The cdn.jotfor.ms domain is where we store resource files for our forms - this is not something that should be indexed by search engines or tracked by Google Analytics. Essentially, this is where we store technical bits of your forms, such as the theme CSS files, scripts, and images that your form uses internally.

cdn.jotform.ms is not a site that should be crawled or indexed by Google and similar services. It only contains back-end files for your forms. Even if this site could be crawled, it would not provide any valuable information.

You still receive Google Analytics for the important and valuable events, such as loading of your actual forms. Just not the loading of the files from the back-end, and this is normal.

Please let us know if you need further assistance.

the home page is not being blocked

IT IS 39 OTHER PAGES THAT MAKE USE OF YOUR FORMS

I AM NOT LOOKING TO INDEX YOUR FORM, HOWEVER IT IS YOUR FORMS THAT ARE CREATING A BLOCKED RESOURCE FOR 39 PAGES

From what I understand it seems you pretty much are having an issue with a lot of your site resources being blocked after using our service that you've tracked to one of our script domains.

As far as I know my colleagues have provided you with information on what we know but for some reason you're still experiencing a lot of blocked stuff.

Since other than what we've stated above I think it would probably be better for us to check with our developers to take a look and assist to answer this issue more accurately in case there's something we can do about it to fix it somehow perhaps. As soon as more is known we'll update you again.