Using Variables
Requires Pro Plus or higher
Variables make it possible to incorporate dynamic content into a site's text, link URLs, form values and more. A variable is generally made up of a name and an optional fallback value:
{{name|fallback}}
The name
portion of the variable is the unique name associated with the content (or value) you're trying to include, while the fallback
portion is an optional fallback in case the value is blank or the variable doesn't exist. For example, the variable {{url.name}}
in the following line of text:
Welcome, {{url.first_name}}!
... will be expanded to the value of url.first_name
, which in this case is the first_name
URL parameter:
Welcome, Cayce!
Similarly the variable {{url.first_name|friend}}
will also be expanded to the contents of the first_name
URL parameter, but if it's blank or doesn't exist it'll instead be expanded to the fallback value friend
:
Welcome, friend!
Supported Variables
Below is a list of all variables currently supported by Carrd. Variables with a Global scope can be used anywhere variables are supported. All other variables can only be used within their defined scopes.
{{email}}
, {{form01.email}}
, or {{form01_response.confirmation_id}}
will only expand after the user has submitted that specific form.Scope | Variable | Description |
---|---|---|
Global | {{url.parameter_name}} | Contents of the |
Global | {{client.date}} | Client's local date in numeric format (eg. |
Global | {{client.time}} | Client's local time in HH:MM format (eg. |
Global | {{client.fulldate}} | Client's local date in string format (eg. |
Global | {{client.fulltime}} | Client's local time in HH:MM:SS format (eg. |
Global | {{client.timestamp}} | Alias of client.utc_timestamp. |
Global | {{client.utc_date}} | UTC date in numeric format (eg. |
Global | {{client.utc_time}} | UTC time in HH:MM format (eg. |
Global | {{client.utc_fulldate}} | UTC date in string format (eg. |
Global | {{client.utc_fulltime}} | UTC time in HH:MM:SS format (eg. |
Global | {{client.utc_timestamp}} | UTC time as a Unix timestamp (eg. |
Global | {{form.fieldId}} | Expands to the value of the last submitted form's |
Global | {{form_response.key}} | Expands to the value of |
Global | {{formId.fieldId}} | Expands to the value of |
Global | {{formId_response.key}} | Expands to the value of |
Contact Form | {{name}} | Value of this form's Name field. |
Contact Form | {{email}} | Value of this form's Email field. |
Contact Form | {{message}} | Value of this form's Message field. |
Contact Form | {{company}} | Value of this form's Company Name field. |
Contact Form | {{phone}} | Value of this form's Phone Number field. |
Contact Form | {{subject}} | Value of this form's Subject field. |
Contact Form | {{consent}} | Value of this form's Require Consent field. |
Signup Form | {{email}} | Value of this form's Email field. |
Signup Form | {{fname}} | Value of this form's First Name field (or Name field if using a single name field). |
Signup Form | {{lname}} | Value of this form's Last Name field. |
Signup Form | {{company}} | Value of this form's Company Name field. |
Signup Form | {{phone}} | Value of this form's Phone Number field. |
Signup Form | {{consent}} | Value of this form's Require Consent field. |
Custom Form | {{fieldId}} | Value of this form's |
Supported Elements
Variables are currently supported by the following elements:
Element Type | Where |
---|---|
Buttons |
|
Embed |
|
Form |
|
Gallery |
|
Icons |
|
Image |
|
Links |
|
List |
|
Table |
|
Text |
|