Vexo connects to the following tools:
| Integration | What it does | Where you set it up |
|---|---|---|
| Slack | Posts a daily analytics report and your alerts to a channel. | Your account settings |
| Microsoft Teams | Posts your alerts to a channel. | The app's settings |
| Jira | Files a Jira issue that links to a session replay. | The app's settings |
| Segment | Forwards your custom events to Segment. | The app's settings |
| Crashlytics | Imports Firebase Crashlytics crashes into Vexo's errors. | The app's settings |
| GitHub | Opens a pull request that installs the Vexo SDK in your repository. | The app's settings |
You set up an app's integrations in its App Settings, and only the app's owner can connect, change, or disconnect them.
Slack connects to your Vexo account, not to a single app, and you choose a channel for each app that you own.
/invite @Vexo AI.Each app's channel then receives:
To disconnect, click Disconnect Slack Integration, and then click Disconnect Integration. Vexo forgets your channel choices, so if you reconnect, choose them again.
Teams receives an app's alerts through a channel's Incoming Webhook.
https on an office.com host, for example https://your-org.webhook.office.com/webhookb2/.... Vexo doesn't accept Workflows webhook URLs.By default, the channel receives every alert. To receive only some, select them under Notifications. The list includes only error spikes, crash-free sessions drops, D1 retention falloff, and funnel step conversion falloff, so selecting any of them also stops anomaly alerts and custom event alerts.
To pause alerts and keep the URL, turn off Delivery enabled and click Save. To remove the integration, click Disconnect.
Jira lets anyone on the app's team file a Jira Cloud issue from a session replay.
To connect Jira:
https://your-team.atlassian.net, the Account email, and the API token.To file an issue:
APP, and a Summary of up to 255 characters. Optionally, add a Description.Vexo creates the issue with the type Task. Its description contains your description, a link to the replay, and the guest link if you attached one.
Segment receives your custom events from Vexo. Vexo doesn't import data from Segment.
Forwarding starts within 5 minutes. Vexo sends each custom event, from your mobile app and your website, as a Segment track call:
event is the custom event's name, and properties are its properties.anonymousId is the Vexo device ID.userId or email, Vexo first sends an identify call with the email and name traits, and sets userId on both calls.Vexo doesn't forward screens, errors, or other automatic events. If Segment rejects a batch three times, Vexo drops it. To pause forwarding and keep the key, turn off Forwarding enabled and click Save.
Forwarding has no extra charge: the events count toward your usage once, when Vexo receives them.
The Crashlytics integration imports crashes from Firebase Crashlytics into the app's Errors, where Vexo groups them with the crashes that its SDK reports. Vexo doesn't connect to Firebase. Instead, you run a scheduled job that sends rows from your Crashlytics BigQuery export to Vexo.
curl -X POST https://api.vexo.co/integrations/crashlytics/import \
-H "X-Api-Key: <your app API key>" \
-H "Content-Type: application/json" \
-d '{ "crashes": [ /* Crashlytics BigQuery export rows */ ] }'
Use the app's API key, the same key as the SDK. The response counts the rows that Vexo received, imported, skipped as duplicates, and skipped because they had no readable event_timestamp. Vexo uses event_id to skip rows that it already imported, so you can safely send a row again.
Vexo imports every row that you send into this app. It treats FATAL and ANR crashes as unhandled and NON_FATAL ones as handled. To show the screen where a crash happened, set a Crashlytics custom key named current_screen, screen, or route. Imported crashes have no session replay.
The section shows Last import and Imported crashes so you can check that the job runs. To pause imports, turn off Import enabled and click Save.
The VexoAI GitHub App opens a pull request that installs and configures the Vexo SDK in your repository.
For a React Native app, the pull request adds the vexo-analytics package. For a website, it adds the Vexo script. To write the change, Vexo sends your repository's JavaScript, TypeScript, HTML, Vue, and JSON files to OpenAI. The change contains the app's API key.
Each app connects to one repository, and VexoAI opens one pull request for it. To disconnect the repository, click Disconnect, and then click Disconnect Repository. VexoAI stays installed on GitHub. To uninstall it from your GitHub organization, for all your apps, click Remove VexoAI.
You can also start this setup from the app's setup page, with Set up with VexoAI.