Skip to content

Pre-fill Quote Options from URLs

You can pre-fill quote page customizations (sliders, switches, toggles) via URL parameters. This is useful for marketing campaigns, email links, and partner referrals where you want users to land on a quote page with specific coverage options already selected.

  • A published quote page in Strapi with quote options configured
  • Knowledge of the questionId for each quote option you want to pre-fill

1. Enable URL pre-filling on the quote page

Section titled “1. Enable URL pre-filling on the quote page”

In Strapi, open your quote page entry and set prefillQuoteOptionsFromParams to true.

This field is a boolean on the quote-page content type, defaulting to false.

URL parameter names must exactly match the questionId of each quote option (slider, switch, or toggle) you want to pre-fill.

Example:

https://app.feather-insurance.com/policies/household/de?coverageAmount=50000&glassProtection=true
Parameter Maps to Value
coverageAmount Slider with questionId: "coverageAmount" Numeric value within the slider range
glassProtection Switch with questionId: "glassProtection" true or false

3. Combine with mergeQuoteOptionsToQuestionnaire

Section titled “3. Combine with mergeQuoteOptionsToQuestionnaire”

If you also set mergeQuoteOptionsToQuestionnaire to true on the quote page, pre-filled quote option values become available as questionnaire answers. This lets rules and calculated fields reference them.

Field Default Purpose
prefillQuoteOptionsFromParams false Accept URL params to pre-select quote options
mergeQuoteOptionsToQuestionnaire false Make quote option values available as questionnaire answers for rules
  • Marketing campaigns: Email links with recommended coverage pre-selected
  • Partner referrals: Affiliate links with specific plan configurations
  • Customer support: Agents can send links with the exact coverage discussed
  1. Navigate to the quote page URL with parameters appended
  2. Verify that sliders, switches, and toggles reflect the URL values
  3. Confirm that invalid values (out of range, wrong type) are handled gracefully — the app falls back to defaults