Create a private (or public, I suppose… whatever your preference) web page on your Trooptrack site.
Edit the page, click on the top-left button in the web page editor. It looks like a page with “<>” on it and the word “Source”.
Take the “embed code” you located in step 2, and paste it into the Troop Track web page editor.
Click “Save Page” and you are done.
Now… after fooling with this for a while, I realized that I didn’t just want all my survey pages floating around in the TroopTrack, so I threw away my test pages, and created a new “top-level” survey web page called… “Surveys” (surprise!) – it doesn’t have to have anything on it, but now when you create more surveys on your TroopTrack website, you create them under this Page for organizational purposes.
But of course, I couldn’t just leave good-enough alone, so I went back to edit this Surveys page, and put a table on it, to create a single page where membership can see the surveys, their closing dates, and a link for Leadership to use to review the statistics of open surveys, and where I will archive the results for closed surveys.
Now… if all of this was functionality built directly into Troop Track, it would probably have saved me a few hours, but I can see now that in order to get all the features I would want, that this might be a “significant” programming effort on their parts. STILL… still… maybe it would be enough for our TroopTrack developer-geniuses to enable use of APIs so these things could be embedded a little more cleanly? For example, I don’t like that SurveyMonkey requires you to visit their site to see the analysis. And, then there’s the nagging SurveyMonkey footer… etc. etc. etc.