Edit your property settings

This is for:

Developer

In this article, we’ll show you how you can find and edit the basic property settings we define for you during onboarding.

How can I edit property settings?

  1. Select Settings from the side menu and then Edit in the Property card

  2. Edit your property settings as required and select Save to confirm

What settings can I change?

During your onboarding with Qubit, we will configure some basic settings for your property. Users with the role of Publisher or higher can edit these settings:

  • Name: This represents the name of your property, typically the name of the company or brand that’s collaborating with Qubit for personalization.

  • Preview links: This defines the default separator (? for querystring OR # for URL fragment) used in experience preview links:

    https://feature-playground.qutics.com/products/QB0001#qb_opts=preview,bypass_segments&qb_experiences=904898&qubit_explorer
    https://feature-playground.qutics.com/products/QB0001?qb_opts=preview,bypass_segments&qb_experiences=904898&qubit_explorer
  • Domains: This defines the domains that will be tracked for your property. Refer to the following guidelines:

    • Don’t include http:// or www

    • Try to use the most top level domain possible, e.g. .company.co.uk instead of .eshop.company.co.uk`

    • Use . in the front of the domain to indicate that all subdomains should be tracked, e.g. .company.co.uk

    • If you want to track subdomains individually, don’t use the dot, e.g. de.company.com,fr.company.com, company.com

  • Native jQuery: This option removes jQuery from your Smartserve script, thereby reducing its size by approximately 10-15%. This option is therefore well suited to clients looking for pageload performance improvements. Observe the following point:

    • If you’re using this option and any of your experiences are calling @qubit/jquery as a dependency, you must make sure jQuery is being loaded on your site. Failure to do so will likely cause experiences to generate JavaScript errors, which may affect the delivery of those experiences and the tracking of experience goals