Connect Slack, issue trackers, revenue and support tools
Last updated
Integrations put Metrickle's findings where your team already works, and bring in the data that shows what a lost conversion cost you: payments, refunds, support tickets and releases. Each app has its own Integrations page. Open your app under Apps in the sidebar, then choose Integrations.
The page has a section for each kind of integration. Setting things up needs the right permission, such as Set up Slack, Teams, webhooks and revenue sources (Stripe, RevenueCat) or Connect issue trackers. Owners and admins have all of them. See team and access for roles.
Notify: Slack, Microsoft Teams and webhooks
Notify sends feedback reports, alerts and fix results to a channel or your own endpoint as they happen.
To add a destination:
- In Notify, choose Add Slack, Teams or webhook.
- Pick the Type: Slack, Microsoft Teams or Webhook.
- Paste the URL. The hint under the field says where to find it:
- Slack: Apps, then Incoming Webhooks, then Add to Slack. Pick a channel and copy the webhook URL.
- Teams: open the channel's menu, then Workflows, then "Post to a channel when a webhook request is received", and copy the URL.
- Webhook: any HTTPS endpoint of yours.
- Give it a Name, such as the channel name.
- Under Send, tick what should go there.
- Choose Add destination.
What you can send
| Choice | Sent when |
|---|---|
| Feedback reports | Someone sends a "Report a problem" report. Accessibility barriers are called out. |
| Task success drops | A saved task's success rate over the last 24 hours is well below its 7-day baseline. |
| New friction hotspots | An element, form or page started causing friction in the last 24 hours. |
| Protected tasks | A protected flow goes red: people using an accessibility setting fall clearly behind people using none since the latest release. |
| Cases opened | A case opens on a broken task, with the step, element and segment that lose most, and what it costs. |
| Cases closed | A case closes, because its fix was verified or an owner dismissed it. |
| Fix results | Seven days after a linked issue is closed: the metric before and after the fix. |
| Study sessions booked | Someone books, moves or cancels a moderated research session. |
| Study tests completed | A participant finishes an unmoderated test, or a moderator wraps up a session. |
Alerts are checked every hour. A task alert is sent at most once a day and a hotspot at most once a week, so an ongoing problem doesn't post every hour.
Test, pause and check deliveries
Each destination has an actions menu:
- Send test posts a test message and tells you whether it arrived.
- Delivery log shows the last 50 deliveries, newest first, with the result of each.
- Choose what's sent changes the events.
- Turn off pauses it without losing the settings. Turn on starts it again.
- Remove stops it for good and deletes its delivery log.
If a destination starts failing, a warning at the top of the page names it, with a link to its log.
Signed webhooks
When you add a webhook, Metrickle shows a signing secret once. Store it with your endpoint. Every request is JSON with a Metrickle-Signature header, which you check against the secret; the dialog includes code to verify it. Any 2xx response counts as delivered. 5xx responses and timeouts are retried twice.
Event sources
Event sources take events from Segment or RudderStack, so you don't need to add Metrickle's script. Choose Set up next to the source and follow the steps. For details, see event sources.
Track work: issue trackers
Create issue on a feedback report, hotspot, task or case opens an editable draft, then files it in your tracker. Metrickle links the issue and measures the result after it's closed.
Tracker accounts are connected once for the whole workspace, then each app picks where its issues go. Metrickle supports:
- Linear
- GitHub Issues
- Jira Cloud
- GitLab, including self-managed GitLab reachable over HTTPS
- Azure DevOps Boards
- Shortcut
- Asana
- ClickUp
- Trello
- YouTrack
To connect a tracker:
- Open Team & workspace in the sidebar.
- Under Issue tracker accounts, choose Connect account.
- Pick the Tracker and paste an access token you made in it. The form explains where to make the token and what access it needs. The token is checked, stored encrypted and never shown again.
To choose where an app's issues go:
- On the app's Integrations page, find Track work.
- Select Choose, or Change if issues already go somewhere.
- Pick the Account, then the team, repository, project or list. Only ones the token can see are listed.
- Choose Save.
Revenue: Stripe and RevenueCat
Revenue brings payments, refunds and cancellations onto the person who made them. That's how Metrickle puts a money figure on a broken flow, and how a refund or cancel within 7 days takes back a completed task.
- Stripe: payments, refunds and subscription cancels from your Stripe account.
- RevenueCat: in-app purchases, renewals, refunds and cancels from the App Store and Google Play.
Choose Connect next to one and follow the steps. To tie payments to people, give Stripe or RevenueCat the same user id you pass to identify(). Stripe can backfill the last 30 days. For the full setup, see revenue.
Support inbox: Zendesk and Intercom
Support inbox brings Zendesk tickets and Intercom conversations into Feedback. A matched ticket about a problem takes back a task the person finished in the 7 days before, just like an in-app problem report.
- Choose Connect Zendesk or Intercom.
- For Zendesk, enter your Zendesk subdomain, an Agent email and an API token. For Intercom, choose Where your workspace is hosted and paste an Access token.
- Choose Connect.
Tickets from the last 7 days come in straight away. After that, new tickets arrive within seconds by webhook, with an hourly sync as a fallback. Where Metrickle can't add the webhook itself, the dialog walks you through it. You can also set how tickets are sorted into categories, which tags to skip, and how tickets are matched to people.
Releases
Releases marks deploys on the Overview chart and in alerts, so you can see which release cost you conversions. New app versions are added automatically. For web deploys, choose Set up deploy hook and call the URL from your CI, or choose Add release to add one by hand. See releases.
Accessibility scans
Accessibility scans take axe-core results from your CI and show each violation next to the friction it causes. Choose Set up scan hook and post results to the URL from CI.
Fixes: measuring what an issue changed
Every issue created from Metrickle records its metric over the 7 days before it was opened. Seven days after it's closed as done, Metrickle measures the same thing again. The app's Fixes page shows each linked issue as Open, Measuring, Fix worked or No improvement. Issues closed as not planned aren't measured. Choose Fix results on a Notify destination to get these in Slack, Teams or your webhook too.
AI assistants
To let Claude or another AI assistant read your analytics and draft funnels, goals, tasks and surveys, open Connect AI in the sidebar. Most assistants sign in with your Metrickle account and you choose the workspace and access; scripts and CI can use a token instead. An assistant never does more than you can, and can't put a survey live, protect a task, or delete anything. See AI assistants over MCP.