Put a Form Inside an Artefact
Capture in context, without writing any markup
Artefacts are the interactive experiences you build to share with clients — calculators, assessments, guides, dashboards — generated and styled to your brand.
An artefact that gets somebody interested and then leaves them with nowhere to go is a wasted opportunity. Placing a form inside it means they can act in the moment, in context, while whatever the artefact just showed them is still in front of them.
The practical advantage over embedding by hand is that the code is generated for you.
Before You Begin
- A Published form — Draft forms are not offered as options
- An artefact you are building or editing
Steps
Publish the form first
Only Published forms appear in the picker. If yours is still Draft, open Manage Form Actions and save it — saving that screen is what publishes a form.
This catches people out, because a Draft form works perfectly at its own address and gives no hint that it is invisible here.
Decide where in the artefact the form belongs
Put it after whatever earns the request, not before.
If the artefact is a calculator, the form belongs after the person has seen their result. If it is an assessment, after their outcome. Asking before you have given them anything converts far worse than asking after.
Insert the form
While building the artefact, insert the form where you want it. Your published forms are offered by name, so you choose rather than paste an address.
Zyntro generates the embed code for you, pointing at the form's public address.
Match the form's styling to the artefact
The form carries its own styling, which was set up independently. Dropped into an artefact it can look like a different product.
Open Manage Styles on the form and bring its colours, input shapes and heading sizes into line. It is worth the few minutes — a form that looks foreign reads as untrustworthy, which is the one thing you cannot afford at the point of asking.
Check the height
An embedded form sits in a frame of fixed height. Too short and the form scrolls inside its own frame, which is uncomfortable and easy to miss on a phone.
If the form is long, consider a shorter version for this placement. Capture the essentials in the artefact and ask the rest later.
Test the whole piece end to end
Work through the artefact as a client would, complete the form, and confirm the submission arrives with everything you expected — including any hidden field identifying this artefact as the source.
Check it on a phone as well as a desktop. Embedded forms are where narrow screens cause the most trouble.
Tip: Add a hidden field with a static value naming the artefact, mapped to a custom field. Then you can tell which artefact produced which submissions — worth knowing before you invest in building more of them.
Info: The form inside an artefact is the same form as everywhere else. Its submissions appear in the same completions list, its actions run identically, and its lead allocation is unchanged. There is no separate copy to maintain.
Result
Your artefact now captures interest at the point it is created, and the submissions join everything else that form collects.
If the form is missing from the picker, check it is Published. That is the explanation nearly every time.
