Tripetto form guide

Capture Tripetto conversational forms in Sheets

Tripetto's visual storyboard creates branching conversational forms that run locally in WordPress. LeadToSheet captures every response path and syncs final submissions to Google Sheets.

CMS: WordPress

Tripetto stands apart by running entirely within WordPress rather than loading from a SaaS platform. Its three form faces (autoscroll, chat, and classic) and visual storyboard editor create complex branching experiences. LeadToSheet captures the completed submission from any form face, preserving the full response path in your Google Sheet.

Implementation checklist

  1. 1

    Add the SDK script to your WordPress footer

    Since Tripetto forms render natively in WordPress (no iframe), the snippet picks up submission events directly from the DOM.

    LeadToSheet snippet

    <script src="https://cdn.leadtosheet.com/sdk.min.js" data-client="YOUR_CLIENT_KEY"></script>
  2. 2

    Test each form face you use

    Submit test entries using autoscroll, chat, and classic modes. Each face fires the same completion event, but field ordering may differ slightly in the Sheet.

    Tip: The chat form face submits on the final message, not on each individual response bubble.

  3. 3

    Walk through every logic branch

    Tripetto's storyboard branches produce different field sets per path. Submit one test entry per major branch to pre-create all column headers in your Sheet.

Customization ideas

  • Map storyboard branches to Sheet tabs

    Use Tripetto's calculated values or hidden fields to tag which branch a respondent followed. Set up LeadToSheet routing rules based on that tag to direct entries to different tabs.

  • Leverage local data processing

    Because Tripetto runs locally in WordPress, submissions never leave your server until LeadToSheet syncs to Sheets. This is ideal for GDPR-conscious teams who want a Google Sheets archive without SaaS form hosting.

  • Build completion-rate reports

    Pair LeadToSheet's submission data with Tripetto's built-in analytics to compare drop-off points against actual Sheet entries and identify friction in your form flow.

Troubleshooting

  • Autoscroll form not triggering capture

    Ensure the LeadToSheet script loads before the Tripetto form initializes. Place it higher in the footer or use a script loading priority plugin.

  • Branch-specific fields missing columns

    Fields that only appear in certain branches will not have Sheet columns until a submission travels that branch. Submit a test entry for each major path during setup.

  • Chat form face submits partial data

    The chat face collects responses incrementally but only fires the submission event at the end. If users abandon mid-conversation, no partial data is sent. This is expected Tripetto behavior.

Frequently asked questions

Does LeadToSheet work with all three Tripetto form faces?
Yes. Autoscroll, chat, and classic all fire the same submission event when complete. LeadToSheet captures identically regardless of face.
Is data sent to an external server before Google Sheets?
Tripetto processes everything locally in WordPress. LeadToSheet sends only the final submission payload to Google Sheets via its secure sync endpoint.
Can I capture Tripetto's calculated values?
Calculated values and hidden fields from the storyboard editor are included in the submission payload and appear as regular columns in your Sheet.