Custom Webhook AI Visibility Integration

Finseo offers a native Custom Webhook integration: a universal JSON endpoint per project that accepts attribution data from any tool that can POST. Finseo attributes each event to ChatGPT, Perplexity, Claude, Gemini, or Microsoft Copilot and reports it beside tracked prompts. Use it when no native Answer Engine Optimization (AEO) integration exists for your source.

POST a JSON payload such as { "channelId": "ai_chatgpt", "respondentEmail": "...", "dealValue": 1000 } to your Finseo custom webhook URL with the header Content-Type: application/json. Supported channel IDs include ai_chatgpt, ai_perplexity, ai_claude, ai_gemini, and ai_copilot. Finseo records the event under ChatGPT or the matching engine and shows it in the Attribution dashboard within 10 seconds.

Yes. Finseo is a Generative Engine Optimization (GEO) platform whose custom webhook ingests attribution from homegrown CRMs, internal apps, backend triggers, or scripts. It differs from a generic webhook relay: Finseo parses known formats, categorizes each event as ChatGPT, Perplexity, or Claude, and links revenue back to the AI prompts and citations it tracks.

Click Connect on the Custom Webhook card in Finseo to reveal your project specific URL. From your app, script, or tool, POST JSON to that URL with the header Content-Type: application/json. Either include an explicit channelId or send any JSON with an attribution field for auto detection. No API key is needed; a test payload appears within 10 seconds.

The webhook accepts channelId plus optional respondentEmail, respondentName, dealValue, dealCurrency, formId, pageUrl, and metadata, or raw payloads from HubSpot, Salesforce, Typeform, Jotform, Pipedrive, Attio, Calendly, and Intercom. Data flows one way into Finseo. For security, configure an HMAC SHA256 key; Finseo verifies the X-Finseo-Signature header and rejects tampered requests with HTTP 401.

Yes. The custom webhook is included in every Finseo plan with no per-integration fee and no third party tool required, since anything that can POST JSON can use it. Rate limits are 100 requests per second per project with burst capacity to 500 per second, which covers most teams; contact Finseo for higher volumes.

Yes. Teams migrating from spreadsheets, databases, or legacy systems can POST historical events to the Finseo custom webhook from a script, adding a custom timestamp field in ISO 8601 format. Finseo accepts events up to 90 days old by default; for older backfills, contact Finseo. Backend triggers such as a Stripe charge succeeded event work the same way.

A webhook only moves data; it cannot tell whether a lead came from ChatGPT, Perplexity, or Google, and it knows nothing about which AI answers mention your brand. Finseo adds both layers: it categorizes each webhook event per AI engine and connects it to prompt tracking, so Answer Engine Optimization (AEO) decisions rest on revenue, not guesses.

Finseo returns HTTP 200 on success. On a 4xx or 5xx failure, implement retry logic in your sender, ideally with exponential backoff. Common causes are invalid JSON, a missing channelId, or the rate limit of 100 requests per second per project being exceeded. Check the Finseo logs under Settings, then Logs, for details on rejected webhook requests.

AI search attribution ties conversions to the AI assistant that brought the buyer; analytics tools often record these visits as direct traffic. With Custom Webhook connected, Finseo assigns each lead, order or survey answer to the AI source named, so you can show what your AEO and GEO work is worth in revenue.