Send Unbounce leads to Juiced

Why Unbounce goes through Zapier or Make

Unbounce's page webhook can post JSON and add custom headers, but its documented JSON format puts every value inside a list, for example {"email": ["test@test.com"]} (Unbounce webhook docs). Juiced reads plain top-level values, so a connector sits in between and sends each value on its own.

Before you start

• In Unbounce: a published landing page with a form, and edit access to it. Unbounce's pricing page lists integrations on the Build plan and above, so check your plan in your account.
• In Zapier or Make: Zapier's Webhooks by Zapier app, used for the POST to Juiced, is on paid Zapier plans only (Zapier webhooks).
• 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. Add hidden fields for UTM values

   In the Unbounce builder, double-click the form and add a Hidden Field for each UTM value. Its ID must match the URL parameter exactly, including case, for example utm_source, with Default Value blank (Unbounce hidden fields). Save and republish, then submit one test lead so Zapier has a sample.

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

   In Zapier, create a Zap with Unbounce as the trigger app and New Form Submission as the event (Unbounce on Zapier). Connect your Unbounce account, choose the page, and test the trigger to load the sample lead and its field names.

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 live page 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.

Using Make instead

In Make, add Webhooks > Custom webhook as the scenario's trigger and copy its URL (Make webhooks). In Unbounce, open the Page Overview, select the Integrations tab, then the Webhooks tab, click +Add Webhook, paste the Make URL and save. Submit a test lead so Make detects the fields, then add an HTTP request that posts JSON to Juiced, as set out in our Make guide. If Make receives the values as lists, map the first item of each.

Field mapping

Zapier and Make list each Unbounce field by its field ID. Map them to the Juiced keys from View API Spec.

Any key you send must exist as a field on the Juiced lead category or source (Fields tab > New field) or it is not saved. Dropdown answers must match the values of a List of Values field exactly.

TrustedForm and Jornaya

ActiveProspect's Unbounce guide installs TrustedForm as page JavaScript: click Edit on the page, click Add New Javascript, keep the placement Before body end tag, paste the Certify snippet, then save and republish. The script adds a hidden field named xxTrustedFormCertUrl. Check the Zapier sample to confirm it is in the data sent, then map it to a Juiced field such as trusted_form_cert_url and mark it Deliverable if buyers ask for it. We found no Unbounce guide from Jornaya, so for a LeadiD follow Jornaya's instructions for custom pages and confirm the field arrives in a test lead. More in passing TrustedForm and Jornaya to Juiced.

Troubleshooting

• Leads sent straight from the Unbounce webhook fail. Unbounce wraps values in lists. Send them through Zapier or Make instead.
• Nothing arrives in Zapier. Submit a lead on the published page after the Zap is on, and check the Zap points at the right page.
• 401 Unauthorized (unauthenticated). The header value must be Bearer, one space, then the token, with no trailing space or line break. A new token expires the previous one 24 hours later.
• UTM values are empty. The hidden field ID must match the URL parameter exactly, including case, and visitors must land on a URL that carries it.
• A copied page sends no leads. Each Zap watches one page. Add the copy to a Zap of its own.

For more, see webhook troubleshooting.

Frequently asked