Guide overview
Summary:
This guide details how to capture leads from HeyFlow by integrating TrustedForm Certify into your form to automatically document user consent and session details via a unique certificate URL. HeyFlow has a built-in integration with TrustedForm. However, in order to use TrustedForm, you need to subscribe to HeyFlow’s Business plan.
Learning objectives:
- Integrate TrustedForm Certify into your HeyFlow lead capture form.
- Customize and configure the TrustedForm script to match your form settings.
- Validate and troubleshoot that each lead submission correctly includes a TrustedForm Certificate URL.
Quick start workflow
- Sign up / Log in and configure basic settings
- Embed the TrustedForm integration into your HeyFlow form
- Publish and test your form
Step‑by‑step instructions
Step 1. Configure your HeyFlow form
Instructions:
- Log in to your HeyFlow Business account and open the form editor.
- Select the lead capture form you wish to integrate with TrustedForm Certify or create a new form.
- Once you have created your form in ‘Build’ mode, click on the ‘Integrate’ tab:
- Then click on ‘Analytics’ tab, scroll down and click on ‘TrustedForm’:
- The TrustedForm option expands as can be seen below. Here, fill in the Certificate URL System Label, Session Identifier (optional), and Ping URL System Label using the information in the Certify section of your TrustedForm account. You can also enable Sandbox using the toggle option.
- Save your changes.
Expected result:
When the form loads, the TrustedForm Certify script runs and automatically adds a hidden field containing a unique certificate URL that records the user’s session details and consent.
Step 2. Publish and validate the integration
- Goal: Verify that your HeyFlow form is successfully capturing leads along with a valid TrustedForm Certificate URL.
- Context: Testing the live form confirms that the TrustedForm Certify script runs correctly and that each form submission includes the hidden certificate URL for compliance documentation.
Instructions:
- Publish your updated HeyFlow form.
- Open the published form in a web browser and complete a test submission using sample data.
- Use the browser’s Developer Tools (e.g., the Network tab) to inspect the form submission payload and confirm the hidden field contains a URL starting with
https://cert.trustedform.com/. - Optionally, click the certificate URL to view the TrustedForm Certificate page displaying session metadata and consent details.
Expected result:
Test submissions will include a populated TrustedForm certificate URL in the designated hidden field, confirming that the integration is correctly implemented.
Validate your setup
To ensure full integration functionality:
- Verify that every lead submitted through the form includes the TrustedForm Certificate URL by reviewing your CRM or backend data.
- Log in to your TrustedForm account to retain and review certificate metadata and session replay. Verify that all required consent and session details were captured accurately and that the certificate matches the corresponding lead submission.
Troubleshooting
| Symptom / Error message | Likely cause | Resolution |
|---|---|---|
| Certificate URL appears blank | Script execution error or network connectivity issues | Check the browser console for JavaScript errors, ensure a stable internet connection, and disable any ad blockers. |
Glossary
| Term | Definition |
|---|---|
| TrustedForm Certify | A TrustedForm product offering that embeds a JavaScript snippet into a web form to generate a unique certificate URL documenting the user’s session and consent. |
| HeyFlow | An interactive drag-and-drop form builder that allows users to create and customize lead capture forms with embedded scripts. |
| Hidden field | An invisible HTML form element used to store additional data (such as the TrustedForm certificate URL) that is submitted with the form. |
| Certificate URL | A unique URL generated by TrustedForm Certify that points to a certificate containing detailed records of the user’s visit, including consent and session data. |
- heyflow1.png200 KB
- heyflow2.png800 KB
- heyflow4.png300 KB
- heyflow3.png400 KB
Comments
0 comments
Please sign in to leave a comment.