Table of Contents

Landbot System Fields: Pre-created fields

Anna P Updated by Anna P

Landbot automatically saves information collected during a chat without the need to ask users for it. These pieces of information are called System fields โ€” and you can use them anytime in your flow to personalize the conversation or analyze results later.

You can learn more about custom Fields in Landbot in our Guide.

Let's discover now what kind of fields are available on Landbot!

โญ Lead Data Fields: Ready to use

These fields can be filled with questions set in your flow, you'll find the pre-created and empty to be filled (except for ID):

  1. ID [Number]: By default, it's a unique id number set up by the system automatically. (example: ย 8029448); This field can be used to identify each user's session, and will depend of your Second visit settings.
Note: it will keep the same ID number if you have set the bot's Second visit settings to Always continue the conversation or Provide Buttons to start again or continue
  1. Name [String]: By default it's the #Visitor & the id fields (example: Visitor #8029448); You can use it in your Ask for a Name block to save your visitor's real name.
  2. Email [String]: empty by default; Use in Ask for an email block to save an email address
  3. Company [String]: empty by default; Use Ask a question block to request this info from your user.
  4. Phone [String]: empty by default; Use a Question: Phone block to fill in this info.

Usage Details Fields

  1. Chat transcription[String]: Chat transcript of the user's responses throughout your bot flow. This can be used for tracking purposes. More info here.
  2. Last seen [Date]: Last time this visitor interacted with the bot (YYYY-MM-DD).
  3. Created [Date]: When the visitor ID was created (YYYY-MM-DD).
  4. Url [String]: Share url of your bot. (example: https://landbot.io/u/H-145130-Z1WUCM98QR4Y2LA7/index.html);
  5. Browser [String]: Filled if detected - Browser your users is on.
  6. Device [String]: Filled if detected - Device your user in on.
  7. OS [String]: Filled if detected - Operative system from your user's device. (Mac, IOS, Windows, etc)
  8. Country [String]: If detected (example: Italy).

๐Ÿ”’Time Reference Fields

Dates are based on Central European Time / European Central Timeย (Standard Time) CET.

  1. Yesterday [Date]: format YYYY-MM-DD
  2. Today [Date]: format YYYY-MM-DD
  3. Tomorrow [Date]: format YYYY-MM-DD
Time reference fields cannot be overwritten in Landbot.
System fields will be displayed in production after the first block. If they're added in the first block they will not be displayed (even though they contain value)

๐Ÿ“Š Display system fields data in your analytics:

You'll notice some usage and date fields do not appear automatically in your Analyze section. For this you'll need to set the field in your flow.

Here's how to do it. Let's say we want to to store the Chat transcript to review later:

1. Create a custom field (new field) with the same name as the system variable you want to store, in this case we'll use @chat_transcription:

Once created, we move to the Value box below, and look up our system variable Chat transcription - select it:

Your set a field block should look like this:

Once published and tested, you should see your system variable in your analytics like so:

๐Ÿ“ฑPlatform-Specific Field Behavior

๐ŸŒ Web Bots:

Collected by default:

  • @country
  • @browser
  • @device
  • @os

Time fields @yesterday, @today, @tomorrow also available.

  • ๐Ÿ’ฌ For WhatsApp:
    Collected automatically after the user interacts with your WhatsApp channel:
    • @name โ†’ The name the user has set in WhatsApp (not necessarily their real name)
    • @phone -> Phone number your user's reaching out from.
    Not collected by default:
    • @browser
    • @device
    • @os
๐Ÿ’™ For Facebook Messenger
  • The fields @name, @phone, @browser, @device, and @os will not be collected by default. You'll need to ask for them using our relative blocks. (Ask for a name, Phone block, Question blocks)

Extra information for WhatsApp and Facebook Messenger bots

You can capture and use the first user's interaction (input) in WhatsApp/ Facebook Messenger by adding Collect Intent block after the Starting point in your flow:

By doing this, you will store the first message sent by the user, which will be available in the field @user_input in case you need to access or use it later.

You can find more information in this article.

Was this article helpful?

Set a Field block

Contact