Send Leadpages leads to Juiced

Why Leadpages goes through Zapier or Make

Leadpages can post each form submission as JSON, and you choose which fields and page details to include (Leadpages webhooks). Its webhook settings offer a destination URL, events, pages, an optional Secret Key and a description; the docs mention no custom headers (connecting integrations in New Leadpages). Juiced needs an Authorization header and its own top-level keys, so a connector sits in between.

Before you start

• Leadpages: a published page with a form. Webhooks are available on every plan. For the Zapier trigger, the form needs at least one integration or Lead Notifications, and one test opt-in with every field filled (Leadpages and Zapier).
• Zapier or Make: Zapier's Webhooks by Zapier app, used for the POST to Juiced and for catch hooks, is on paid Zapier plans only (Zapier webhooks).
• Juiced: a source, its bearer token, and the field names from the source's View API Spec page.

Step by step

1. Create a Juiced source and token

   In Juiced, go to Ingest > Sources > New source, turn on Test mode, and click Create source. On the Authentication tab click New bearer token and copy it (it is shown once). Open Overview > More actions (⋯) > View API Spec for the endpoint and field names. See setting up a source.

2. Add hidden fields for UTMs

   Open the form's Edit Integrations and set up the fields in Lead Notifications. Under FIELDS, select a field, check This is a hidden field, enter a default value, set a URL variable such as utm_source, and click Done. A link ending in ?utm_source=facebook then fills the field (Leadpages hidden fields).

3. Start a Zap with the Leadpages New Form Submission trigger

   Submit a test opt-in on the published page. Then click the form, select Edit Integrations, Add an Integration, More Services, and Use this Zap, or start in Zapier with Leadpages and the New Form Submission trigger. Connect your Leadpages account, confirm the form, choose the sample submission and click Test & Continue. Each form needs its own Zap.

4. Add a JSON POST to Juiced

   Add a Webhooks by Zapier action with the POST event. Set the URL to https://usejuiced.com/api/v1/leads, send the data as JSON, and add the Authorization, Content-Type and Accept headers. Map each form field to its Juiced key using the table below. The exact settings are in our Zapier guide.

5. Send a test lead and check Incoming logs

   Submit the form with zip 00001 and test the Zapier step. In Juiced, open Entries > Incoming logs, set the Test mode filter to Test only, open the log and click Post to see the request, any Validation errors and the response. When it shows Accepted, turn test mode off on the source and turn the Zap on.

New Leadpages: use an account webhook

Create the receiving URL first: a Webhooks > Custom webhook trigger in Make (Make webhooks) or a Webhooks by Zapier Catch Hook trigger in Zapier. In Leadpages, click your account name, go to Account Settings, select Webhooks under Organization, and click Add Webhook. Paste the URL, choose the form submission event and the pages it applies to, and save. Leadpages' help article does not list the exact event names, so check them in your account. Submit a test, then add the JSON POST to Juiced, as set out in our Make guide or Zapier guide.

Field mapping

Zapier and Make list each form field by name. Map them to the Juiced keys from View API Spec.

TrustedForm and Jornaya

Leadpages' help center does not describe TrustedForm or Jornaya support. TrustedForm's docs say its script must run in the page that holds the form and the page builder must allow custom JavaScript (TrustedForm iframe forms). Check with Leadpages and ActiveProspect before relying on certificates from a Leadpages form. If you capture one in a hidden field, map it to a trusted_form_cert_url field in Juiced, as covered in passing TrustedForm and Jornaya to Juiced.

Troubleshooting

• Hidden fields do not show in Zapier. They must be tied to Lead Notifications. Hidden fields set up in an email provider, or from other integrations, are not passed.
• A duplicated page sends nothing. Zaps do not carry over when you duplicate a page. Build a Zap for each form.
• You need to remove a Zap. It cannot be deleted from the form directly. Duplicate the form widget and delete the original.
• The consent checkbox is missing. Zapier cannot pass the built-in Leadpages active-consent field. It can pass consent fields from other integrations you add.
• 401 Unauthorized. The token was replaced (old tokens expire 24 hours after a new one is created) or the header has a stray space or line break.
• 422 or status rejected. A 422 has error.code validation_failed and errors names the field: a key does not match a Juiced field title or a value is not allowed. A 201 with data.status rejected means received but not sold. Open the log in Incoming logs. More fixes in webhook troubleshooting.

Frequently asked