OptiPub can send webhook postbacks to external URLs when funnel events fire. This lets you notify third-party systems — such as CRMs, analytics platforms, or custom backends — in real time when subscribers take actions like signing up, opening an email, or clicking a link.

Webhooks are sent using the Make Post Request to Url funnel action. It can send either a GET or a POST request, and you can either send OptiPub's default JSON payload (subscription, subscriber, and event data) or supply your own custom request body. URLs and request bodies support macros so you can inject subscriber-specific values like email address or ESP variables.

Setting Up a Funnel Webhook

Step 1. Create or edit a funnel.

Open an existing funnel or create a new one in Marketing > Funnels.

Step 2. Add a trigger event.

Choose the funnel event that should trigger the webhook (e.g., New Subscription, Email Opened, Email Clicked). Click the + button on the event grid to add one.

Step 3. Add the "Make Post Request to Url" action.

Click the + button under your trigger event and select Make Post Request to Url from the action list.

Step 4. Configure the request.

GET requests send no body. When Method is set to GET, the body encoding and custom body fields are hidden. To pass data on a GET request, include it as query-string parameters in the URL using macros (see below).

Google Ads Data Manager must be connected under Admin → Settings → Integrations (and the Data Manager API enabled on the Google Cloud OAuth project) before a Google Enhanced Conversions action can send. Connect with a Google account that can access the Ads account. The conversion action must be type UPLOAD_CLICKS (shown in Google Ads as Website — Import from clicks). This uses Google's Data Manager API, not the legacy Ads API UploadClickConversions endpoint.

Step 5. Set the timing.

Choose when the webhook should fire after the trigger event:

Step 6. Save.

Click OK to add the action, then Save the funnel.

Webhook Payload

When a POST request fires without a custom body, OptiPub sends this default JSON payload to the configured URL. It includes the full subscription, subscriber (with emails and ESP variables), and event context. To send your own body instead, see Customizing the request body.

{
    "id": 715462777,
    "active": true,
    "email_id": 10048162,
    "publication_id": 7,
    "subscriber_id": 57343261,
    "started_at": "2024-10-17 16:11:50",
    "ended_at": null,
    "deleted_at": null,
    "created_at": "2024-10-17T16:11:50.000000Z",
    "updated_at": "2024-10-17T16:11:50.000000Z",
    "publication": {
        "id": 7,
        "name": "OptiPub Daily",
        "active": true,
        "code": "opd"
    },
    "subscriber": {
        "id": 57343261,
        "created_at": "2024-10-17T16:11:50.000000Z",
        "updated_at": "2024-10-17T16:11:50.000000Z",
        "emails": [
            {
                "id": 10048162,
                "email": "[email protected]",
                "md5": "01f6ea24e7137bd99a7b73436fd7ef30",
                "variables": [
                    { "id": 1002021, "name": "phone", "value": "5554445949" },
                    { "id": 1002703, "name": "first_name", "value": "John" },
                    { "id": 1002707, "name": "last_name", "value": "Doe" }
                ]
            }
        ]
    },
    "email": {
        "id": 10048162,
        "email": "[email protected]",
        "md5": "01f6ea24e7137bd99a7b73436fd7ef30"
    },
    "event": {
        "event": "NewSubscription",
        "data": {
            "ip": "17.30.57.47",
            "user_agent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36",
            "referring_url": "https://example.com/landing-page",
            "effort_id": "809502",
            "variables": [
                { "name": "first_name", "value": "John" },
                { "name": "last_name", "value": "Doe" },
                { "name": "phone", "value": "5554445949" }
            ]
        }
    },
    "subscription": {
        "id": 715462777,
        "active": true,
        "email_id": 10048162,
        "publication_id": 7,
        "subscriber_id": 57343261,
        "started_at": "2024-10-17 16:11:50"
    }
}

The payload above is condensed for readability. The actual payload includes additional fields on the subscription, subscriber, and nested objects.

Macros

Both the URL and a custom request body support macros — placeholders that OptiPub replaces with subscriber-specific values when the request fires. Macros use the format {$name} and are case-insensitive.

Where macros work:

• In the URL — values are automatically URL-encoded, so macros are safe to use in query-string parameters (e.g. https://example.com/hook?email={$email}). This is the primary way to pass data on GET requests.
• In a custom body — macros are substituted inside string values (not keys). Values are inserted as-is (not URL-encoded).

Click IDs ({$gclid}, {$fbclid}, {$fbc}) are taken from the referring_url query string. Many OptiPub paths set referring_url from the HTTP Referer header, which browsers often strip of click IDs. Landing pages that post the full landing URL (query string included) will populate them; Referer-only flows often will not.

Customizing the Request Body

For POST requests, you can replace the default payload with your own body by filling in the Custom body field. Leave it blank to send the default payload.

Enter a valid JSON object. If the body is empty or is not valid JSON, OptiPub falls back to the default payload.

The Body encoding setting controls how the body is sent:

Example — custom JSON body with macros:

{
    "email": "{$email}",
    "first_name": "{$esp_first_name}",
    "source": "optipub",
    "effort": "{$effort_id}"
}

Custom headers and HTTP methods other than GET/POST are not currently supported on generic Post to URL actions. Google Enhanced Conversions is the exception: OptiPub attaches a refreshed OAuth Authorization header (and x-goog-user-project) when the URL is the Data Manager ingest endpoint.

Common Use Cases