Search blocks by description or jump to a page.
A centered header above a comparison table weighing native apps, no code recipes, and the developer API, with the most popular column highlighted.
The source for every Marketing block is included with Pro and Team. Start a plan to copy the code.
Already on a plan? Log in
Connection Methods Table settles the how do we hook this up question with a straight comparison. A centered header states there are three ways to connect and frames when each one fits, then a bordered card holds a table whose columns are native apps, no code recipes, and the developer API. The native column is tinted and carries a most popular badge, and each column pairs a name with a one line tagline so the tradeoff is legible before the reader scans a single row.
The rows mix short text answers with check and minus glyphs for the yes or no cells, covering setup time, best fit, sync direction, field mapping, maintenance, and availability. Methods and rows are plain arrays and a small cell component decides between an icon and a string from the value type, so re-costing a row or adding a method is a data edit. A reassurance line under the table tells the undecided reader to start native and switch later without losing history.
Reach for this block when buyers reasonably ask which path is right for them and the honest answer is it depends. Laying the three routes side by side keeps the native app looking like the default while still crediting recipes and the API, so nobody feels steered. It suits platforms with a real developer story and works well on an integrations page once the catalog has established that the common tools are covered.
A natural flow around it on a Marketing Pro page:
Before
After
The obvious fit is native, recipes, and API. A few other ways to use the frame:
Tip: highlight exactly one column and pick the row order so the highlighted method wins most of the yes cells, the table should make a recommendation, not just present options.