Send Instapage leads to Juiced

Before you start

• In Instapage: a published page with a form, and access to the workspace's integration settings. Instapage's help does not list a plan for webhooks, only that the Ad Campaign and Average Cost per Visitor session fields are for Convert accounts, so check in your account.
• In Juiced: a source for these leads, a bearer token from its Authentication tab, and the exact field names from View API Spec. Turn on Test mode on the source while you set up.

Step by step

1. Create a Juiced source and copy a bearer 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 > Create 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. Connect the Juiced endpoint in the workspace

   Webhook endpoints are added once per workspace. From the main Integrations dashboard, select the workspace, go to Settings > Integrations and add a Webhook endpoint with the URL https://usejuiced.com/api/v1/leads (Instapage webhook docs).

3. Add the webhook to the page with your token

   From the Landing Pages list, click the page name and go to Integrations > Form Integrations. Select the Juiced endpoint and enter your token in the token authorization (bearer authentication) field. Instapage sends it in the Authorization header. Its docs do not say whether you type the word Bearer, so check the field's hint in your account.

4. Choose the JSON sending method

   Select the sending method and click Continue. Instapage's help does not list the options; pick the JSON one (a third-party guide shows it as Send by POST + JSON). If no JSON option appears, stop here and use the Zapier route below.

5. Type each Juiced key into Webhook Fields

   In Webhook Fields, next to each Instapage form field, type the Juiced key exactly: first_name, last_name, email, phone, zip. On the session step, leave a field's Webhook Fields entry blank to exclude it, or type a key you created in Juiced, such as page_url.

6. Finish and click Update

   Click Finish, then CLOSE. Back on the page slide-out, click Update so the change goes live. Do this again any time you add, change or remove the webhook.

7. Send a test lead from the live page

   Open the live URL (not preview), clear your cache and submit with zip 00001 and a real, unused email (Instapage may flag repeated emails as spam). In Juiced, open Entries > Incoming logs, filter Test mode to Test only, open the log and click Post to see the payload, any Validation errors and the response. Turn test mode off before going live.

Field mapping

Whatever you type in Webhook Fields becomes the key Juiced receives. Every Instapage form field needs a label, but the label does not need to match Juiced.

Add hidden fields by selecting the form, clicking add field and choosing hidden. Instapage's help does not document how a hidden field picks up a URL parameter, so check a test lead. Any extra key must exist as a field on the Juiced lead category or source (Fields tab > New field) or it is not saved.

Zapier route. If your account cannot send JSON or the bearer token is rejected, use the Instapage trigger Form Submission in Zapier (it asks for the Page), map each form field to its Juiced key and finish with the shared POST step in Zapier to Juiced. Make works the same way.

Example request

With the JSON method and your Webhook Fields entries, Juiced should receive one flat object per submission:

POST https://usejuiced.com/api/v1/leads
Authorization: Bearer YOUR_TOKEN
Content-Type: application/json

{
  "first_name": "Jane",
  "last_name": "Doe",
  "email": "jane@example.com",
  "phone": "5555550123",
  "zip": "00001",
  "trusted_form_cert_url": "https://cert.trustedform.com/..."
}

Instapage also adds base parameters such as page_id and variant; they show in the log but are not saved unless you create matching fields. A 201 response with data.status accepted means the lead was accepted (leads endpoint reference).

TrustedForm and Jornaya

Jornaya's Instapage guide adds a hidden form field (for example leadid_token, value empty), pastes a callback script and the campaign script into the page's JavaScript section under the footer tab, and then names that field in the webhook. For TrustedForm, paste the Certify snippet into the same footer JavaScript and set the snippet's field parameter to your hidden field's name, as described in ActiveProspect's Web SDK article. Map each field in Webhook Fields to a key you created in Juiced, and mark it Deliverable if buyers ask for it. More in passing TrustedForm and Jornaya to Juiced.

Troubleshooting

• Nothing arrives. Click Update on the page after any webhook change, test on the live URL rather than preview, and clear your cache.
• 401 Unauthorized (unauthenticated). Check whether the token field expects the full Bearer value or the token alone, and remove any trailing space or line break. A new Juiced token expires the previous one 24 hours later.
• 422 with a zip error. The Webhook Fields entry for the zip field is not exactly zip. Open the log's Post view to see the keys as received. Juiced returns error.code validation_failed with errors keyed by field.
• Body arrives as form data. Juiced reads JSON only. Change the sending method to JSON, or use Zapier.
• Thank-you page or redirect fails. Instapage waits up to 20 seconds for the endpoint. Check Incoming logs for errors on the matching submission.

For more, see webhook troubleshooting.

Frequently asked