Analytics, Audit log and User data view
Open a deployed service's analytics link from Environments and choose QA or Production. Use Analytics for performance, Audit log for events and User data view for individual journey state.
Choose the evidence you need
| View | Purpose | Limits |
|---|---|---|
| Analytics | Starts/completions, page hits, completion/drop-off/bounce, validation failures, time per journey/page, device/browser and tagged-field breakdowns. | Today can be about 30 minutes behind. Very large date ranges may need narrowing. Tagged-field charts require service configuration. |
| Audit log | Chronological page, submission, validation, action, review and file-error events. Filter by time, submission/user, event and outcome. | Detailed evidence can expire. A missing event/result is not proof that nothing happened. |
| User data view | Saved journey status, answers, selected answer columns, last update and links to full data/audit history. | Includes incomplete work where permitted. Old/expired data may be unavailable; this is different from a submitted-response-only export. |
Access and library controls
External QA testers do not have Builder analytics access. Individual data and audit evidence require the appropriate environment/data permissions and MFA where required. Production follows the Live data access boundary. Library Security settings can disable User data view or Audit log, prevent live export, or limit administrator reopening/deletion.
Use the current role and environment rather than assuming a visible aggregate chart grants access to individual answers. Response Hub provides a separate submitted-response/team workspace.
Investigate an action or reported problem
- Confirm the environment, service version, submission reference and approximate time.
- Filter Audit log to that journey, then inspect the relevant validation/action/file event.
- Check action ID/type, response code, error and available request/result details.
- Compare the saved answers and form revision with the intended route.
- For an integration, verify delivery at the destination; processing completion alone is insufficient.
Detailed payloads can contain personal information. Use authorised views and avoid copying complete records or credentials into support messages. User view action mocks do not establish real external delivery.
Exports, reopening and retention
Live exports require library permission. Downloaded files are outside Govform's access control. Administrator reopening is enabled unless disabled; live deletion is disabled unless enabled. Use each action's confirmation and the service's retention process.
Deleting a response does not refund a payment. Accepted unpaid responses use Awaiting payment, and submitted-data APIs exclude them until submission. Use Response history for exact submitted-version evidence rather than treating a changing draft as the original submission.
For automation, see Analytics events API, Journey analytics API and Submitted data API.