---
title: "GoogleCM360_Conversion_Export: Update job"
method: PUT
path: "/job/google-cm360-conversion-export/{id}"
tags: ["Jobs"]
---

# GoogleCM360_Conversion_Export: Update job

`PUT /job/google-cm360-conversion-export/{id}`

Update a GoogleCM360_Conversion_Export job

## Path parameters

- `id` string, required

## Query parameters

- `account_id` string

## Response `200`

GoogleCM360_Conversion_Export Job

- object
  - `_meta` object — Response Metadata
  - `data` object — Response Payload
    - `account_id` string — Lytics Account ID
    - `anomaly_rule` ModelsAnomalyRuleResp
      - `aid` integer
      - `checks` ModelsRuleCheckConfigReq[]
        - `allowable_violations` integer
        - `interval` string
        - `lookback_count` integer
        - `max_threshold` integer
        - `metric_type` string
        - `min_threshold` integer
        - `type` string
        - `variance_pct` number
      - `created` string
      - `id` string
      - `subject_id` string
      - `subject_type` string
      - `updated` string
    - `api_token_auth_id` string — this is set when work is create using access token
    - `auth_ids` string[] — Authorization IDs associated with the Job
    - `config` object, required — Job configuration, unique per-workflow
      - `conversion_quantity` string — Enter the Lytics user field that contains the conversion event quantity. If not given, the value will be set to 0.
      - `conversion_timestamp` string — Enter the Lytics user field that contains the conversion event timestamp. If not given, the events will be sent with the current timestamp. Please not events cannot be older than 28 days.
      - `conversion_value` string — Enter the Lytics user field that contains the conversion event value. If not given, the value will be set to 0.
      - `enhanced_conversion` boolean — Select to send enhanced conversion events to Google CM360. Otherwise the events will be uploaded as offline events.
      - `event_identifier_mapping` object[], required — Map the Identifier fields from Lytics to Google CM360 event identifier by selecting the Lytics field on the left, and its CM360 destination field on the right. You can only send one identifier to CM360.
      - `floodlight_activity_id` integer, required — Enter the Floodlight Activity ID for the conversion events.
      - `floodlight_configuration_id` integer, required — Enter the Floodlight Configuration ID for the conversion events.
      - `ordinal_id` string, required — Enter the Lytics user field that contains the conversion event ordinal ID which is used as a deduplication key in Google CM360.
      - `profile_id` integer, required — Select your Google CM360 User Profile ID.
      - `segment_ids` string[] — Select the Lytics audience to export to Google CM360.
      - `user_pii_mapping` object[] — Map the User PII fields from Lytics to Google CM360 fields by selecting the Lytics field on the left, and its CM360 destination on the right. All these fields if not already hashed will be hashed using SHA256 before sending to Google CM360.
      - `withbackfill` boolean — Select to add users who already exist in the selected Lytics audience.
    - `created` string
    - `deleted` boolean — The Job has been deleted
    - `description` string — A user-defined description
    - `drop_events_during_quiet_window` boolean
    - `expires_at` string, date-time
    - `id` string — A Lytics-assigned, immutable unique ID for the Job
    - `meta` object — Extra meta data about the job
    - `monitoring` object — Inline monitoring config. On write: omit to keep, null to clear, or a config to set.
    - `name` string, required — A user-defined name
    - `quiet_period` integer
    - `quiet_time_of_day` string
    - `quiet_timezone` string
    - `sleep_until` string
    - `status` 'runnable' | 'sleeping' | 'paused' | 'completed' | 'fault' | 'failed' | 'killed' | 'deleted' | 'unknown' — The status of the job
    - `updated` string
    - `user_id` string — The user ID that created or updated the job
    - `workflow` string — The workflow slug
    - `workflow_id` string — The workflow ID
  - `request_id` string
  - `status` integer — HTTP Status Code

## Other responses

- `404` — Not Found
- `500` — Internal Server Error

---

[API](https://skmtc.net/lytics/apis/lytics-api.md) · [All operations](https://skmtc.net/lytics/apis/lytics-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/lytics/lytics-api/versions/366eeabcb6de/schema)