Cloud Talent Solution now provides visualizations of your data in the
CTS [dashboard](http://console.cloud.google.com/talent-solution).
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:

1. Search data
2. 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](https://docs.cloud.google.com/talent-solution/job-search/v4beta1/docs/events.md.txt). 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:

1. **Multiple impressions** : Cloud Talent Solution uses [`IMPRESSION`](https://docs.cloud.google.com/talent-solution/job-search/v4beta1/docs/client-event.md.txt#EventType.ENUM_VALUES.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.

2. **No impressions** : `IMPRESSION` events are
   vital to training the model, and missing events can affect model learning.

3. **Reused `eventId`** : [`EventId`](https://docs.cloud.google.com/talent-solution/job-search/v4beta1/docs/client-event.md.txt#FIELDS.event_id)
   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.

4. **Invalid `jobId`** : [`relatedJobNames`](https://docs.cloud.google.com/talent-solution/job-search/v4beta1/docs/client-event.md.txt#FIELDS.related_job_names)
   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.

## More management tools

For more information on ways to monitor and troubleshoot your
data, see the [Cloud Talent Solution management tools](https://docs.cloud.google.com/talent-solution/docs/management-tools.md.txt)
page.