Content Ignite Requests

Content Ignite Requests

Content Ignite Requests

When adding Content Ignite Ad Code to your site and your visitors load it through their browser, Content Ignite initiates certain requests which are needed to track usage:

Scripts (.js files)

https://cdn.tagdeliver.com/cipt/xxxxx.js (where xxxxx is the site UID)
This file is our core product and contains everything needed to load an ad. It will make one call to our API to determine any legal requirements (such as GDPR) before proceeding to load ads via the Google network.

Note

All XHR requests appear to occur twice. In reality this happens because unlike simple requests, these are “preflighted” requests which first send an HTTP OPTIONS request header to the resource on the other domain in order to determine whether the actual request is safe to send. Cross-site requests are preflighted like this since they may have implications to user data.