Global configs

Intro

The Global Settings are used for website-wide configs which are not relevant to any specific section.

Right now we have 2 configs in place:

  • Default link for sign-up and signin
  • Analytics. Lifetime of the IP recognition
  • ABSmartly configs
  • Сontact form fields
  • Url analytics cookie configs
  • Script tag
  • Nlx nudge text

Link to the Global Configs in the CMS Admin Panel

Sign-up. Default link

The sign-up button in the header (top) menu is a hardcoded button with a specific logic. It does not link to only 1 URL. This config specifies to which DEFAULT URL the button should link in case the Geo-location services do not work or did not recognized a specific country. See the Sign-up links section in countries configurations

Signin default link

This config specifies to which URL the sign-in button in the header (top) menu should link.

Analytics. Lifetime of IP recognition

The internal analytics uses also the IP for the geo-location services, but it does not store it and this recognition expires after a life-span period. This period is configured in this global setting.

ABSmartly

A/B Smartly Configurations

The A/B Smartly configurations control various aspects of the A/B testing functionality integrated into the system. These configurations define specific experiments, environments, tracking, and other key settings used for running and analyzing experiments across the platform.

List of Configurations

  1. ab.uid_versioning

    • Description: Specifies the versioning for A/B Smartly UUIDs.
    • Current Value: v1
    • Purpose: Defines how user UUIDs are versioned for experiment tracking, ensuring consistency in identifying participants across experiments.
  2. ab.menu_experiment_menu

    • Description: The name of the menu experiment being run.
    • Current Value: example_experiment
    • Purpose: Sets the experiment name used for testing changes in the site’s menu structure or behavior.
  3. ab.chat_experiment_menu

    • Description: The name of the chat experiment being run.
    • Current Value: marketing_website_chatbot_signup
    • Purpose: Configures the chat experiment, particularly for A/B testing changes related to the chatbot’s behavior or signup process.
  4. ab.environment

    • Description: Defines the environment where the A/B experiments are executed.
    • Current Value: production
    • Purpose: Indicates that the current environment for running experiments is the production environment.
  5. ab.application

    • Description: Specifies the application name for which the A/B testing is being conducted.
    • Current Value: bcom
    • Purpose: Identifies the application (bcom) as the target for A/B testing experiments.
  6. ab.unit

    • Description: Defines the unit of experimentation used for tracking participants.
    • Current Value: anonymous_id
    • Purpose: Uses an anonymous_id as the unit for experiments, which helps in tracking users without requiring personally identifiable information (PII).
  7. ab.global_environment

    • Description: Specifies the global environment for the entire site.
    • Current Value: production
    • Purpose: Sets the global environment to production, ensuring that all experiments run in the same stable environment.
  8. ab.global_experiment

    • Description: The global experiment running across the entire site.
    • Current Value: obe_marketing_aa
    • Purpose: Configures a global experiment for site-wide testing, particularly for marketing-related initiatives.
  9. ab.track_sign_up_click

    • Description: Tracks the clicks on the sign-up button.
    • Current Value: marketing_page_register_button_click
    • Purpose: Tracks user interactions with the sign-up button on marketing pages, enabling analysis of user sign-up behavior.
  10. ab.track_sign_in_click

    • Description: Tracks the clicks on the sign-in button.
    • Current Value: marketing_page_signin_button_click
    • Purpose: Monitors user activity related to the sign-in button on marketing pages, providing insights into user login behavior.

Summary

These configurations allow for detailed A/B testing and tracking on different parts of the website. They manage the environments, specify the experiments, and track key user interactions such as sign-ups and logins. These settings ensure that experiments are correctly run, tracked, and analyzed in both production and testing environments.

Сontact form fields

The form configurations control the settings related to the contact form in the system. These configurations define the subject, recipient email addresses, and reply-to email for the contact form submissions, ensuring proper routing and handling of inquiries.

List of Configurations

  1. form.contact_subject

    • Description: Specifies the subject line for contact form submissions.
    • Current Value: Contact form B4B
    • Purpose: Sets the subject that will appear in the email when a user submits the contact form. This helps the recipient identify the context of the email at a glance.
  2. form.contact_email

    • Description: The email address where contact form submissions are sent.
    • Current Value: B4BbyMyCWT@mycwt.com
    • Purpose: Configures the email address that will receive all form submissions. This ensures that all inquiries from the contact form are sent to the correct recipient for handling.
  3. form.reply_email

    • Description: The reply-to email address for contact form responses.
    • Current Value: d.ghimpu@rminds.nl
    • Purpose: Specifies the email address that will be used in the CC.

Summary

These form configurations handle the essential aspects of the contact form’s email functionality, such as the subject line, recipient email, and reply-to address. Proper configuration ensures that inquiries are routed to the correct people and that responses can be efficiently managed.

Url analytics cookie

URL Analytics Cookie Configurations

The URL Analytics Cookie configurations are responsible for tracking and identifying existing users based on specific cookie values.

List of Configurations

  1. url_analytics.user_cookie_value

    • Description: The specific cookie value used to identify existing users for URL analytics purposes.
    • Current Value: 2c3b066d02fb0824fb972584d93fa4d7c75b4c21
    • Purpose: This configuration holds the encrypted value of a cookie that is used to recognize existing users when they revisit the site.
  2. url_analytics.user_cookie_name

    • Description: The name of the cookie used for identifying existing users in URL analytics.
    • Current Value: existing_users
    • Purpose: Defines the name of the cookie (existing_users) that is stored in the user's browser. This cookie helps the analytics system detect returning users and associate their actions with past interactions, improving the accuracy of user behavior tracking.

Script gtag

Script gtag

The Script gtag configurations used when CMS inserts value of this config on each page.

List of Configurations

  1. script.gtag
    • Description: Script value which will be inserted inside tag in the footer of the page.
    • Current Value: script value
    • Purpose: The script which you can insert can be gtag script - (Global Site Tag) is used to integrate Google Analytics, Google Ads, and other Google services into a website, allowing for the collection of data regarding user interactions, traffic sources, and conversions.

Nlx nudge text

Nlx Nudge Text Configuration

The Nlx Nudge Text configuration is responsible for setting the default text displayed in a nudge or prompt that encourages user interaction on the website. This nudge typically appears as a conversational prompt in chatbots or help systems, aiming to engage users and assist them in navigating or learning more about the site.

Configuration Details

  1. nlx.nudge_text
    • Description: The default text used in the nudge prompt to engage visitors.
    • Current Value: Welcome! What would you like to know \n\nabout Booking.com for Business?
    • Purpose: This configuration sets the initial greeting message shown to users in a nudge or chatbot interface. It encourages users to interact by asking what they would like to learn about the website. The use of "\n\n" in the value indicates line breaks for formatting the message across multiple lines, providing a friendly and inviting experience for users.

Summary

The Nlx Nudge Text configuration defines the initial interaction message for users, helping to guide them towards finding the information they need or engaging with the website’s features. It is a key part of improving user experience and encouraging engagement.