Client event livestream

Check if Google received the event messages you sent, and confirm that the
format of the messages are correct. In the GCP Console,
you can access the Client event livestream tool.
The most recent event messages (up to 50) are listed. View event details
by selecting any of the listed events. Check all events with the same
requestId by clicking the "ALL EVENTS BY REQUESTID" button in the header.
You'll see warnings in the detailed view in cases where the clientEvent message was sent with
incorrect formats. Use filtering options to filter the messages
by either the requestId, userId, or sessionId.

If the message doesn't appear in the Client event livestream, check that the
requestId in the event message is valid. Event messages without a valid
requestId are discarded by Cloud Talent Solution.

Client event search

Search for all event messages having a specific requestId. Similar to
Client event livestream, you can verify if Google received your event
messages and that these are well-formatted messages for a particular
requestId. You can also use the filter panel on the right side to filter out,
for example, well-formed messages.

Job export

Export job data to generate a JSON file of your jobs indexed with Cloud Talent Solution using the Job export tool.
There are three options for selecting the job fields to view.

Default fields: Include name, distributorId, and requisitionId

Selected fields: Choose up to 10 fields to include.

All fields: This option generates the JSON based on the snapshot at the
timestamp indicated above the field.

Choose an option, and select GENERATE to create a JSON file. A record of your
export can now be viewed on the table. Click the download link to download the
file.

Note: After 7 days, the file is removed from the table.

If there are more than 3MM jobs in your system, and options other than
ALL_FIELDS have been selected, only the most recently created 3MM jobs are
returned.

To prevent further performance issues, Google disables this option if your
file is too large.

Service account management

You must connect a service account to Cloud Talent Solution in order to use the
credentials associated with that account and to make an API request. Use the
Service accounts connections tool to manage your service accounts.
All service accounts associated with your Google Cloud project are listed.
Click "Connect" to associate a service account with Cloud Talent Solution.
Learn more about service accounts at Creating and Managing Service Accounts.

Troubleshooting ClientEvent validation errors

Validations based on a single event

Constant

UI string

RELATED_JOB_ID_INVALID

The ClientEvent message has one or more invalid or incorrect relatedJobNames

EVENT_ID_REUSED

An eventId must be unique to a Google Cloud Project. In this case, the message has an eventId previously generated by your Google Cloud Project. Best practice is to include some form of timestamp into each eventId, to ensure uniqueness.

One or more fields of the message were either incomplete or were not expected by Cloud Talent Solution. See the ClientEvent schema for more information on required fields, and the values expected in those fields.

UNKNOWN_FIELDS

Received unknown field(s)

INVALID_FORMAT

Received an invalid JSON string in the Cloud Talent Solution ClientEvent message. For example, a missing brace.

Aggregated validations by requestId

The number of VIEW events is fewer than the number of APPLICATION_START events. This could either be because the VIEW events are not being correctly sent to Cloud Talent Solution, or the Apply button on the UI is being triggered without actually triggering a view. If this is the intended behavior (for example, if the search results page has an apply button that job seekers can click without viewing the job details) then consider using a APPLICATION_START_FROM_SERP event for this use case instead.

VIEWS_FEWER_THAN_APPLY_REDIRECTS

The number of VIEW events is fewer than the number of APPLICATION_REDIRECT events. This could be either because the VIEW events are not being correctly sent to Cloud Talent Solution, or the Apply button on the UI is being triggered without actually triggering a view. If this is the intended behavior (for example, if the search results page has an apply button that job seekers can click, without viewing the job details) then consider using a APPLICATION_REDIRECT_FROM_SERP event for this use case instead.