Stay organized with collections
Save and categorize content based on your preferences.
Cloud Talent Solution now provides visualizations of your data in the
CTS dashboard.
You can use this information to monitor your API configurations. The dashboard
also provides information about how Cloud Talent Solution impacts the behavior of job
seekers on your website.
The dashboard displays information in two main sections:
Search data
Client event data
Search data
The Search data section shows aggregated information about the search
queries sent through your service. You can use this section to keep track of the
top Query texts and Location filters. The search data Data
validation chart highlights data problems to enable you to detect and correct
issues. The validation chart displays actionable information and metrics on any
search queries with defects, such as missing user IDs, session IDs, query texts,
or other important information. Ensuring high quality search request data is
important for Job Search performance.
Client Event Data
The Client event data section displays user behavior information that
has been sent back to CTS as
client events. You can use this
section to review actionable information on client event Counts per day as
well as daily Apply rates and View rates.
The client event Data validation table displays metrics on event data with
defects. Because client event data is used to train your model, you
should check that the data sent back to CTS by your service is in line with your
expectations. You can use the metrics displayed in this table to evaluate your
configurations:
Multiple impressions: Cloud Talent Solution uses IMPRESSION
events to establish actions. The baseline action is that the API has
returned a list of jobs to a job seeker in response to a search request.
Cloud Talent Solution expects one IMPRESSION event
per search API request. Multiple impression events being sent
for a single request might indicate an incorrect configuration.
No impressions: IMPRESSION events are
vital to training the model, and missing events can affect model learning.
Reused eventId: EventId
values are unique identifiers that you assign to this field. You should
never resuse them. EventId values must be unique to the Google Cloud
Platform project that you use to call Cloud Talent Solution.
Invalid jobId: relatedJobNames
are used to tell the model which jobs are within the context of an event.
For example, an IMPRESSION event should contain the Google-provided ids of
jobs that were displayed to the job seeker. Cloud Talent Solution cannot accept ids
that were not generated by the Google system.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-28 UTC."],[],[],null,["# Dashboard management tool (v4beta1)\n\nCloud Talent Solution now provides visualizations of your data in the\nCTS [dashboard](http://console.cloud.google.com/talent-solution).\nYou can use this information to monitor your API configurations. The dashboard\nalso provides information about how Cloud Talent Solution impacts the behavior of job\nseekers on your website.\n\nThe dashboard displays information in two main sections:\n\n1. Search data\n2. Client event data\n\nSearch data\n-----------\n\nThe **Search data** section shows aggregated information about the search\nqueries sent through your service. You can use this section to keep track of the\ntop **Query texts** and **Location filters** . The search data **Data\nvalidation** chart highlights data problems to enable you to detect and correct\nissues. The validation chart displays actionable information and metrics on any\nsearch queries with defects, such as missing user IDs, session IDs, query texts,\nor other important information. Ensuring high quality search request data is\nimportant for Job Search performance.\n\nClient Event Data\n-----------------\n\nThe **Client event data** section displays user behavior information that\nhas been sent back to CTS as\n[client events](/talent-solution/job-search/v4beta1/docs/events). You can use this\nsection to review actionable information on client event **Counts** per day as\nwell as daily **Apply rates** and **View rates**.\n\nThe client event **Data validation** table displays metrics on event data with\ndefects. Because client event data is used to train your model, you\nshould check that the data sent back to CTS by your service is in line with your\nexpectations. You can use the metrics displayed in this table to evaluate your\nconfigurations:\n\n1. **Multiple impressions** : Cloud Talent Solution uses [`IMPRESSION`](/talent-solution/job-search/v4beta1/docs/client-event#EventType.ENUM_VALUES.IMPRESSION)\n events to establish actions. The baseline action is that the API has\n returned a list of jobs to a job seeker in response to a search request.\n Cloud Talent Solution expects one `IMPRESSION` event\n per search API request. Multiple impression events being sent\n for a single request might indicate an incorrect configuration.\n\n2. **No impressions** : `IMPRESSION` events are\n vital to training the model, and missing events can affect model learning.\n\n3. **Reused `eventId`** : [`EventId`](/talent-solution/job-search/v4beta1/docs/client-event#FIELDS.event_id)\n values are unique identifiers that you assign to this field. You should\n never resuse them. `EventId` values must be unique to the Google Cloud\n Platform project that you use to call Cloud Talent Solution.\n\n4. **Invalid `jobId`** : [`relatedJobNames`](/talent-solution/job-search/v4beta1/docs/client-event#FIELDS.related_job_names)\n are used to tell the model which jobs are within the context of an event.\n For example, an `IMPRESSION` event should contain the Google-provided ids of\n jobs that were displayed to the job seeker. Cloud Talent Solution cannot accept ids\n that were not generated by the Google system.\n\nMore management tools\n---------------------\n\nFor more information on ways to monitor and troubleshoot your\ndata, see the [Cloud Talent Solution management tools](/talent-solution/docs/management-tools)\npage."]]
