Was this page helpful?

Custom dims: auto-feed

    The custom dimension value declaration

    Custom dimensions values are used to compute averages in the OLAP Model.

    By default, each value has to be declared manually in order to trigger this calculation. However, in a dynamic context (user Ids, etc.), it may become useful to auto-declare those values.

    Attention: This mechanism has to be agreed with your iplabel sales representative before any implementation.

    Auto feed

    The auto-feed mechanism allows the automatic update of custom dimensions every time a new one is beng added.

    The custom dimension using auto-feed feature should conform to the following syntax:

    @_@childcustom
    or
    parentcustom@_@childcustom
    or
    
    parentcustom@_@childcustom@_@grandchildcustom
    

    Reminder: childcustom and grandchild must be unique. In cases where unicity cannot be garanted, it is recommended to repeat the content of the parent token in the child. Here is how this would be applied in the context of the chapter 1.2.5 example:

    "S2@_@S2.V1"
    

    Usage

    A total of 5 custom dimensions are available: custom (deprecated), ABTesting, Business, Customer, Infrastructure. They can be called by using the following variables:

    Custom dimension name Matching javascript variable Usage suggestion
    Custom iplcustomdim (deprecated)  
    Business rumbiConf.business Business line/department
    A/B Testing rumbiConf.abtesting Application version number
    Infrastructure rumbiConf.infrastructure Type of plateform (prod, dev, test...)
    Customers rumbiConf.customer  

    Implementation example with 5 custom dims:

    <script type="text/javascript">
    var iplobserverstart = new Date();
    
    rumbiConf.business = 'ParentBusiness1@_@ParentBusiness1.ChildBusiness1';
    rumbiConf.abtesting = 'ParentVersion1@_@ParentVersion1.ChildVersion1';
    rumbiConf.infrastructure = 'ParentInfrastructure1@_@ParentInfrastructure1.ChildInfrastructure1';
    rumbiConf.customer = 'ParentCustomer1@_@ParentCustomer1.ChildCustomer1';
    </script>
    

    The actual content of the variable are up to you. You can you one, two or three levels. The two constrains are to use @_@ as seperator and to have unique child and grand child.

    The script call does not change:

    <script id="clobscript" type="text/javascript" src="/path/to/clobs.js?id=xxxx&i=9&v=1&2014012301"></script>
    

     

    Manual Verification (client side): use https://gx.ip-label.net/rumbi/decode.php

     

    Was this page helpful?
    Tag page (Edit tags)
    • No tags
    Page statistics
    3017 view(s), 7 edit(s) and 3143 character(s)

    Comments

    You must login to post a comment.

    Attach file

    Attachments