ConveYour for Developers

For: Builders integrating with ConveYour, agencies customizing programs, and anyone who wants real merge logic—not a shallow “first name only” mail merge.

ConveYour uses Liquid (the same family of syntax popularized by Shopify and many CMSs) almost anywhere we personalize a contact’s experience: SMS, email, lesson content, automations, smart links, and more. One mental model, many surfaces.

Why this should excite you

• Logic + data, not just tokens — Conditionals, filters, defaults, and composable snippets—not a fixed mail-merge grid.
• Composable content — Pull in shared blocks, nest them, and keep long programs maintainable.
• Scheduling-aware — Booking and reschedule links can surface directly in copy when someone has an appointment on file.
• Integration-friendly — Pass your own structured data into templates when you compile content via the API so your stack and ConveYour share one language.

Basics: contact fields

Job to be done: Greet someone by name, branch on whether a field exists, or fall back gracefully.

Where you’ll use it: SMS bodies, email bodies and subjects, lesson text, form acknowledgements, campaign messages—anywhere merge tags are supported.

Hi {{ contact.first_name | default: "there" }},

{{ contact.email }}

Many org-defined fields are available on contact (and often at the root of the template too, so first_name and contact.first_name can both work—handy when you’re migrating old copy).

SMS: short, sharp personalization

Job to be done: Send a punchy text that still feels 1:1.

Where: SMS campaigns, automated SMS steps, alerts.