Unbounce and Instapage
Add the widget to landing pages built in Unbounce or Instapage through their custom-script areas.
Evidence tooling, not legal advice. Whether a capture satisfies a particular consent requirement is for your counsel to decide.
Set up
- Get your client id (it starts with tnt_) from Magic Setup in the dashboard at capchacloud.com/app. Your site origin must be allowlisted there, or the widget will not boot.
- Both builders let you add a custom script/HTML block to a page. Paste the snippet there so it loads on the published page.
- Use the form's real id or class from the published page (open the page, right click the form, Inspect). Builders generate these ids, so do not guess; the selector must match exactly one <form>.
- Test on the published URL, not the editor preview.
Snippets
Wrap the landing-page form (selector shown is an example, replace it)wrap
<script src="https://capchacloud.com/v1/widget.js" async></script>
<capcha-auth
data-capcha-client-id="YOUR_CLIENT_ID"
data-capcha-wrap="form.lp-pom-form"
data-capcha-company="Your Company Name"
data-capcha-privacy-url="https://example.com/privacy"
data-capcha-terms-url="https://example.com/terms"
data-capcha-campaign-id="landing-page"
data-capcha-form-id="lp-main"></capcha-auth>What is tested
Every snippet on this page is checked by an automated test that loads the page, takes the snippet out of it, and runs the real /widget.js in a browser DOM: the attributes must be exactly the ones the widget reads, the form selector must match exactly one form, and a test submission must produce a capture request carrying your campaign and form ids.
What is not verified
- Not run inside Unbounce or Instapage (paid accounts). The fixture is representative markup, not a recording of either builder's output; their generated selectors differ per page, which is why the page tells you to inspect and copy your own.
This is not a marketplace app, partner listing or certified integration of Unbounce / Instapage. It is a snippet for your own pages.