Describe the audience, devices, and decision you need to study. Makeform builds an editable internet of things survey with ownership screening, device follow-ups, usage scales, setup questions, trust measures, and open feedback.
Send survey responses to Google Sheets, Slack, and Zapier.
Sample prompts for the survey builder
Choose a scenario, tailor its prompt, or send it to the builder. The question structure is an example, not a live AI result.
Audience
Adults who own or manage connected home devices
Format
Ownership matrix with device-specific follow-ups
Prompt size
231 chars
Example survey structure
Ownership matrix with device-specific follow-ups
Which connected home devices do you currently use?
Who completed the setup?
How often do you use each selected device?
How easily do your devices work together?
Suggested routing tags
Current IoT users
Former users
Interested non-users
Ask about each device category separately. A person may trust a thermostat but avoid a connected lock, and one broad score hides that difference.
Step 1
Screen
separate users, former users, and non-users
Step 2
Branch
show follow-ups for relevant device categories
Step 3
Measure
capture routines, friction, trust, and intent
Step 4
Segment
compare responses by device, tenure, or role
Research without guesswork
Connect ownership, behavior, breakdowns, and trust to the exact device being discussed instead of asking whether people like connected technology generally.
Use an ownership screener, then show category-specific questions. Non-users answer about barriers while owners report actual behavior.
Keep scales and time windows consistent so teams can compare ease, frequency, trust, or intent across devices.
Follow a key rating with open text so respondents can explain the failure, worry, or benefit behind it.
Four research angles
Study a connected device as a daily tool, product concept, operational system, or data relationship. Pick one primary decision.
Find where installation, account creation, pairing, Wi-Fi, permissions, or first automation causes people to pause.
Measure tasks, apps, hubs, assistants, and routines to see whether the product fits an ecosystem or creates work.
Ask separately about data collection, access, sharing, controls, and deletion instead of using one broad privacy question.
Test problem relevance, feature value, integrations, price expectations, and reasons for interest.
Survey workflow
Give Makeform the audience, devices, and decision. Then refine routing, labels, and scales before sharing.
State the decision, who qualifies, and which devices count as IoT in the study.
Reveal questions for selected devices. Give former users and non-users separate paths.
Remove assumptions, define time windows, ask one idea at a time, and preview every path.
Send responses to Google Sheets and compare device, tenure, role, or workplace segments.
Broad vs device-aware research
Branching keeps common measures comparable while tailoring details to each respondent's experience.
Field guide
Start with observable experience, then ask about attitudes and intent. These six sections add context to ratings and written feedback.
Eligibility and context
Capture ownership and role first. Purchasers, installers, and users may describe the same device differently.
Setup and ecosystem
Separate account creation, connection, pairing, permissions, updates, and integration to locate friction.
Behavior and routines
Use a recent time window. Frequency, trigger, and task distinguish routine from occasional use.
Reliability and recovery
Ask whether failures self-resolved, needed a workaround, triggered support, or reduced use.
Trust and control
Name specific data, purposes, and recipients; comfort can differ by use.
Value and next decision
Measure intent to keep, replace, recommend, connect, or consider, then ask why.
Related tools
Pair device-usage research with focused product, market, software, and testing surveys.
Explore problems, alternatives, decision criteria, and unmet needs.
Open toolCollect reactions to a prototype, beta device, or experience.
Open toolTrack beta defects, confusion, missing features, and continued-use intent.
Open toolStudy awareness, alternatives, buying roles, criteria, and language.
Open toolExamine routines, triggers, trade-offs, and household influences.
Open toolEvaluate companion-app usability, workflows, and feature priorities.
Open toolFAQ
Answers for teams planning connected-device research.
An internet of things survey studies connected products such as smart-home devices, wearables, sensors, appliances, or workplace equipment. It can measure ownership, setup, use, interoperability, reliability, trust, value, barriers, and intent. Define the devices and route questions by experience.
Ask about device, role, and tenure. Within a recent time window, cover frequency, tasks, triggers, apps, failures, workarounds, and outcomes. Add open questions for the main benefit and frustration.
Use a checkbox screener and conditional paths. Keep shared measures with the device name visible. If every product would make the survey long, focus follow-ups on the most-used device.
Ask what data respondents think is collected, comfort with specific uses and recipients, and whether controls are clear. Include Not sure, separate concerns from experience, and avoid unverified assumptions.
Yes, when common questions use the same wording, time window, and scale direction. Keep device context visible and examine categories separately before combining results. Include role and setting as segments.
Let the research decision and branches determine length. Ask only questions a respondent can answer, preview each path, and remove items that do not inform analysis. Separate owner and non-user paths keep the survey focused.
Yes. Makeform supports unlimited free forms and responses. You can generate, edit, publish, and collect responses without a response cap; the paid tier removes the Makeform badge. Review wording and routing before sharing.
Organize responses in the Makeform inbox or send them to Google Sheets. Set stable labels for device, status, tenure, and context before launch. Keep written answers beside their related ratings.
Study connected-device experience.
