Publication defining and sections defining

This document refers to data visible in gem files (ad campaings planning tool - gemiusExplorer application)

General rules of Publication defining

  • Publication is defined according to Look & feel rules - technically as a set of domains/URL masks.

    Eg a imaginary publication sample.com can be defined as a group of two domains:
    sample.com (domain/positive); mysample.com (domain/positive)

  • Definition of publications is done by Gemius. Publisher receives a information of used definitions while receiving xls file with data preview (usually in the middle of the month) and can direct his comments to Gemius.

  • As default the publication is defined as one node (without division into any sections).

  • There is a possibility to divide the publication into sections in one of the two following ways:
    1. in private gem files that are provided to the given publisher only.
      Definitions of sections should be done by publisher and provided to Gemius (at any time).

    2. in official gem files that are provided to the market - in such case all market players, who is granted with valid licences, have access to data about those sections. All official files are available for downloading from the "result page".
      Definitions of sections should be done by publisher and provided to Gemius by 5th of the next month (it means that sections for using in January file should be provided by 5th February).
      First vawe is always made in "private gem" files, in next vawes sections start to be visible in "official gem" files.

Sections defining rules

    Rules for sections defining:

  • Sections/subsections (called: nodes) are defined as a set of domains/URL masks.

  • All nodes should have the url masks defined in such a way that the url of page view would fit to one node only (!).

  • Folder doesn't have it's own URL definition - it is always the summ of its "child" nodes ("leaves" from the tree).
    the only exceptin is the root of the publication which always has a deffinition according to the official definition of that publication

  • Unlimited number of masks can be defined for each "leave" node.

  • Definition of masks should be provided to Gemius in xls file. The definitions are revised by Gemius and, if changes are necessary, Gemius sent back it to client with comments.

URL masks types

All masks are case-insensitive.

There are some kinds of masks that can be used for tee defining:

  • domain mask - the most basic and commonly used type of mask. URL addresses, which contains series of marks defined by pattern. This should be contained part from domain of URL and (optional) part of catalogue of URL. If the type of mask is not given - it is a DOMAIN type as default.
    Masks should be defined without inscription "http://'".

    Example:

    • Mask "sample.dk/a" DOMAIN fits to the following example URLs:

      http://sample.dk/a/
      http://www.sample.dk/a
      http://something.sample.dk/a/
      http://www.sample.dk/a/b/c.html
      http://lola@sample.dk/a?id=234

      does not fit to:
      http://mysample.dk/a
      http://sample.dk/
      http://sample.dk/ab
      http://sample.dk/b/a

    • Mask "sample.dk/index.php" DOMAIN fit to the following example URLs:

      http://sample.dk/index.php
      http://www.sample.dk/index.php
      http://something.sample.dk/index.php?par=value
      http://www.sample.dk/index.php&ala=ma_kota
      http://sample.dk/index.php/ala
      http://lola@sample.dk/index.php?ola=ma_psa

      does not fit to:
      http://mojsample.dk/index.php
      http://sample.dk/

  • exactly mask - URL address (following 'http://') have to be excactly the same as given pattern (masks); parameters are allowed (if masks doesn't finish with $).

    This type of mask is used for defining of a node "Forside" (Main page) which usually consists of a few strictly defined URLs.

    Example:

    • Mask "sample.dk/index.php" EXACTLY fits to adresses:

      http://sample.dk/index.php
      http://something@sample.dk/index.php
      http://sample.dk/index.php?a=127

      does not match (fit) to:
      http://www.sample.dk/index.php

    • Mask "sample.dk/index.php$" EXACTLY fits to adresses:

      http://sample.dk/index.php
      http://something@sample.dk/index.php

      does not match (fit) to:
      http://sample.dk/index.php?a=127
      http://www.sample.dk/index.php

    Note:

    • while defining "Forside" make sure that you define all necessary URLs (and include sample.dk and www.sample.dk)
    • $ at the end of EXACTLY masks means that can not be any string (any parameter) after the given url template.

  • asterics and optionally #
    • Mask "sample.dk/serwis.php*i=245" DOMAIN fits to adresses:

      http://www.sample.dk/serwis.php?i=245
      http://www.sample.dk/serwis.php?a=2&i=245
      http://www.sample.dk/serwis.php?mi=245
      http://www.sample.dk/serwis.php?mi=245&a=23
      http://www.sample.dk/serwis.php?mi=2456
      http://www.sample.dk/serwis.php?i=2456&b=2

      does not match (fit) to:
      http://www.sample.dk
      http://ala@www.sample.dk/serwis.php
      http://www.sample.dk/serwis.php4?i=245
      http://www.sample.dk/section/serwis.php?i=245

    • Mask "sample.dk/serwis.php*i=245#" DOMAIN fits to adresses:

      http://www.sample.dk/serwis.php?i=245
      http://www.sample.dk/serwis.php?a=2&i=245
      http://www.sample.dk/serwis.php?mi=245
      http://www.sample.dk/serwis.php/something?mi=245

      does not match (fit) to:
      http://www.sample.dk
      http://ala@www.sample.dk/serwis.php
      http://www.sample.dk/serwis.php4?i=245
      http://www.sample.dk/serwis.php?mi=245&a=23
      http://www.sample.dk/serwis.php?mi=2456
      http://www.sample.dk/serwis.php?i=2456&b=2
      http://www.sample.dk/section/serwis.php?i=245

      Notes: If one of node has definition eg.: sample.dk/*/sport and the second node is defined as sample.dk/*/auto, then URL http://sample.dk/sport/auto/ fits to both nodes and the tree is not then defined correctly. Negtive masks should be used then.

  • positive or negative masks

    Example of usage:

    sample.com def: sample.com
      |
      |_section_A def: sample.com/a
      |_section_b def: sample.com/b
      |_others def: sample.com; !sample.com/a (negative); !sample.com/b (negative)

In case of any questions - please contact us by email audience-dk@gemius.com

back to the main page