1. Are views from externally embedded forms tracked in the Stats section of the form in Full Fabric?
No, only views from the landing page and portal widget are counted in the form’s Stats section
2. Will a Form workflow be triggered every time if a profile submits the form multiple times?
Yes, the Form workflow will be triggered every time a profile submits the form. Each submission makes the profile enter the workflow again.
3. Can I use specific Form answers to filter profiles in a Segment?
No, the individual Form schema fields cannot be used as rules in Segments. You can only use the rules 'has submitted' or 'has not submitted'.
4. If I delete a form from the list, will its submissions also be deleted?
Yes, deleting a form will also permanently delete all of its submissions.
5. I need to enable a Form integration. Where can I find the form’s token?
The token can be found in the Integrations tab of the form. Each form has its own unique token, so to set up the integration correctly, make sure the API POST Requests include the correct token for that specific form.
6. Why am I getting a 'is invalid' error in a Form's integration?
That is caused by field validations. After receiving a form, Full Fabric checks if the data matches the expected values. If one or more fields don’t match, the submission is be rejected. Field types, field names, dropdown options, etc., must match exactly — letter for letter — between your provider and Full Fabric.
7. Do Full Fabric forms support CAPTCHA protection?
Yes. CAPTCHA is available in the Details tab of forms and events. It can be enabled or disabled individually per form and per event.
8. Does the 'Unique View' stat count multiple clicks from the same profile?
No. Only the first time someone views the form is counted. Repeated clicks by the same profile aren’t included.
9. Do the first name / last name / email fields always need to be visible and required on a form for it to be submitted?
Yes. These three fields must always be visible and required on any Full Fabric form schema (including events, applications, etc.), as they are used to identify the profile. If any of these fields aren't filled out, the form cannot be submitted.
10. I set up a Form integration, what should I check to ensure it works well?
For a Form integration (Zapier/Keystone) to run smoothly, ensure the following:
The form fields must match exactly on both ends (Full Fabric / Zapier);
Field names must be identical by the letter, capitalization and spacing;
Field types must be the same (e.g., paragraph, dropdown, checkbox, etc);
For fields with sub-options (like checkboxes or dropdowns), the sub-options must match exactly by the letter, just like the field names.
11. What happens if the fields in my Form integration don’t match exactly?
If the form sent from Zapier contains any fields that don’t exactly match those in the corresponding Full Fabric form, our system will reject the submission. An error message will be sent back to Zapier, specifying which field is invalid.