Selling Point
Use Selling Point to explain a benefit, argument, or value proposition in a compact block.
Content settingsβ
| Setting | What it controls |
|---|---|
| Title or benefit | Main selling point text. |
| Supporting text | Optional explanation or detail. |
| Icon or image | Visual support when available. |
Style settingsβ
| Style area | What you can adjust |
|---|---|
| Typography | Title and supporting text styles. |
| Visual | Icon/image size, color, background, and spacing. |
| Container | Background, border, radius, shadow, padding, and margin. |
| Layout | Alignment, gap, and responsive stacking. |
Best practicesβ
- Focus each Selling Point on one clear benefit.
- Use consistent icon and text styles across a benefit section.
- Keep supporting text short.
FAQβ
When should I use this page?
Use this page when you need a quick reference for this Atomicat feature and want to understand what it changes before editing or publishing. It is especially useful while reviewing a page, funnel, quiz, lead flow, product setup, video configuration, or account setting. For Selling Point, keep a short checklist of the fields you changed and test the result in the same browser session.
Do I need to configure this before publishing?
Configure it before publishing whenever the feature affects visitor behavior, tracking, SEO, forms, embeds, checkout, or access. If the feature only changes internal organization, review it before launch so your team can manage the campaign consistently. For Selling Point, keep a short checklist of the fields you changed and test the result in the same browser session.
Can this affect live pages?
Yes, some settings can affect live pages after saving or publishing. Always preview the page, test the main action, and confirm desktop and mobile behavior before sending paid traffic or sharing the URL. For Selling Point, keep a short checklist of the fields you changed and test the result in the same browser session.
What should I check if something looks wrong?
Check the page status, project access, saved revisions, browser cache, connected domain, and any related integrations. If the feature depends on a plan, permission, or enabled module, confirm that your workspace has access. For Selling Point, keep a short checklist of the fields you changed and test the result in the same browser session.