How the webhook works
Every client account automatically has its own webhook endpoint in MetricDash. Forms, funnel builders, Zapier, Make or your own systems send leads straight into it — by default with name, email, phone and source, freely extendable with your own fields. Because each client has its own endpoint, enquiries automatically land in the right client account.
Set up and test
- 1Open the client account and copy the webhook URL.
- 2Add the URL in your form tool, funnel, Zapier or Make.
- 3Decide which fields are transmitted — at least name, email, phone and source.
- 4Use the built-in test function to send a sample lead and check whether it arrives.
What a lead contains
By default a lead transmits name, email, phone and source. Beyond that you can extend the fields freely — for example with a message, the campaign or your own IDs from your system. That way everything comes together in one place: one connection per client instead of scattered point solutions in the inbox, the form tool and the funnel builder.
Leads, sources and cost per lead
From now on every enquiry appears as a list in the agency dashboard and in the client portal — each with source attribution. MetricDash connects your campaigns’ ad spend with the incoming enquiries, so per client it becomes visible what a lead really costs. That is your strongest argument in the budget conversation.
In the automatic reports, leads appear as their own sections: the lead summary by source and the lead list. So your client gets campaign numbers and enquiries in one document.
Data protection and pitfalls
- Portal leads area: it only becomes visible after your client has given a one-time data-protection confirmation (legal basis, DPA, purpose limitation).
- Test first: always send a test lead before handing over the setup — that way you know the connection works.
- One endpoint per client: use the URL belonging to each client, otherwise leads land in the wrong account.