The draw query language is relational and structured in tables. This documentation is an overview of those tables. Fields are interpreted as a custom single table.

  • @consumers

    Contains all unique consumers which ever interacted in any way with the site. A consumer is only captured once and he will be identifier as long as he does not delete his cookies.

  • @experiments

    Contains all experiments created through the editor or the DuckProve user interface. To use the experiment table in a useful manner, it should be used together with the @sessions and field tables.

  • @experimenttags

    Contains all associated tags for each experiment. This is a table very often used with joins in generic custom reports in order to illustrate overall statistics.

  • @primary

    The primary is a virtual table which corresponds to the currently selected primary fields table. Field tables are automatically created and can be deleted at any time.

  • @sessions

    Contains all sessions created automatically by the consumers. A session is destroyed after the browser closes or the cookies are deleted.

  • @tags

    Contains all tags which are dynamically managed through the experiments description. A tag can be used to group experiments together.

  • @useragents

    The user agents table holds data of all kinds of user agents it knows about. Generally the view stores a relation to the user agent.

  • @views

    Contains all page views made on the website. A page view represents a single HTTP Request made to a site which has DuckProve installed.

  • Field Tables

    All fields are interpreted as custom tables. Those tables are called field tables and contain the goal data. Field tables are automatically created and can be deleted at any time.