OptiMonk

OptiMonk is a webhook platform: rather than reading your data directly, you paste Instasent's webhook URL into an OptiMonk campaign so the leads you capture through popups and forms flow into Instasent's ingest stream. Use it to add contacts to your audience as OptiMonk captures them.

How to connect

OptiMonk is a webhook platform: you don't create a credential — Instasent gives you a webhook URL, and you paste it into OptiMonk. This is a manual webhook: OptiMonk posts to that URL every time a lead is captured. You can create the Instasent source before setting anything up in OptiMonk; the source waits for data in real time.

1. 1

   Add the data source

   In Data sources, select Add data source and choose OptiMonk from the Integrations section.

2. 2

   Configure the source

   Fill in the Configure step — Connection name, Default country, Regional settings / Locale and Timezone — and Instasent creates the source.

3. 3

   Copy the webhook URL

   Instasent shows the source's Webhook URL under Setup instructions. Copy it.

4. 4

   Paste it into OptiMonk

   In your OptiMonk campaign, add a webhook integration and paste the Instasent webhook URL. From now on OptiMonk posts each captured lead to Instasent.

5. 5

   Watch the stream log

   Back in Instasent, the source shows a stream log of the data arriving, so you can confirm the connection is working.

For the endpoint shapes and the full setup, see API & webhooks.

What it syncs

OptiMonk sends the contacts it captures — the leads from your popups and forms — in real time as each one comes in. The payload identifies the contact (contact_id) and carries the fields the OptiMonk campaign collected.

Field mapping

The fields OptiMonk sends are mapped to Instasent attributes the same way as any source — you confirm which incoming values go into which Instasent attributes. See field mapping.

Consent mapping

OptiMonk passes through the fields the campaign collects; it has no consent mapping of its own. Consent is controlled by the fields you map — if a campaign collects an explicit marketing opt-in and you map it to a consent attribute, that value applies. The same rules apply as for any import: only set _accepts_marketing_* to false on an active opt-out; "no data" stays null. See Consent.