How the connection works
Aesthera sends a JSON POST to your receiving endpoint. Your system accepts the request and creates or routes the lead. We agree on the destination and field mapping with your CRM administrator before enabling delivery.
What your developer provides
- A public HTTPS endpoint on port 443 that accepts JSON without redirecting.
- The authentication method: bearer token or a named header, when required. Share credentials through an agreed secure channel.
- The expected JSON field names, required fields, and any fixed values for routing or ownership.
- Rules for missing values and duplicate requests. Aesthera can include the session ID for your endpoint’s duplicate-handling logic.
Example custom payload
This is an illustrative custom mapping, not the default webhook schema. Aesthera can map fields to the names your endpoint expects, including nested objects. The standard payload does not include all the attribution fields shown here; request a custom mapping if you need source, medium, or gclid.
{
"session_id": "11111111-2222-4333-8444-555555555555",
"name": "Example Visitor",
"email": "visitor@example.com",
"phone": null,
"utm_source": "google",
"utm_medium": "cpc",
"utm_campaign": "co2-resurfacing",
"gclid": null
}Agree on missing fields
Contact fields reflect what the visitor provided. Campaign tags are available only when captured. A gclid requires the website’s consent signal and enabled capture. Your endpoint should accept the agreed empty values or tell us which fields are mandatory before setup.
CRM-specific requirements
If your CRM requires a different authentication flow or request format, your developer may need an adapter that accepts Aesthera’s JSON and calls the CRM’s API. This also applies to self-hosted systems. Confirm that the endpoint creates the intended lead record, including assignment and custom fields.
Connection check
We preview the configured payload with your integration team and arrange a marked test delivery. Your team confirms the resulting CRM record and fields, then we check a submission through the widget. Agree on duplicate handling and failure recovery before enabling the connection. An HTTP success response confirms acceptance by the endpoint; the CRM record confirms the intended result.