embed and popup routes; the plain (non-embed) fill link does not read prefill params.
The field’s name is the internal machine name you see in Studio field settings — not its display label. Only scalar (string) values are accepted; anything else is ignored.
Reserved keys
These keys always control embed behavior and are never treated as field names, even if a field happens to share the name:Why doesn't prefill work on the plain fill link?
Why doesn't prefill work on the plain fill link?
Prefill-from-query only runs for the embed and popup routes (
isEmbed in the fill component). If you need prefill on a direct link, wrap it in a Standard embed instead.Does prefill work for choice/select fields?
Does prefill work for choice/select fields?
Yes, as long as the query value exactly matches one of the field’s option values.