All roles
Analysis-ready evidence

For Data & BI Analysts

Receive analysis-ready survey data with stable structure, quality context, valid bases, suppression rules, and provenance preserved for downstream work.

Data quality
Analysis and segmentation
Reporting handoff
Explore analyticsRead data documentation
Illustrative Gotopico response-quality workspace with a completion funnel, review signals, segment chart, and reversible review queue.
Illustrative product view—not a customer result
Available

A relevant product path

Review response quality before analysis

For data analysts, start with clean exports: Start from typed question structures and export stable CSV or JSON with question and response context.

Open the matched decision guide

Problems this playbook solves

Each path starts with a concrete decision, names the method, and links to the deeper problem guide.

Clean exports

Problem

Inconsistent schemas and undocumented transformations slow every downstream analysis.

How to solve it

Start from typed question structures and export stable CSV or JSON with question and response context.

CSV
JSON
Open the decision guide
Reviewed data handoffs

Problem

A chart without sample, method, and caveats invites overinterpretation.

How to solve it

Carry bases, suppression rules, quality notes, and provenance into stakeholder outputs.

Quality review
Provenance
Open the decision guide
Built-in analysis

Problem

Repeated manual setup delays straightforward cuts and method-specific readouts.

How to solve it

Use built-in crosstabs, trends, text themes, and advanced-method results before deeper custom analysis.

Crosstabs
Method analysis
Open the decision guide

Survey examples

Three surveys for the decisions ahead

Start with the decision, inspect the evidence available today, and keep the limits attached to every handoff.

Response Quality Audit

Carry response dispositions, valid bases, and review context into downstream analysis.

Public quality-review workflow capture.
Analysis · Captured

Synthetic example · not a customer result.

Public: Available

Boundary: Quality metadata informs review; it is not a universal fraud guarantee.

Evidence gap: Golden JSON/CSV and response-level dispositions are bound to identical synthetic rows; an authenticated response-level product capture remains missing.

Use audit templateRead study evidence and limitations
How it works and evidence limits

Use this when

Analysts receive rows without the context used to include or exclude them.

What you do

Review response-level signals and dispositions.

  • Response-level review flags
  • Visible valid-base changes
  • Review state in exports

Evidence returned

Valid bases, flags, identifiers, and export columns.

Product: Live
Evidence: Seeded Capture Ready

Illustrative product view using synthetic data. It is not a customer result or outcome claim.

Inspect synthetic quality evidence

Capabilities: csv-excel-json-exports, presentation-and-share-links

Read evidence provenance and downloads

Technical study evidence

Illustrative technical evidence using deterministic synthetic data. It is not a customer result, live connector receipt, or outcome claim.

Fixture version
technical-persona-evidence.v1
Declared fixture timestamp
Provenance
Checked-in deterministic synthetic fixtures. Hashes identify artifact contents; they do not certify live execution.

Limitations

All organizations, products, respondents, identifiers, results, and delivery acknowledgements are fictional.

Authentication and signing material is omitted or visibly redacted; these files contain no usable credentials.

Webhook and warehouse receipts validate fixture lineage only and do not prove a live connector, external delivery, retry policy, or signature verification.

No artifact is customer evidence, production availability evidence, a security claim, or an outcome claim.

Artifact downloads

v1/api/pricing-analysis.response.json

SHA-256: 5725bfb1ca16b5ec80eac28f0ffb296e6d06f1ce2eaa123693d338d1490d201e

v1/api/pricing-study.create.request.json

SHA-256: d16f54ecf1f711bc5ad265b720da8ae93e034ce42573ba988e4247f146b86d56

v1/api/pricing-study.create.response.json

SHA-256: 15b37a335e3dc2f1a240c867675b83b9beaf764e2abefe0420c0798290e6f45b

v1/api/readiness.corrected.request.json

SHA-256: 5e72f05df67846de9bbe574d18b0bd43610e7f18133e1fca2ad09dd493b82348

v1/api/readiness.corrected.response.json

SHA-256: a1db393eb97b2fa0c8269f121ffcc76ba3fb7f92191e383764a7ef7aa7c11ca4

v1/api/readiness.invalid.request.json

SHA-256: 62b7fea239ce80429cbc850afa429fa27c535f5d36f3647d5f2dfe405b9daba7

v1/api/readiness.invalid.response.json

SHA-256: 35e685f5ba33232141dcab3fde950d0b8de3023ed4f6e206df00dce50de97d9c

v1/audit/warehouse-delivery.json

SHA-256: 7faaeb848549cea440719bcc90eafba59dff2c5af481db8f3948f52bc48f6c90

v1/exports/readiness-survey.v1.json

SHA-256: 2a061a1e0120336af941ae36ef8e625b8994ae48e77b7cd47432d0b7d5823e2c

v1/exports/technical-responses.v1.csv

SHA-256: 9472d201249eaf5e8a8bd57dc6e2695aca67bbbe807e665859674c3825bd531a

v1/exports/technical-responses.v1.json

SHA-256: d49dbd1f5c3d76d2f79ab1b714b732e4991c2986f2b49d4ee406826fd22d58ea

v1/quality/quality-review.json

SHA-256: 0bfa8d0a6978bb84758f716e3cf19f36e77ba2cc60ae628e59b8ded8027f1b72

v1/reports/stakeholder-report.json

SHA-256: e2ecf76581a872a274d3316cadf8b7aa820bcf6d2ba864a83500ac2e00573657

v1/source/technical-responses.json

SHA-256: 73cf5f1ed401188b540b8de550788e95bc800cc48c95ae09d36f3703850ca374

v1/webhooks/response-exported.receipt.redacted.json

SHA-256: 5de2c0a520f1944982399f0cce0e2bfd5ed9f24f068759be1d7ddef66a07fd0a

v1/webhooks/survey-published.receipt.redacted.json

SHA-256: 8238f18ce232ab04a5cb2cc8e5c69703cc16d73efe99fad2478fe7bd24c0e615

Download machine-readable manifest

Stakeholder Report Readiness

Keep method, base, provenance, and caveats attached when evidence leaves analysis.

Public stakeholder-report workflow capture.
Analysis · Captured

Synthetic example · not a customer result.

Public: Beta

Boundary: A report communicates evidence; it does not certify the decision.

Evidence gap: A canonical synthetic report object now binds method, bases, provenance, caveats, review, and export; authenticated read-only share capture remains missing.

Preview report templateRead study evidence and limitations
How it works and evidence limits

Use this when

Charts lose method, base, provenance, and caveats during handoff.

What you do

Assemble an evidence inventory and publish a reviewed report.

  • Evidence inventory
  • Base-aware reviewed report
  • Read-only stakeholder view

Evidence returned

Charts, bases, caveats, and a read-only stakeholder view.

Product: Beta
Evidence: Template Ready

Illustrative product view using synthetic data. It is not a customer result or outcome claim.

Inspect synthetic report evidence

Capabilities: presentation-and-share-links, pdf-reports

Read evidence provenance and downloads

Recurring study evidence

Illustrative product evidence using deterministic synthetic data. It is not a customer result or outcome claim.

Fixture version
persona-recurring-evidence-manifest.v1
Declared fixture timestamp
Provenance
Checked-in deterministic synthetic fixtures. Hashes identify artifact contents; they do not certify live execution.

Limitations

Wave-to-wave movement is descriptive and does not establish that a campaign, product change, or service intervention caused an outcome.

Minimum reportable base: 30. Fixture readiness does not establish authenticated product capture or live publication.

Artifact downloads

brand-tracker-instrument.v1.json

SHA-256: ca65e3803b203c6782e58803a377172f1c210d20074e8749606dff910edd50d9

brand-tracker-response-summary.v1.json

SHA-256: de175941dc189c0666aa69e7b0be03116759733ff967733865a8d2a7f3758a2f

nps-csat-diagnostic-instrument.v1.json

SHA-256: e26db48287327e9c54b1b5c6c6b43c8443113a70f52c39bbdf2f9e55ae4efa50

nps-csat-diagnostic-response-summary.v1.json

SHA-256: 629152b21fcff10d3d0eca4b2214685347d5249e2806a6fd444bfcaca60fe6d1

stakeholder-report.v1.json

SHA-256: 19aa996807e7ff40d616b5562cc72ef667cf7342023233cbe5c3416539d4a25c

stakeholder-report-public-share.v1.json

SHA-256: 959ac3a046ccf499d8a672853226d01842131ee55cbcf9fd9fd2b9eb20fdcc9b

stakeholder-report-export.v1.json

SHA-256: b9e1418bbdd93a731ed9b9d9b0b5296d01703011932685c3e2018bc1694b053f

Download machine-readable manifest

Research Data Stack Feedback

Define schema, missingness, webhook, and audit requirements before integration begins.

Public API automation workflow capture.
Analysis · Captured

Synthetic example · not a customer result.

Public: Beta

Boundary: Connectors and exports must retain documented status and limits.

Evidence gap: Versioned golden exports and redacted webhook/warehouse fixture lineage exist; no connector, external delivery, or authenticated audit capture has been verified.

Preview data templateRead study evidence and limitations
How it works and evidence limits

Use this when

Survey-to-warehouse requirements are discovered after integration begins.

What you do

Collect internal requirements and test a versioned handoff contract.

  • Integration-needs instrument
  • Versioned export contract
  • Webhook and audit trail

Evidence returned

Structured response, schema, missingness, webhook, and audit record.

Product: Beta
Evidence: Template Ready

Illustrative product view using synthetic data. It is not a customer result or outcome claim.

Inspect synthetic delivery evidence

Capabilities: csv-excel-json-exports, event-webhooks, scoped-api-keys

Read evidence provenance and downloads

Technical study evidence

Illustrative technical evidence using deterministic synthetic data. It is not a customer result, live connector receipt, or outcome claim.

Fixture version
technical-persona-evidence.v1
Declared fixture timestamp
Provenance
Checked-in deterministic synthetic fixtures. Hashes identify artifact contents; they do not certify live execution.

Limitations

All organizations, products, respondents, identifiers, results, and delivery acknowledgements are fictional.

Authentication and signing material is omitted or visibly redacted; these files contain no usable credentials.

Webhook and warehouse receipts validate fixture lineage only and do not prove a live connector, external delivery, retry policy, or signature verification.

No artifact is customer evidence, production availability evidence, a security claim, or an outcome claim.

Artifact downloads

v1/api/pricing-analysis.response.json

SHA-256: 5725bfb1ca16b5ec80eac28f0ffb296e6d06f1ce2eaa123693d338d1490d201e

v1/api/pricing-study.create.request.json

SHA-256: d16f54ecf1f711bc5ad265b720da8ae93e034ce42573ba988e4247f146b86d56

v1/api/pricing-study.create.response.json

SHA-256: 15b37a335e3dc2f1a240c867675b83b9beaf764e2abefe0420c0798290e6f45b

v1/api/readiness.corrected.request.json

SHA-256: 5e72f05df67846de9bbe574d18b0bd43610e7f18133e1fca2ad09dd493b82348

v1/api/readiness.corrected.response.json

SHA-256: a1db393eb97b2fa0c8269f121ffcc76ba3fb7f92191e383764a7ef7aa7c11ca4

v1/api/readiness.invalid.request.json

SHA-256: 62b7fea239ce80429cbc850afa429fa27c535f5d36f3647d5f2dfe405b9daba7

v1/api/readiness.invalid.response.json

SHA-256: 35e685f5ba33232141dcab3fde950d0b8de3023ed4f6e206df00dce50de97d9c

v1/audit/warehouse-delivery.json

SHA-256: 7faaeb848549cea440719bcc90eafba59dff2c5af481db8f3948f52bc48f6c90

v1/exports/readiness-survey.v1.json

SHA-256: 2a061a1e0120336af941ae36ef8e625b8994ae48e77b7cd47432d0b7d5823e2c

v1/exports/technical-responses.v1.csv

SHA-256: 9472d201249eaf5e8a8bd57dc6e2695aca67bbbe807e665859674c3825bd531a

v1/exports/technical-responses.v1.json

SHA-256: d49dbd1f5c3d76d2f79ab1b714b732e4991c2986f2b49d4ee406826fd22d58ea

v1/quality/quality-review.json

SHA-256: 0bfa8d0a6978bb84758f716e3cf19f36e77ba2cc60ae628e59b8ded8027f1b72

v1/reports/stakeholder-report.json

SHA-256: e2ecf76581a872a274d3316cadf8b7aa820bcf6d2ba864a83500ac2e00573657

v1/source/technical-responses.json

SHA-256: 73cf5f1ed401188b540b8de550788e95bc800cc48c95ae09d36f3703850ca374

v1/webhooks/response-exported.receipt.redacted.json

SHA-256: 5de2c0a520f1944982399f0cce0e2bfd5ed9f24f068759be1d7ddef66a07fd0a

v1/webhooks/survey-published.receipt.redacted.json

SHA-256: 8238f18ce232ab04a5cb2cc8e5c69703cc16d73efe99fad2478fe7bd24c0e615

Download machine-readable manifest
Role-specific workflow
1

Before analysis: review field definitions, missingness, response-quality flags, and valid bases.

2

Before handoff: document transformations, suppression, confidence, and the decision each output supports.

Decision-ready handoffs
CSV export
JSON export
Quality flags
Chart snapshot
Decision report

Important context: CSV, Excel, and JSON are live; other formats retain their explicit capability status and should not be represented as universally available.

Start Here Next

Templates

Analysis-ready survey templates

Open templates that already include method tags, quality gates, and export-friendly structures.

Browse templates
Use cases

Find the decision workflow

Map the analysis plan to pricing, roadmap, message testing, or customer feedback use cases.

Browse use cases
Trust

Defend data handling

Review privacy, governance, quality, and statistical honesty controls before sharing outputs.

Review trust

Related roles

DevelopersIntegrate research without guessing schemas: inspect capabilities, fail invalid studies before fielding, and keep credentials and delivery boundaries scoped.UX researchersShip research at product speed while keeping the instrument, valid base, quality decisions, uncertainty, and reviewer context intact.

Explore analysis templates

Discuss a data workflow

Explore analyticsRead data documentation