Why can a multi-page OptiMonk campaign create multiple webhook logs?

OptiMonk documents logs corresponding to campaign pages, with later-page fields appearing in later logs. Inspect the complete sequence instead of assuming each request contains the final, complete submission.

Send OptiMonk leads to a webhook URL

OptiMonk’s webhook sends campaign form data by POST to a URL you configure. Use it when your receiving system needs a custom connection, and verify both request arrival and downstream processing before calling the integration complete.

This guide follows OptiMonk’s webhook documentation, checked September 6, 2026. The receiver checklist is editorial guidance, not a tested implementation contract for every endpoint.

Prepare the receiving endpoint

Identify who owns the endpoint and where test requests can be inspected. Agree which fields the receiving system needs and how it will turn the request into a usable contact. Use synthetic test data while inspecting a temporary request collector; do not route real customer submissions to a public sample endpoint.

The vendor guide explains basic sending and field mapping. It does not establish a complete contract for authentication, retries, signatures, timeout handling or duplicate prevention. Confirm those requirements for your implementation before relying on unattended processing.

Add the campaign integration

Open Campaigns, select the intended campaign and choose Edit settings.
Under the subscriber and campaign-data destination section, select Add new integration → Webhook.
Name the integration and enter your receiving URL.
Map each required campaign field to the expected receiving field.
Save with Done, then Next, as shown in the source workflow.

Test the same campaign you configured. If several campaigns are active, record the campaign name and ID so a request from another form does not look like proof that this one works.

Map fields against an observed request

Data	Documented identifier or constraint	Verification
Email	`email`	Matches the test address
Name	`firstname`, `lastname`	Reaches the intended fields
Phone	`phone`	Preserves the submitted value needed by your receiver
Page	`url`	Identifies the test page
Campaign	Campaign name and ID	Identifies the correct campaign
Coupon	Documented for Lumira/Vegas templates	Verify availability in the actual campaign
Other inputs	Mapping covers supported form inputs	Compare each required value individually

Inspect the actual request body and headers rather than assuming JSON encoding or inventing a payload shape from field names. A receiver accepting the request does not establish that it parsed every value correctly.

Account for multi-page campaigns

OptiMonk documents multiple logs corresponding to campaign pages, with later-page data such as a coupon appearing later. Its guide also warns that delayed sending is unsupported: separating email and phone inputs across signup pages can produce an admin integration error even when data arrives. It recommends collecting them on the same page for this case.

Plan around the observed sequence. Do not treat every request as a complete new lead or assume that the last request contains everything from earlier steps without checking.

Verify the full path

Stage	Evidence to capture
Submission	Controlled test value, page and campaign
Request arrival	Receiver log and time
Parsing	Required values extracted correctly
Storage	Intended contact or record created
Further action	Expected automation executes once as intended
Error handling	A controlled failure is observable and recoverable through your defined process

Use one traceable test through all stages. If no request arrives, investigate the campaign, saved URL and receiver availability. If the request arrives but no record appears, inspect parsing and processing before changing the campaign.

For a direct email-service connection, see OptiMonk with Klaviyo or OptiMonk with Keap.

How to Integrate OptiMonk with Webhook