Brand and widget themes
Style collection surfaces with brand settings, widget options and separate light and dark colors.
Brand styling and widget configuration are related but distinct. A brand provides an identity for forms and the workspace. A widget's generated installation options determine how that widget looks on its host page.
Set up a brand identity
Open the brand editor to configure its name, logo, colors, font and corner style. Save the brand before testing the resulting public form. Brand extraction can suggest settings from a website URL; review the proposed logo, colors and font before applying them.
Extracted settings are a starting point. Check text contrast, button labels, long question text and the way the form looks on a small screen. A successful extraction does not establish that every color combination is readable.
Feedback Pages use brand appearance, and the editor also exposes form presentation settings. For a form shared across brands, review the preview from the intended brand context before sharing it; workspace sharing and public presentation should both match your intention.
Customize a widget
Use the widget builder to preview a configuration and copy its installation code. Common options include the rating type, prompt, position, light/dark theme, primary color, background, text, borders, button text and success message.
For the script widget, pass options as data attributes:
<script
src="https://pollenate.dev/widget.js"
data-api-key="YOUR_COLLECT_ONLY_ORGANIZATION_KEY"
data-inbox-key="product-feedback"
data-type="stars"
data-theme="auto"
data-primary-color="#7c3aed"
data-dark-primary-color="#c4b5fd"
data-prompt="How was this experience?"
data-button-text="Send feedback"
defer
></script>auto follows the system theme preference. Check both appearances and use the dark-specific color options when the light palette does not work on a dark background. The script also supports inline placement, trigger text, animation choices, logo and brand-name options; copy the builder's configuration for the presentation you previewed.
The React package accepts corresponding component props for its supported options. Use the React guide rather than copying HTML data attributes into a component's props.
Verify changes on the installed page
Changes in a builder preview do not replace code already deployed on your website. Update the installed snippet or React props, then reload the page and submit a test response. If the appearance differs, inspect the options actually present in the page and check for old cached application assets.
Keep credentials out of screenshots and examples. Browser widgets should use a collection-scoped organization key, not an administrative key. See Widget installation for the complete setup.