These pages and web services will either save and/or return data.
Ajax was originally an acronym for Asynchronous Java Script and XML.
Effectively it looks like you can't change the display value of a control via model value updates on a Postback operation. I have a small section in a document where I display an editable email address: This is what the form displays on a GET operation and as expected I get the email value displayed in both the textbox and plain value display below, which reflects the value in the mode.
I added a plain text value to demonstrate the model value compared to what's rendered in the textbox.
Postback tracking is required for offers that don't direct to a website, notably for mobile apps.
If you want to start session tracking on impression or measure view-through conversions, you cannot use postback tracking for that offer as well.
Ajax is a client-side script that communicates to and from a server/database without the need for a postback or a complete page refresh.
You must set that offer to use pixel-based tracking.
Working directly with the TUNE Marketing Console is the exception to this.
The above code also demonstrates the click events of the Button control.
Normal server side logic can be implemented in the function assigned to onclick attribute of the Button control.