What the participant sees first
The gate applies to the text and media modalities: video, audio, text, image, and document. Interactive and chat studies never have one. The card is a single generic feed card in one of four looks, picked from the content type: video (16:9 thumbnail), news for news and editorial articles (16:9), product (square), and social (square). It is not dressed as any particular platform’s feed. An email is the exception: its card is the inbox row (sender, subject, and preview text), and its rate is called the open rate. You can write the card yourself as afeed_preview on the iteration’s details:
Every field is optional. Without a
feed_preview, ish builds the card from the
content’s own title, caption, and first image. With nothing to show at all (an
email with no subject or sender, or an item with no title, caption, or image), the
run goes ahead ungated.
The card renders only images stored in ish. A thumbnail URL from another host
shows as a blank placeholder tile. The web app copies a pasted thumbnail into ish
when you save the card; through the CLI or MCP, upload the image first.
What the decision does to the run
The participant answers three things: whether they would open it, why (in a sentence or two, in their own words), and roughly how many seconds they spent on the card. The gate step carries no sentiment or engagement reading.- Opened. The participant goes on to the content, and the rest of the run is the same as an ungated one. An email opener goes straight to the body.
- Scrolled past. The run stops before any content. The participant is marked
completed, skips the closing interview, and is billed for that one step.
content_config.early_termination), a separate setting that
applies after someone has opened it.
Because only openers see the content, every metric after the gate (engagement,
sentiment, conversion) describes openers only. The web app says so beside those
numbers. Non-openers’ reasons still reach the study’s
findings.
How the would-open rate is counted
For each version, the rate is the number of participants who would open it divided by the number who recorded a decision. A participant with no recorded decision is left out, never counted as a no. Versions are ranked by rate. The rate is worked out each time you read it, so it needs no analysis run. Read it as a ranking of your cards against each other, within one study. It is not a forecast of a real click-through or open rate, and it does not compare across studies or over time. Below 15 decisions, the web app shows the split as a count (“4 of 9”) instead of a percentage. Beside the rate, the web app shows an entry funnel for each version: of the participants who completed a run, how many opened the content, carried on past its first moment, and finished it.Turning it on
The gate is a per-iteration setting,preview_gate_enabled in the iteration’s
content_config. New iterations of an email or a social post have it on by
default; every other content type has it off.
The would-open rate, the reasons, and the funnel are read in the web app, on the
study overview and in each participant’s replay, which shows the exact card they
saw and whether they opened it. Public share links carry the rate too. The CLI
and MCP do not return it; there you read each participant’s decision in their
interactions.
Social post platforms are a different thing
A social post study also takes asocial_platform, and that is easy to confuse
with the gate. The platform decides how the post itself is drawn, as a native
Instagram, TikTok, Facebook, LinkedIn, X, or YouTube post, and it is what the
participant reacts to. Instagram and TikTok posts are always shown on mobile; the
others can be shown on mobile, desktop, or a mix.
The platform has no would-open rate of its own. If the gate is also on, the
participant first sees the square social card built from the caption and first
image, then the platform post if they open it. The CLI help and the MCP tool list
five platforms; youtube is accepted by the web app.
Related
Modalities
The media and text modalities the gate applies to.
Iterations
Where
content_config and the card live, one version at a time.Reactions and results
What openers report once they reach the content.