---
title: "AdwordsCustomerMatch: Update job"
method: PUT
path: "/job/adwords-customer-match/{id}"
tags: ["Jobs"]
---

# AdwordsCustomerMatch: Update job

`PUT /job/adwords-customer-match/{id}`

Update a AdwordsCustomerMatch job

## Path parameters

- `id` string, required

## Query parameters

- `account_id` string

## Response `200`

AdwordsCustomerMatch 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
      - `ad_consent` string — Select the consent status for sending user data to Google for advertising purposes. Different consent groups should be sent through separate jobs to the same list
      - `adwords_account_id` string, required — Select which Google Ads account to create the customer match list and audience model. This has to be set to select lists from managed Google Ads accounts
      - `adwords_customer_id` string — Select the managed Google Ads account associated with the account selected above. This will take precedence over the selected Google Ads account. If there is no managed Google Ads Account select the same account as above.
      - `adwords_list_id` integer — Select which Google Ads customer match list to append to. If no list is selected, a new customer match list will be created
      - `app_id` string — If Mobile ID is entered, enter the Mobile App ID for the mobile application from which the data was collected to AdWords API
      - `country_code_field` string — Select which field contains the user's two letter country code
      - `email_field` string — Select the field containing the user's email — plain or SHA256-hashed; plain values are hashed before sending.
      - `first_name_field` string — Select which field contains the user's first name. To match by name, country code and zipcode must be provided
      - `last_name_field` string — Select which field contains the user's last name
      - `mobile_id_field` string — Select to match on mobile ID field instead of email
      - `personalization_consent` string — Select consent status for ad personalization. Different consent groups should be sent through separate jobs to the same list
      - `phone_number_field` string — Select the field containing the user's phone number — plain or SHA256-hashed; plain values are hashed before sending.
      - `segment_id` string — Select the Lytics audience to export to Google Ads and create audience model off of
      - `user_id_field` string — Select to match on user ID field instead of email
      - `zip_code_field` string — Select which field contains the user's zipcode
    - `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)