KWIGA help center Services, integrations, API, Settings General setting Using variables on the project, list of available variables

Using variables on the project, list of available variables

Articles:

3 months ago • Updated

This article explains how to use variables in your project—where to apply them, what data is available, and how to use them for automation and personalization. Includes a list with descriptions and examples for emails, webhooks, buttons, lessons, and more.

General information about variables

Variables are a convenient way to insert personalized data into various elements of your project. They can be used in places like:

1. Webhooks in automations

Variables can be inserted:

in the webhook URL, for example:
https://example.com/hook?user={user.email}
in the request body parameters
in the headers

This allows personal data to be automatically sent to third-party services.

2. CTA (Call to Action)

In buttons and links, variables can be used for:

personalizing button text
passing data through links, such as user ID or UTM tags

3. In parameters

Variables can be used in form parameters or other elements:

user email
subscription ID
unique codes and tags
any other variable available in the context

4. In redirect link (if not using payment transition)

Variables can be manually added to the redirect link:

https://my.site.com/thanks?email={user.email}&course={course.title}

5. In lesson info blocks

Variables work within the texts of info blocks. For example:

Addressing by name: Hi, {user.first_name}!
Displaying course name, date, status, etc.

6. In emails

Using variables in emails makes communication more personalized and effective. With variables like {name}, {date}, or {course name}, the email appears personally addressed to the client. This increases trust, engagement, and the likelihood that the user will read the email to the end or take the desired action. Additionally, variables simplify the automation of mass mailings without losing a personal touch.

7. In notifications

When setting up notifications in automation actions, variables allow you to dynamically insert information into notifications, such as the username, order number, or offer name. This simplifies and speeds up the notification creation process, making them more intuitive and adaptable for different scenarios.

List of available variables

List of available variables that are accessible in all places where variables can be used.

Variable	Value
contact.id	Contact ID
contact.user_id	User ID
contact.first_name	Contact name
contact.last_name	Contact surname
contact.middle_name	Middle name of contact
contact.name	Contact full name
contact.email	Contact email
contact.phone	Contact phone
contact.country	Contact country. For example: Ukraine
contact.timezone	Contact timezone. For example: Europe/Kyiv
contact.currency	Contact currency. For example: USD
contact.city	Contact city
contact.utm_source	List of unique contact utm_source (separator ", ")
contact.utm_medium	List of unique utm_medium of the contact (delimiter ", ")
contact.utm_campaign	List of unique utm_campaign of the contact (delimiter ", ")
contact.utm_term	List of unique utm_term of the contact (delimiter ", ")
contact.utm_content	List of unique utm_content of the contact (delimiter ", ")
contact.field_<id>	Custom fields (description below)
datetime	Date and time in UTC format YYYY-MM-DD HH:mm:ss
contact.visit_source	Visit source

Custom fields

{contact.field_<id>}

Example {contact.field_123}

<id> - field ID, which can be obtained in the contact field settings (example https://sampleschool.kwiga.com/expert/crm/contacts?view=settings)

Custom fields example

Variables that can be additionally used in CTA

in parameters
in redirect link (if not using payment transition)

Variable	Value
first_name	First name from application
last_name	Last name from application
middle_name	Middle name from the application
name	Full name from application
email	Email from application
phone	Phone from application
field_<id>	Custom fields Phone from the application (description below)
utm_source	utm_source - specifically from the visit where the application was submitted
utm_medium	utm_medium - specifically from the visit where the application was submitted
utm_campaign	utm_campaign - specifically from the visit where the application was submitted
utm_term	utm_term - specifically from the visit where the application was submitted
utm_content	utm_content - specifically from the visit where the application was submitted
widget_landing	Landing page URL from which the application was sent
widget_landign_referer	Referrer that was on the landing page when the application was sent
Also, in certain forms, variables described below in Variables available in automation webhooks may be accessible By order ({order.}) - If the Access to product (Full access/By offer) form option is selected By product({product.}) - If the Access to product + Full access form option is selected By offer ({offer.*}) - If the Access to product + By offer form option is selected

Custom fields

{field_<id>}

Example {contact.field_123}

<id> - field ID, which can be obtained in the contact field settings (example https://sampleschool.kwiga.com/expert/crm/contacts?view=settings)

Custom fields example

If on the page where the CTA or Kwiga tracking script is placed, there were visits with utm tags, and the client submitted a request on the landing page without utm tags, they will be absent in these variables. But they will be available in the variables {contact.utm_...}, which are described above.

Variables available in automation webhooks (url, parameters, emails)