Banner
Communicate information or drive action via in-line banners
About this component
The Banner
component is a versatile, persistent UI component that typically span the full width of a page or container, often at the top or bottom of the page. They serve as an unobtrusive way to communicate important information and promote additional offerings without disrupting the user’s workflow.
When to use Banners:
- Alerts: Ideal for notifying users about critical updates, such as free trial expirations or scheduled maintenance.
- Lightweight Up-sells: Effective for promoting related products or features, banners can be strategically targted and placed next to relevant content.
Advantages of Banners:
- Non-Disruptive Communication: Since banners remain visible without interrupting the user experience, they allow users to continue their tasks while still being informed.
- Flexible Design Options: Banners can be customized with full-bleed graphics and images, making them visually appealing and engaging. Frigade supports custom components including on-brand, eye-catching banners.
Best Practices for Banners:
- Use Collections: Leverage Collections to define reusable in-app UI channels, enabling teams to efficiently manage and launch banners across different pages, such as your product dashboard or a specific product pages.
- Regulate Frequency: Control the frequency of banner displays to ensure they remain relevant and engaging without overwhelming users.
- Make Dismissible: Most often, banners are easily dismissible for the best user expeirence. In select cases, banners may be non-dismissible to communicate a critical message for some time (e.g. product downtime).
Resources
- Launch banners with no-code using custom Collections
- Target your banner to specific users with Targeting
- See industry examples of banners
Demo
- See banners in action in our live demo
Installation
Customization
To learn about how to customize Frigade components, see the customization documentation and examples of custom themes in action.
SDK Properties
Optional component to wrap the child components in, e.g. as={Dialog}
will render the Flow in a modal Dialog. Defaults to Box
.
Whether to automatically mark the Flow started (i.e. in progress) when the Flow is eligible to be shown.
You will need to call flow.start()
or step.start()
from the parent component if you set this to false
. Most components should not need to override this behavior.
Defaults to true
.
Emotion CSS prop to apply to the component. See Theming documentation for more information.
Example usage:
Whether the Flow is dismissible or not
The Flow ID to render. You can find the Flow ID in the Frigade dashboard.
If true, the Flow will be mounted even if it has already been completed or dismissed. However, if the user does not match the Flow’s targeting, the Flow will not be mounted.
Register the Flow as a modal to prevent popup collisions (only one modal Flow will render at a time).
Handler for when the Flow is completed. This is event is fired immediately after the user completes the Flow.
Handler for when the Flow is dismissed (skipped). This is event is fired immediately after the user dismisses the Flow.
Handler for when primary button is clicked.
If this function returns false or a promise that resolves to false
, the step will not be automatically completed when clicked.
Handler for when secondary button is clicked.
If this function returns false or a promise that resolves to false
, the step will not be automatically completed when clicked.
Variables to pass to the Flow. You can use variables in the Flow configuration to customize copy.
For instance, you can use title: Hello, ${name}!
in the Flow configuration and pass variables={{name: 'John'}}
to customize the copy.
Optional component to wrap the child components in, e.g. as={Dialog}
will render the Flow in a modal Dialog. Defaults to Box
.
Whether to automatically mark the Flow started (i.e. in progress) when the Flow is eligible to be shown.
You will need to call flow.start()
or step.start()
from the parent component if you set this to false
. Most components should not need to override this behavior.
Defaults to true
.
Emotion CSS prop to apply to the component. See Theming documentation for more information.
Example usage:
Whether the Flow is dismissible or not
The Flow ID to render. You can find the Flow ID in the Frigade dashboard.
If true, the Flow will be mounted even if it has already been completed or dismissed. However, if the user does not match the Flow’s targeting, the Flow will not be mounted.
Register the Flow as a modal to prevent popup collisions (only one modal Flow will render at a time).
Handler for when the Flow is completed. This is event is fired immediately after the user completes the Flow.
Handler for when the Flow is dismissed (skipped). This is event is fired immediately after the user dismisses the Flow.
Handler for when primary button is clicked.
If this function returns false or a promise that resolves to false
, the step will not be automatically completed when clicked.
Handler for when secondary button is clicked.
If this function returns false or a promise that resolves to false
, the step will not be automatically completed when clicked.
Variables to pass to the Flow. You can use variables in the Flow configuration to customize copy.
For instance, you can use title: Hello, ${name}!
in the Flow configuration and pass variables={{name: 'John'}}
to customize the copy.
The steps to show in the tooltip tour.
Unique identifier for the step. Do not change this once the step has been created.
The title of the step
The description of the step
Url to an image to display in the step
Url to an icon to display in the step. This is only supported by the carousel checklist component.
Url to a video to display in the step such as YouTube, Vimeo, or a direct link to an mp4 file
Config for the primary button in this step.
Primary button action. (defaults to step.complete).
Possible values: false
, flow.back
, flow.complete
, flow.forward
, flow.restart
, flow.skip
, flow.start
, step.complete
, step.skip
, step.reset
, step.start
Primary button URI target (defaults to _self).
Primary button title. If omitted, the primary button will not be shown.
Primary button URI.
Deprecated: use primaryButton.title
instead. The title of the primary button
Deprecated: use primaryButton.uri
instead. The url to open when the primary button is clicked
Deprecated: use primaryButton.target
instead. The target of the primary button url (default: _blank; use _self to open in the same window). Setting it to # will open the existing page and dismiss any Frigade modals.
Config for the secondary button in this step.
Secondary button action. (defaults to step.complete).
Possible values: false
, flow.back
, flow.complete
, flow.forward
, flow.restart
, flow.skip
, flow.start
, step.complete
, step.skip
, step.reset
, step.start
Secondary button URI target (defaults to _self).
Secondary button title. If omitted, the secondary button will not be shown.
Secondary button URI.
Deprecated: use secondaryButton.title
instead. The title of the secondary button
Deprecated: use secondaryButton.uri
instead. The url to open when the secondary button is clicked
Deprecated: use secondaryButton.target
instead. The target of the secondary button url (default: _blank; use _self to open in the same window). Setting it to # will open the existing page and dismiss any Frigade modals.
Targeting that automatically completes the step. E.g.: user.property(‘connectedBank’) == true
Targeting that automatically blocks the step from starting until it becomes true. E.g.: user.property(‘connectedBank’) == true
Targeting that automatically shows the step when it becomes true. E.g.: user.property(‘connectedBank’) == true
Override the default UI props for the corresponding component