POWR Form Builder for Shopify

Sync POWR Form Builder to Google Sheets

POWR Form Builder brings drag-and-drop forms, file uploads, conditional logic, and PayPal integration to Shopify. Add LeadToSheet to stream every submission into Google Sheets for reporting and automation.

CMS: Shopify

POWR Form Builder is a cross-platform app popular on Shopify for its drag-and-drop editor, auto-responders, and PayPal payment fields. While POWR offers its own Google Sheets connector on higher plans, LeadToSheet captures submissions at the browser level with zero plan restrictions, adding UTM attribution and device context that POWR does not include natively.

Implementation checklist

  1. 1

    Install the LeadToSheet SDK in theme.liquid

    Navigate to Online Store > Themes > Edit code. Open theme.liquid and paste the script tag before </body>. This ensures the SDK is present on every page where POWR forms appear, including product pages and landing pages.

    theme.liquid snippet

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

    Embed POWR forms using the app block or embed code

    Add POWR forms via the Shopify theme customizer app block or paste the POWR embed code into a custom Liquid section. Both methods render forms inside the storefront DOM where the LeadToSheet SDK can detect them.

    Tip: If you use the POWR embed code inside a custom HTML block, make sure the script runs after the page loads to allow POWR to render the form first.

  3. 3

    Test file uploads and conditional fields

    Submit a test entry that triggers conditional logic branches and includes a file upload. Verify that the Google Sheet captures all visible field values, conditional answers, and a URL reference for the uploaded file.

Customization ideas

  • Track PayPal payment form submissions

    When using POWR's PayPal integration for order forms or deposits, LeadToSheet records the form payload alongside the page URL so you can reconcile payment submissions in Google Sheets against your PayPal transaction log.

  • Segment by auto-responder status

    Add a hidden field that flags whether the POWR auto-responder is enabled for that form. In Google Sheets, filter by this column to identify leads that received an immediate follow-up versus those requiring manual outreach.

  • Route multi-purpose forms to separate tabs

    If you reuse one POWR form across contact, feedback, and wholesale inquiry pages, add data-leadtosheet-tab to each page's form wrapper so submissions land in the correct Google Sheet tab based on context.

Troubleshooting

  • POWR form renders inside an iframe

    Some POWR embed methods render the form in an iframe hosted on powr.io. If submissions are not captured, switch to the Shopify app block embed method, which injects the form directly into your storefront DOM where the SDK can detect it.

  • Conditional logic fields missing from the sheet

    Fields hidden by POWR's conditional logic are not included in the submission payload. Submit a test entry that triggers every branch so all possible column headers are created in the sheet during initial setup.

  • Auto-responder conflicts with LeadToSheet

    POWR's auto-responder and LeadToSheet operate independently. If you see submission timing differences, it is because POWR sends the auto-reply server-side while LeadToSheet captures the browser event. Both work without conflict.

Frequently asked questions

POWR already has a Google Sheets integration. Why use LeadToSheet?
POWR's native Sheets connector requires a paid plan and does not capture UTM parameters, referrer data, or device context. LeadToSheet works on any POWR plan and includes full attribution metadata.
Will POWR's file uploads appear in Google Sheets?
LeadToSheet captures the file URL reference generated by POWR. The actual file remains hosted on POWR's servers, but you get a clickable link in your spreadsheet for quick access.
Can I use LeadToSheet alongside POWR's Zapier integration?
Yes. LeadToSheet writes to Google Sheets independently of any Zapier workflows you have connected to POWR. There is no overlap or conflict between the two data paths.