This is not possible. The ITB needs to be loaded on a separate page from any other instances of the ITB.
We advise that you disable/hide your next button and submit the page in your jsFunction that is passed to the ITB.
You can find in depth information on status codes here.
Ideally, you would insert the itb.js script in the document HEAD and then call Quester.loadITB() with the appendId attribute after the page is loaded. This method offers you the most control over how the ITB is loaded on the page. Check out our examples page.
However, in our experience, our clients find it easiest to include the itb.js and immediately call Quester.loadITB() in the document BODY where you would like the ITB to appear. This method has proven to work well for most use cases. Check out our examples page.
The look of the Standard ITB can be changed through CSS. Check out our examples page.
You may consider using the Blank ITB if you are looking to seamlessly integrate the look of the ITB into your survey platform. Check out our examples page.
The ITB status and conversation data is passed as a xml string to your jsFunction. You may process the response xml in javascript, or submit it to your survey platform and process it there. Check out our examples page.
The ajax ITBs load two additional javascript libraries for you: json2 and jquery-1.5.2. Care is taken to isolate jQuery so that it will not affect any previously loaded version.
Yes there is! Check out our examples page.