Hi Saba,

I'll take a shot.

1. This is a tricky use case. I'd try to figure out a better trigger. Ideally the server that is building the html page could populate a variable in the head that could be picked up by Target with the TargetPageParams function. Though technically you could add some JS to the page that checks for the div and then fires a getOffer() that qualifies for the activity. This presents flicker scenarios though, as this second request will most certainly fire after the page has begun rendering.
2. Yes. If you modify the edit at.js settings you need to redownload and re-deploy the file.
3. The token parameters listed in the create profile scripts page will update if you switch to mbox vs profile.
   1. Model and subcat are the names of custom profiles that were used in this example. They were sent over an mbox request with the "profile." prefix.
4. I think that's the primary stuff. You might find some stuff on github, but I think that's more the SPA extensions.