Webhooks

Webhooks send real-time notifications to external services when specific events occur in your Ovyxa analytics. Use them to trigger alerts, sync data, or automate workflows.

How Webhooks Work

When a configured trigger fires, Ovyxa sends an HTTP POST request to your webhook URL with a JSON payload describing the event.

Setting Up a Webhook

1. Go to Settings → Webhooks for your site
2. Click Add Webhook
3. Enter the destination URL (must be HTTPS)
4. Select the trigger event(s)
5. Click Save

Trigger Events

Trigger	Description
goal.completed	A visitor completes a goal (pageview or custom event goal)
usage.threshold	Monthly event usage reaches 80% or 100% of plan limit
realtime.spike	Active visitor count exceeds a configured threshold

Payload Format

All webhook payloads follow this structure:

{
  "event": "goal.completed",
  "timestamp": "2025-03-15T14:32:18Z",
  "site_id": "your-site-id",
  "data": {
    "goal_name": "Purchase",
    "visitor_count": 1,
    "url": "/checkout/success",
    "source": "google",
    "country": "FR"
  }
}

Retry Logic

If your endpoint returns a non-2xx status code, Ovyxa retries the webhook:

• Retry 1: 1 minute after failure
• Retry 2: 5 minutes after first retry
• Retry 3: 30 minutes after second retry

After 3 failed attempts, the webhook is marked as failed. Check the webhook logs in settings to see delivery status and error details.

Use Cases

Slack Notifications

Send a message to a Slack channel when a goal is completed. Use Slack's incoming webhook URL as the destination.

Zapier Integration

Connect Ovyxa to 5,000+ apps via Zapier. Use Zapier's webhook trigger to receive Ovyxa events and route them to email, Sheets, CRM, or any connected service.

Custom Alerting

Build your own alerting system by receiving webhook events on your server and triggering notifications based on custom logic (e.g., alert when revenue goal reaches 100 completions/day).

Security

• Webhook payloads are sent over HTTPS only
• Each webhook includes a X-Ovyxa-Signature header containing an HMAC-SHA256 signature
• Verify the signature on your server to ensure the request came from Ovyxa
• The signing secret is shown when you create the webhook

Limits

• Maximum 5 webhooks per site
• Payload size: < 10KB
• Timeout: 10 seconds per request
• Rate: maximum 100 deliveries per hour per webhook