建设中

你的这次采样正好赶上我们施工。

这些指南面向新版 ExpiWell 平台(v2),仍在撰写、校对和调整中——请谅解眼前的脚手架:页面可能在两次访问之间移动或更改。仍在使用旧版应用?其文档仍保留在旧的支持门户上。

打开旧版支持门户
知识库  /  来自 ExpiWell 团队

我们能帮你什么?

覆盖研究每一步的指南——从第一个项目到最终的数据导出。ExpiWell 知识库,服务于研究者网页平台与参与者移动应用。

29 个类别下共 101 篇指南 · 由 ExpiWell 团队维护更新
Help CenterBuildGEMA

Geographic Ecological Momentary Assessment (GEMA)

Build · GEMA
Updated 2026年10月13日

What GEMA is

Geographic Ecological Momentary Assessment (GEMA) is EMA with location attached. Participants report in the moment as they normally would — mood, stress, symptoms — and their location is recorded alongside it, so an answer carries the place it was given in.

That is the whole point: a stress rating from a crowded office and the same rating from a quiet park are different findings, and retrospective recall cannot tell them apart. GEMA lets you see which environments a pattern belongs to, and design interventions around them.

Geofencing

A geofence is an invisible boundary drawn around a real place. When a participant's phone crosses it — entering, leaving, or staying inside for a set time — ExpiWell can send them a survey automatically.

This is what makes a GEMA study active rather than merely observational: instead of sampling at fixed times and hoping the interesting moments fall inside them, you ask the question at the place it is about.

Before you start

Three things have to be true before any of this is reachable.

  • Continuous location tracking is on. It lives in the Integration step, and switching it on shows how often your plan samples location.
  • Your surveys exist. A geofencing task fires a survey you have already built; you cannot create one from here.
  • The project is not active. Triggers are part of the Schedule step and lock once a study is running — see below.
The Integration step with Continuous location tracking switched on and a GPS active badge, showing its sampling interval and an optional sub-toggle to require location sharing to join the project

Require Location Sharing to join Project appears underneath once tracking is on, as a separate toggle. Switch it on and participants must grant location permission before they can join at all — worth it for a study that is meaningless without location, unnecessary otherwise.

Note

Only one integration runs per study. Turning on location tracking rules out Fitbit, Apple Watch and SensorKit for the same project.

Creating a geolocation event

An event is a container. Inside it you add one or more tasks, each one a geofenced area with its own survey and rules.

Open Project Setup → Schedule, then switch to Event Triggers using the second icon in the narrow rail down the left.

The Event Triggers tab on the Schedule step with a New Event button, a search field and a type filter, above three event cards each naming its surveys, tagged Geolocation and showing how many tasks it holds

Each card names the surveys it fires, its type, and how many tasks it holds.

Important

Triggers cannot be changed while the project is active. A banner says so across the top and New Event grays out. Set your geofences up before you activate, or deactivate the project to change them — the same rule the Integration step follows.

Click New Event, name it, and choose what to base it on. Four types are offered; Geolocation is the one that fires by place. Create stays disabled until a type is picked.

The New Event dialog with an event name entered and four type cards — Survey Submission, Schedule Edit, Exiting Survey and Geolocation — with Geolocation selected and the Create button enabled

The other three fire on something a participant does rather than somewhere they go; see Event triggering.

Drawing the area

The Geolocation Triggers page opens on a world map — it does not center on you, and nothing asks for your location. Zoom to the place you care about first.

The Geolocation Triggers page showing a world map with zoom and drawing tools, an Upload GeoJSON button above it, a note that no geofenced areas are configured yet, and an empty Configured Tasks section below

Use the rectangle or polygon tool on the left of the map to draw the boundary. Finishing the shape opens the Configure Geofencing Task dialog.

Note

You do not need an external tool to draw a boundary. Upload GeoJSON is for a polygon someone has already defined elsewhere — a campus outline from a facilities team, say. For anything you are defining yourself, drawing it on the map is the shorter path.

Configuring the task

The dialog has six groups. Stay Time is the only field marked required, and only when the trigger type calls for it. The label and the survey are yours to fill; the timing, rate-limiting and scheduling fields all arrive with working defaults.

Location Label and Area Color

A name for the area and the color it takes on the map. Both appear in the task list afterwards, so a color per site is worth the two seconds.

Survey Configuration

  • Survey to Trigger — which survey fires.
  • Trigger Type — Entering Location, Staying in Location, or Leaving Location.

Timing Configuration

  • Survey Window — how long the triggered survey stays available, in minutes.
  • Start After Trigger — minutes to wait before sending it; 0 for immediate.
  • Stay Time — how long they must remain inside before it fires. Only appears for Staying in Location, and is required when it does.
The Configure Geofencing Task dialog with Trigger Type set to Staying in Location, which adds a required Stay Time field beside Survey Window and Start After Trigger, above the Geofenced Area map showing a drawn rectangle and its captured area in square kilometres

Geofenced Area

The shape you drew, on its own map with edit, move and erase tools if you need to adjust it. The dialog reports the area it captured in km², which is worth a glance — it is easy to draw something far larger than you meant.

Rate Limiting

  • Daily Cap (max triggers per day) — leave empty or 0 for unlimited.
  • Suppression Window (minutes) — the minimum gap between consecutive surveys; 0 for none.
Important

Set these before you run a location study. A participant who works inside your geofence crosses it repeatedly, and without a cap every crossing is another survey. The daily cap bounds the total; the suppression window stops a cluster of them arriving in one afternoon.

Active Hours

Active from and Active until restrict firing to a window in the participant's local time. Leave both empty to allow all day.

Two behaviors worth knowing: someone already inside — or already out of — the area when the window opens gets the survey then, rather than having to cross the boundary again. And the end time may be earlier than the start — that is how you span midnight.

Advanced Options

Pause overlapping survey windows pauses other survey windows that overlap the one this trigger opens, so a location survey does not land on top of a scheduled one. Switching it on reveals Surveys to Pause.

The lower half of the Configure Geofencing Task dialog with Rate Limiting fields for a daily cap and suppression window, Active Hours with from and until times, and an Advanced Options checkbox for pausing overlapping survey windows

After the task is created

The area appears on the map with its label and color, and Configured Tasks lists it with everything you set, plus controls to edit or delete it.

The Geolocation Triggers page after a task is created, with a toast confirming it, one labeled geofenced area shaded on the map and a Configured Tasks table beneath listing the location label, survey triggered, survey window, trigger type, timing, daily cap, suppression window and active hours, with edit and delete controls

One event can hold several areas and several tasks — draw again to add another.

Note

The table words the trigger differently from the dialog. A task set to Staying in Location is listed as At location (Stay time 10 mins). Same setting, two phrasings — go by the stay time rather than the name.

Reusing a survey across tasks

Assign a survey that another geofencing task already uses and a Survey Conflict Detected advisory explains why not: if the two conditions fire close together — entering and leaving the same place, say, within about ten minutes — the deliveries can overlap and interfere.

A Survey Conflict Detected advisory over the Edit Geofencing Task dialog, warning that the survey is already used in another geofencing task and that close-together events can overlap, with Choose Different Survey and Continue Anyway buttons

Choose Different Survey or Continue Anyway — it is a warning, not a block. Give each condition its own survey unless you have a reason not to.

What participants have to do

Once the project starts, participants must set the ExpiWell app's location permission to Always Allow. Anything less and the app stops reporting location in the background, which is where almost all of it happens.

Important

iOS suspends background apps. iOS participants should open ExpiWell periodically — particularly around geofenced areas — or the system may stop it reporting and the trigger never fires.

Note

How often location is sampled depends on your plan. The default is every 5 minutes; GEMA, GEMA+ and Zenith plans — including their trial variants — sample every 1 minute. The Integration step states the figure for your own plan next to Continuous location tracking. Either way there is some delay between crossing a boundary and the survey arriving, so do not design a study that depends on an instant response.

Was this helpful?
Start today

与 ExpiWell 团队的真人交流。

还没解决?我们的研究者团队既解答技术问题,也解答研究设计问题。