Skip to main content
Cta renders a full-width band containing a single headline and a single button. This page explains the props, the available variant, and the patterns Cta supports — post-content conversion, sticky band, end-of-flow. The block is intentionally minimal — one message, one action — designed to capture attention at peak reader interest. Reach for it after a FeaturesGrid or another content section to convert readers ready to act, or as a sticky conversion band at the bottom of long pages.

​
Example

cta.json
{
  "block": "Cta",
  "props": {
    "headline": "Ready to start?",
    "cta_label": "Get started",
    "cta_href": "/signup",
    "variant": "centered"
  }
}

​
Props

The source enumerates "centered" as the only explicit variant. Other values may exist in your runtime — fetch the authoritative enum via the Builder MCP get_block_schema tool.

​
Patterns

Post-content conversion. Place Cta directly after the last content section and before the Footer — readers have absorbed the value proposition and are at peak engagement. Sticky bottom band. On long pages, combine Cta with the visible_if common prop so the band appears only after the user has scrolled past the Hero. This keeps the top of the page uncluttered without losing the conversion surface. End-of-flow. Use Cta as the terminal block on quickstart and onboarding pages — one clear next action, no competing links.

​
Common props

In addition to the Cta-specific props, every block accepts id, class_overrides, visible_if, and analytics_event. See common props on the PageBlocks overview.

​
Where to go next