How to embed a Google Form inside a Continu Article — for in-context surveys, feedback collection, and quick polls without sending learners to an external link.
Embedding a Google Form keeps learners in flow while they complete it. They see the form in the Article context, fill it out, submit, and continue. Compare with linking out to the Form, which interrupts the learning flow and increases drop-off.
Reach for an embedded Google Form when you need form fields beyond what Continu Surveys offers, when the Form's data needs to land in a Google Sheet for a downstream workflow, or when the Form is already established and you just want to surface it in Continu.
For native survey content inside Continu, use a Survey content type instead — see the Surveys section. For other embed scenarios, see Embedded Content.
How to Embed a Google Form
1. Create or open an Article in Continu. Embedding happens in the Article editor, so start with an Article that will host the Form.
2. Click the Code View icon. Code View toggles the editor to raw HTML, which is needed to paste the Form's embed code.
3. Open the Google Form you want to embed and click Send. The Send dialog is where Google exposes the embed option.
4. Click the Embed HTML icon. Look for the <> icon in the Send dialog.
5. Click Copy to copy the embed code.
6. Paste the embed code into the Article's Code View. Place it where you want the Form to appear.
7. Click the Code View icon again to return to visual editing. The Form should now render in the Article.
Considerations
Verify Form sharing permissions before publishing the Article. If the Form is set to "anyone with the link" it works for all learners. If it's set to "people in your org," learners without that org's Google login can't see the Form. Test as a learner before publishing.
Frame the Form in the Article above it. A bare embedded Form looks abandoned. Add a paragraph explaining what the Form collects, why, and what learners can expect afterward.
Adjust the embed size if needed. Google's default embed dimensions may not fit Continu's Article width well. Edit the width and height in the embed code (visible in Code View) for a cleaner fit.
Configuration Pitfalls
Form Sharing Set to Restricted Domain. The most common embed issue. Learners outside the Form's permitted domain see a sign-in prompt instead of the Form. Test from a learner account before publishing.
Using Embedded Forms Instead of Native Surveys. If the form fits Continu's Survey content type, build it as a Survey instead. Native Surveys integrate with Continu's reporting; embedded Forms send data to Google only. Use embedded Forms only when Google's specific functionality matters.
Pasting Embed Code Outside Code View. Pasting the embed in regular Article view renders the code as visible text rather than as a Form. Always switch to Code View first.
Forgetting to Test the Submission. A learner submitting an embedded Form generates an entry in the Google Sheet behind the Form. Submit a test entry yourself before publishing to confirm the data lands where you expect.
Form Stops Rendering After Source Changes. Google occasionally updates its embed format. If the Form stops rendering, re-copy the embed code from Google's Send dialog.
Where This Fits
You're here because you're embedding a Google Form. For native survey functionality inside Continu, see the Surveys content type. For embedding other external content, see Embedded Content.
See Also
- Add an Article to Continu — the Article creation flow.
- Continu Articles: Using the Advanced Editor Tools — beyond-basics editor capabilities.
- Embedded Content — embedding external content as a standalone content piece.
Code View, paste embed, exit Code View. Test as a learner. For Continu-native surveys, use the Survey content type instead.