Why it matters
Link tracking webhooks allow you to send real-time data to external systems when a contact clicks a link. This enables advanced workflows such as syncing engagement data to your CRM, triggering automation in other tools, or building custom reporting outside of Whippy.
Key Concepts
Webhook: A real-time HTTP request sent to an external system when a specific event occurs.
Click event: The event triggered when a contact clicks a tracked link.
Payload: The data sent in the webhook request, which includes details about the click.
Endpoint: The URL where webhook data is sent.
Integration: Connecting Whippy with external tools using webhooks.
Step-by-Step: Set Up a Link Tracking Webhook
Go to Settings.
Open Link Settings.
Locate the Webhooks section.
Add a new webhook endpoint (URL).
Configure the webhook to trigger on link click events.
Save your settings.
Test the webhook by clicking a tracked link.
Confirm that your external system receives the event data.
What Happens When a Link Is Clicked
A contact clicks a tracked link.
Whippy records the click.
A webhook event is triggered.
A request is sent to your configured endpoint.
Your external system receives the data and can take action.
What Data Is Included
Webhook payloads typically include:
Link information (original URL and tracked link)
Click timestamp
Location data (country, city)
Device information
Conversation or campaign identifiers
This data allows you to understand who clicked, when they clicked, and where the interaction came from.
When to Use Webhooks
Use link tracking webhooks when:
You need to send click data to a CRM or external database
You want to trigger workflows in other tools (for example, Zapier or custom systems)
You are building custom analytics or reporting pipelines
You need real-time notifications of engagement events
Example Use Cases
Create a lead in your CRM when a contact clicks a link
Trigger a follow-up task for a sales team
Send engagement data to a data warehouse
Start an external automation workflow
Tips and Best Practices
Ensure your endpoint can receive and process HTTP requests
Log incoming webhook data for debugging and validation
Use secure endpoints and validate incoming requests
Test with sample clicks before using in production
Combine webhooks with internal automations for full workflow coverage
Troubleshooting
Issue | Possible Cause | Fix |
Webhook not triggering | Link tracking disabled or webhook not configured | Enable link tracking and verify webhook setup |
No data received | Incorrect or unreachable endpoint | Check endpoint URL and server availability |
Incomplete data in payload | Feature limitations or misconfiguration | Review webhook setup and test again |
Delayed or missing events | Network or server issues | Check logs and retry testing |
External system not responding correctly | Integration logic error | Validate payload handling in your system |