Open Destinations in eventabee before starting this guide.
Click Add Destination, choose the destination type when it is available, give it a clear name, and save it. Then click Edit on the destination to fill in the structured fields and set the consent category.
If the type is not shown in the Add Destination menu, use Request a destination instead. eventabee currently exposes Meta, Google Analytics / Ads, TikTok, and Webhook directly in the add form; additional first-party connectors can be provisioned after review.
1. Add the destination
Click **Add Destination**, choose **Webhook**, enter a clear name, and save.
2. Enter the endpoint URL
Click **Edit** and fill in **Endpoint URL**. Use an HTTPS endpoint that can accept JSON POST requests.
3. Add authentication if needed
Fill in **Authorization Header** if your receiver requires it, for example:
```text
Bearer your-token-here
```
eventabee stores this as sensitive config. After saving, leave the field blank if you want to keep the existing value.
4. Consent category
Choose the category that matches what the webhook does:
- Analytics for internal analytics pipelines.
- Marketing for ad/retargeting/activation systems.
- Functional for non-marketing customer experience tools.
- Essential only when the destination is strictly necessary.
5. Advanced JSON
Business-plan stores may see **Advanced Config (JSON)**. Use it only for support-approved options; the standard UI does not provide a separate event-filter builder.
Retries and verification
Trigger a storefront event and inspect **Event Log**. Failed webhook deliveries are retried automatically, and failed rows can be retried from their delivery detail where available.
Troubleshooting
- Your endpoint must return a 2xx response for success.
- Keep response bodies small and avoid returning secrets.
- If a firewall is in front of the endpoint, allow eventabee’s outbound traffic or use a public HTTPS receiver.