Start with a Source
A Source is the data admitted for analysis from a Survey. Select the versions, completed or partial attempts, confidence criteria and fields you need. Review the preparation and any exact acquisition quote before confirming. Opening a preview does not buy data.
Answers, stored contact or runtime variables, captured URL parameters and exported response metadata can all be analytical fields. Repeated blocks may provide linked working matrices. Choose the matrix whose rows match your question: a respondent and a repeated product are different units.
See acquiring data for analysis for selection, payment and updates.
Describe your preparation in a Recipe
The Recipe records transformations such as derived variables, filters, exclusions and weighting. Saving a draft preserves your choices; it does not replace the current Result.
- Read the Source fields and their types.
- Add the transformations you need and inspect their preview.
- Apply the Recipe when the changes are ready.
A categorical grouping, a calculated number and an extracted value from structured data need explicit definitions. Use fields returned by the Source instead of duplicating variables as hidden survey questions.
Explore an applied Result
A Result is the completed output of an applied Recipe branch. Its table shows the available fields and rows; exploration calculates summaries over the full selected Result, rather than just the visible page.
Filters and exclusions determine the analytical base. Weighting changes the contribution of cases while the real case count remains visible. An incomplete or failed calculation leaves the previous coherent Result available.
Explore a Result, export it, or connect it to a Report and share the Report with a public link. These are separate actions.
Choose following or fixed data
A following Source can use new data admitted to the Survey's shared acquisition. A fixed Source keeps its chosen capture. Changing this policy requires reviewing and confirming the proposed change.
Following does not authorize purchases or import unpaid responses. Source updates, applying a Recipe and publishing Report content each have their own controls. Stored response snapshots are used; current CRM data is not fetched to reinterpret an old response.
Keep different questions in different branches
Share common preparation steps, then branch when you need different filters, weights or outputs. Name each Result so its purpose is clear. A Report connects to a chosen Result; it does not silently switch to a sibling branch.