Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

   

Image Removed

Dear Kantar Technology Users Welcome!

This is the Kantar Audience Global Support and ODDU Ticket Portal!

Here you find all the information to raise your request to L2 Global Technology Support Experts. The Portal connects you to the teams for Kantar audience measurement applications such as, TV Meters, Video Meters, Audio Matching, Audio Watermarking, Atria Technology and Tagging technologies. 

Links to Service Desk and Service Now ticketing tools user guides are provided to help you open and follow requests.

...

Image Added

Welcome to the L2 Ticket Portal One Stop Support Home

Note

For all AGS requests please always raise a ticket in Service DeskSee below for each team service desk.

For all changes make sure you raise or request it following the process referenced below.

IT and AGS change freeze starting on December 20th.



TICKETINGTECHNOLOGY COMPONENTS


Atria Support  > All Markets

Atria Cloud, Atria Aten, Atria NG/NGI, Atria Online (FMDP Classic up to 2.14, VMRG), Atria QC framework, Aten, Portal,

Atria Pro, Fusion

AtriaPro, Atria Portable, Transmission Logs.

 Atria Documentation Jan Fric Richard.Goalen@kantar.com


Support

Kantar ACR Audiomatching technologies: 

/wiki/spaces/ANE/pages/123142212

 and 

 

/wiki/spaces/ANE/pages/123142760 

(I33, Collect Stations, RTM)    Audio Matching DocumentationPhilippe Gauxtanguy.millet@kantar.comWatermarking Support Kantar ACR Watermarking technologies: /wiki/spaces/ANE/pages/135123988  Watermarking DocumentationPhilippe Gauxtanguy.millet@kantar.com

  


Watermarking Documentation

Kantar
TV Meters
technologies: PM7, PM5000TV Meters
Documentation
Morgana SellamuthuVassilis.Tantsios@Kantar.com

Kantar Video Meters technologies: Focal Meter, Virtual Meter, Kantar Media Backend (KMBE), Focal Meter Data Processing (FMDP).
/wiki/spaces/EVME/overview
Marc DrosnetJean-Christophe.Mison@kantar.comService Desk User GuideUse this link to get help Service Desk ticketing toolService Now User Guide

Kantar ODDU technologies: Kantar Browser Meter Frontend, Kantar Tagging ( SDK's for Java Script, Android, IOS etc.), ODDU data collection and ODDU data processing (delivieries EMEDIA census, targets and panelusage)ODDU DocumentationRalf JahnkeFrank.Kammann@kantar.com
ODDU Documentation
(info)Good Ticket Description (L1)

To ensure the team can support you faster and efficiently a Good Acceptable Description for a ticket request must contain: 1) Title, what is the request for, with concise subject and the correct category (e.g. weighting not running, rerun failure, etc.); 2) the Description, what you want L2 support team to do, it must describe comprehensively the problem/request including, what you (L1) have done to resolve (this is essential) with the analysis, investigation, relevant logs, errors, reports, data files, tests, panel homes/individuals, application/s and version/s. Where possible should always provide evidence like pics/audio; 3) Please ensure all mandatory fields are completed.

An incomplete / not acceptable description could lead to delay or, return to “waiting for customer” state.

(info)AGS Know-How

AGS Global Support Training & Documentation repository.

All questions contact David Strange (Atria BARB)

(info)Change Management Media CAB/Process

Part 1 reference deck.

If you would like training or more information please write to Carlo Imperato Woods, Kelly (KNLDN)

(info)Service Desk

User Guide.

Onboarding new clients in Service Desk- No need to be registered as a JIRA user or to have a Kantar address. 

  1. To onboard clients please notify the Team Support Manager for ACR, Atria, VDM, TVM, ODDU, with the list of people, emails, teams to add.
  2. Team Support Manager to acknowledge request. They may create ticket in system for our tracking.
  3. Team Support Manager to set up. The customer will receive an invite to login, to create his password and so its customer account to raise tickets.

If client is internal already has an Atlassian account:

  1. Team Support Manager to declare them, not as customers but as internal agents (need to have an Atlassian account JIRA or Confluence) e.g. developers which provide access to internal comments 
  2. This account to be used for Service Desk, set up as developers
(info)One JIRA

If you need access to Confluence or Service Desk licenses for support engineer (it is not for customers only licenses).