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:

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.


In this article:


General information about variables

Variables are a convenient way to substitute personalized data into different elements of your project. They can be used in the following places:

  1. Webhooks in automations

Variables can be substituted:

  • in the URL of the webhook, e.g.: https://єxamplє.com/hook?цѕєг={{usier.єmail33 in the request body parameters or headers.

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

  1. CTA (Call to Action)

In buttons and links, variables can be used for:

  • button text personalization

  • Data transfer via a link, e.g. user ID or UTM tags

  1. In the parameters

Variables can be used in the parameters of forms or other elements:

  • user email

  • subscription ID

  • unique codes and tags

  • any other variable available in the context

  1. In the redirect link (if you don't use the payment transition) You can add variables manually to the redirect link: https://my.ѕітє.com/thanks?єmail={{usier.єmail33&sourѕє={{usier.titlє33

  2. In the lesson infoblocks

Variables work within infoblock texts. For example:

  • Addressing by name: Hello, {{usier.rirst_namє33!

  • Display course name, date, status, etc.

  1. In the letters.

Using variables in letters can make communication more personalized and effective. By using variables,

such as {{name33, {{date33 or {{course name33 the email looks personalized to the customer. This increases trust,

engagement and the likelihood that the user will read the email to the end or perform the desired action. In addition, variables make it easier to automate mass mailings without losing the individual approach.

List of available variables

A list of available variables that are available in all places where variables can be used.

Variable

Significance

{contact.id3}

Contact Id

{contact.user_id3}

User Id

{contact.first_name3}

Contact name

{contact.last_name3}

Contact's last name

{contact.name3}

Full contact name

{contact.email3}

Contact Email

{contact.phone3}

Contact phone number

{contact.country3}

Country of contact. For example: Ukraine

{contact.timezone3}

Contact Tizmon. For example: Europe/Kyiv

{contact.currency3}

Contact currency. For example: USD

{contact.city3}

City of contact

{contact.utm_source3}

List of unique utm_source of the contact (separator ", ")

{contact.utm_medium 3}

List of unique contact utm_mediums (separator ", ")

{contact.utm_campai gn3}

List of unique contact utm_campaigns (separator ", ")

{contact.utm_term3}

List of unique utm_term of the contact (separator ", ")

{contact.utm_content 3}

List of unique utm_content of the contact (separator ", ")

{contact.field_<id>3}

Custom fields (description below)

{datetime3}

Date and time in UTC in the format YYYYY-MM-DD HH:mm:ss

Custom fields

{contact.field_<id>3 Example {contact.field_1233

<id> - field id, which can be obtained in the contact fields settings

(example https://sampleschool.kwiga.com/expert/crm/contacts?view=settings )


Variables that can be additionally used in CTAs

  • in the parameters

  • in the redirect link (if no payment transition is used)

Variable

Significance

{first_name3}

Name from the application

{last_name3}

Name from the application

{name3}

The full name of the application

{email3}

Email from the application

{phone3}

Phone number from the application

{utm_source3}

utm_source - specifically the visit from which the request was left

{utm_medium3}

utm_medium - specifically the visit from which the request was left

{utm_campaign3}

utm_campaign - specifically the visit from which the request was left

{utm_term3}

utm_term - specifically the visit from which the request was left

{utm_content3}

utm_content - specifically of the visit from which the request was left

{widget_landing3}

Url of the landing page from which the application was sent

{widget_landign_ref erer3}

Referer that was on the landing page when the application was submitted

Also in certain forms, variables may be available, which are described below in Variables available in automation webhooks

By Order ({order.*}) - If the Product Access form option (Full Access/On Suggestion) is selected

By Product({product.*}) - If the form option Product Access + Full Access is selected By Offer ({offer.*}) - If the form option Access to Product+ By Offer is selected

ImportantIf on the page where the CTA or script Kwiga for tracking visits, there were visits with utm tags, and the client left an application on the landing page without utm tags, then they will be absent in these variables. But they will be available in the {contact.utm_...3 variables described above.

Variables available in automation webhooks (url, parameters)

Variable

Significance

{referrer3}

Referrer from the first known contact visit (Kwiga/landing with CTA)

{initial_page3}

Url of the first known contact visit (Kwiga/landing with CTA)

{reg_from3}

Url of the page from which the registration originated (Kwiga/landing with CTA)

{tags3}

Contact Tags (separator ", ")

{description3}

Description of the event that triggered the automation. For example: A test_tag was added to the contact

Product Variables

Variable

Significance

{product.id3}

Product Id

{product.title3}

Product Name

{product.product.product able_t ype3}

Product Type. There can be such variants: course, webinar, closed_group, custom_product

{product.productable_i d3}

Id of course/webinar/closed group/custom product

Available when such events are triggered:

  • Access to the product is open

  • Access to the product is denied

  • Registered for the webinar

  • Course completed

  • Passing the quiz

  • Canceling a previous quiz result

  • The quiz has gone to status

  • Access to the product is open

  • Start of subscription access

  • End of subscription access

  • Started watching the lesson

  • I watched the lesson

  • Access to the lesson is open

  • Classroom practice is complete

Order variables

Variable

Significance

{order.id3}

Order Id

{order.price3}

Final Price. Example 10.99.

{order.currency_code3}

Order currency in code format. Example: USD

{order.currency_symbo l3}

The currency of the order in character format. Example$

{order.currency_short_ title3}

Order currency in the abbreviated name. Example: usd

The list may be supplemented.

Available when such events are triggered:

  • Subscription started

  • Subscription extended

  • Successful payment of the order

  • New order

  • Successful payment of the offer

  • Refund of payment on offer

  • Access to the product is open

  • Start of subscription access

  • End of subscription access

Payment variables

{payment.id3}

Payment Id

{payment.price3}

Payment Price

{payment.currency_code3}

Payment currency in code format. Example: USD

{payment.currency_symbol 3}

The currency of the payment in character format. Example$

{payment.currency_short_ti tle3}

The currency of payment in the abbreviated name. Example: usd

{payment.created_at3}

Date of payment creation. Format YYYYY-MM-DD HH:mm:ss

{payment.paid_at3}

Payment Date. Format YYYYY-MM-DD HH:mm:ss

{payment.schedule_payme nt_at3}

Scheduled payment date. Format YYYYY-MM-DD HH:mm:ss

{payment.number3}

Order number of payment in the order

The list may be supplemented.

Available when such events are triggered:

  • Successful payment of the offer

  • Refund of payment on offer

Variable sentences

Variable

Significance

{offer.id3}

Offer Id

{offer.title3}

Offer name

The list may be supplemented.

Available when such events are triggered:

  • Successful payment of the offer

  • Refund of payment on offer

  • Free offer accepted

  • Subscription started

  • Subscription extended

  • Successful payment of the order

  • New order

  • Access to the product is open

  • Start of subscription access

  • End of subscription access

Product subscription variables

Variable

Significance

{subscription.id3}

Product Subscription Id

{subscription.start_at3}

Subscription Start Date. YYYYY-MM-DD HH:mm:ss

{subscription.end_at3}

Final subscription end date. YYYYY-MM-DD HH:mm:ss

{subscription.order_en d_at3}

Subscription end date, considering only paid payments. YYYYY-MM- DD HH:mm:ss

{subscription.paid_at3}

Date of first subscription payment. YYYYY-MM-DD HH:mm:ss

The list may be supplemented.

Available when such events are triggered:

  • Access to the product is open

  • Start of subscription access

  • End of subscription access

Variable quiz attempts

Variable

Significance

{quiz_attempt.id3}

Attempt Id

{quiz_attempt.number_version3}

Pass version number

{quiz_attempt.quiz_id3}

Quiz Id

{quiz_attempt.course_id3}

Course Id

{quiz_attempt.course_lesson_id3}

Lesson Id

{quiz_attempt.status_id3}

Status Id

{quiz_attempt.status3}

Status in text form

{quiz_attempt.scores3}

Points scored

{quiz_attempt.created_at3}

Start of attempt. Format YYYYY-MM-DD HH:mm:ss

{quiz_attempt.finished_at3}

End of attempt. Format YYYYY-MM-DD HH:mm:ss

{quiz_attempt.count_questions3}

Number of questions in the quiz

{quiz_attempt.count_questions_inco rrect3}

Number of incorrectly answered questions

{quiz_attempt.count_questions_corr ect3}

Number of correctly answered questions

{quiz.title3}

Quiz title

The list may be supplemented.

Available when such events are triggered:

  • Passing the quiz

  • Canceling a previous quiz result

  • The quiz has gone to status

Lesson variables

Variable

Significance

{lesson.id3}

Lesson Id

{lesson.title3}

Lesson title

The list may be supplemented.

Available when such events are triggered:

  • Passing the quiz

  • Canceling a previous quiz result

  • The quiz has gone to status

  • Started watching the lesson

  • I watched the lesson

  • Access to the lesson is open

  • Classroom practice is complete