Usabilla/GetFeedback: when does feedback become automatic measurement?

What is the service for?

Usabilla, also encountered through GetFeedback documentation, helps organisations collect feedback and show surveys. An SDK, a packaged library inside the app, can open a form when you request it. It can also receive app events and select an automatic survey campaign.

The provider documents custom variables: named values attached to feedback or used to target surveys, such as subscription type or a previously visited page. These are supported features, not proof that every inspected app sends those examples. A survey answer and the context attached to it are separate pieces of information. GetFeedback custom variables.

How can a survey tool observe behaviour?

Hypothetical example: an app reports “video failed” three times and a survey tool then offers a questionnaire. You have not yet typed an answer, but the trigger already describes app use. If the eventual answer includes an installation ID and subscription status, it gains more context than the words you submit. This explains why a feedback button and automatic event collection need separate treatment.

In this site, telemetry means information sent about the operation or use of software. It does not automatically mean advertising, and it does not automatically become anonymous just because it serves quality improvement.

What did the inspected integrations do?

Buienradar 7.4.8 configures UbTelemetryRecorder and calls Usabilla.sendEvent; the identified destination is sdk.out.usbla.net. Disable tracking forces telemetry level zero and stops automatic events. Its manual Settings feedback form remains. Pinned Buienradar audit.

The boundary differs in NU.nl 26.9.0: startup, queued events and the leaf sender are stopped, and explicit feedback or surveys may be unavailable. In AD 9.22.0, automatic events/custom variables stop while manual feedback initialization, readiness and form callbacks remain. These differences matter more than a generic claim that an SDK was “removed”. NU.nl audit, AD audit.

What does the evidence leave open?

The code identifies collection and sending paths; it does not supply a captured feedback payload from your phone. A manual form you choose to submit can still transmit its contents through retained functionality. Neither a domain name nor the presence of a survey SDK establishes retention, resale or every use of an answer.

Evidence reviewed 28 October 2026. See tracking mechanisms, identifiers and methodology.