Skip to content
VEKTIS

Get Help & Share Feedback

Need help? Start with the channels below. Have product feedback? The form is at the bottom.

How to get help

Section titled “How to get help”

In rough priority order — pick whichever fits the question best.

  • Email support — help@vektis.io. Best for account questions, dashboard issues, and anything sensitive you don’t want in a public tracker.
  • GitHub Issues for SDK bugs — github.com/vektis-dev/tracker-js/issues. Best for @vektis-io/tracker problems you can reproduce from a code snippet — error codes, install-time issues, unexpected runtime behavior.

We’re a small team, so responses are best-effort rather than tied to a fixed SLA. The more context you include up front, the faster we can help.

What to include in a support request

Section titled “What to include in a support request”

Whichever channel you use, gathering this before you write saves a back-and-forth:

  • The Dev Item’s URL (so we know which one).
  • A screenshot of the section that’s misbehaving.
  • The full output of vektis.getStatus() from your app’s browser DevTools console.
  • The exact feature_id your code is reporting and the one configured on the Dev Item.

Try self-service first

Section titled “Try self-service first”

A lot of common issues resolve in seconds against the existing troubleshooting matrices. Worth a scan before you write to us:

  • Dashboard troubleshooting — missing metrics, weak baselines, blank impact scores, post-release gaps, feature-mapping mismatches.
  • Tracker troubleshooting matrix — every SDK error code mapped to its likely cause and fix, plus install-time issues that don’t surface as error codes.

Have product feedback?

Section titled “Have product feedback?”

Not stuck — just have an idea, a critique, or a wish-list item? Drop it in the form below. It’s a one-way mailbox; we read every response, but we won’t reply individually.

Section titled “Related”