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)

cdn.connectignite.com/srv/zzzzz/xxxxx/add.js (where xxxxx is the site ID & zzzzz is the product type)
This file is our core product and contains everything needed to load an ad. It will make various calls to our campaign serving platform, our core RTB bidder and tracking scripts for logging the state of the request. If no ads our loaded from our bidder application, this script will request and load additional pass-back scripts in the format cdn.connectignite.com/srv/passback/zzzzz/xxxxx/yyyyy/add.js where yyyyy represents a combination of slash separated identifiers.

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.

Testimonials from our partners


img01

Content Ignite® is an innovator in the space, and their brand and vision is a huge inspiration and keeps us challenging ourselves at Revcontent.

John Lemp (CEO RevContent)
img02

Content Ignite® has been a key partner for us and we look forward to working with the team in the future to fuel each others ambitious growth.

Mike Harty (Co Founder & COO PowerLinks)
img03

Content Ignite® was the first platform we worked with to deliver native advertising products onto our group of websites. They have been a most helpful, resourceful and inventive partner we have worked with, with very fast turnaround in SLAs.

Russell Winterburn (Friday Media)