> ## Documentation Index
> Fetch the complete documentation index at: https://docs.scanova.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Update your campaign log

> PATCH /campaign/user-log/{id}/

Updates a single G2 review-campaign log row on the **Management API** host (`api.scanova.io`), authenticated with your raw Management API key.

```
PUT   https://api.scanova.io/campaign/user-log/{id}/
PATCH https://api.scanova.io/campaign/user-log/{id}/
Authorization: 401f7ac837da42b97f613d789819ff93537bee6a
```

<ParamField path="id" type="integer" required>
  The log row's `id`, from [`POST /campaign/user-log/`](/api-reference/management-api/campaign/user-log-create) or [`GET /campaign/active/user-log/`](/api-reference/management-api/campaign/user-log-status).
</ParamField>

Both `PUT` and `PATCH` are supported (`PUT` for a full replace, `PATCH` for a partial update) and accept the same field set documented for [Log that the review popup was shown, dismissed, or submitted](/api-reference/management-api/campaign/user-log-create), minus `g2_campaign` — which row you're updating is fixed by `id` in the URL, not something you can move to a different campaign after creation.

<RequestExample>
  ```bash cURL theme={null}
  curl -X PATCH "https://api.scanova.io/campaign/user-log/118/" \
    -H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a" \
    -H "Content-Type: application/json" \
    -d '{ "last_dismissed": "2026-08-21T09:02:00Z" }'
  ```
</RequestExample>

<ResponseExample>
  ```json 200 theme={null}
  {
    "id": 118,
    "last_shown": "2026-08-20T10:15:00Z",
    "last_dismissed": "2026-08-21T09:02:00Z",
    "last_submitted": null,
    "is_popup_disabled": false
  }
  ```
</ResponseExample>

## `is_popup_disabled` can't be set here

`is_popup_disabled` appears in every response from this resource, but it's read-only on this serializer — sending it in the request body (via either `PUT` or `PATCH`) is silently ignored, despite it being a real field on the underlying model. There's currently no documented Management API path that flips it; it's set internally.

## Scope and errors

Scoped to log rows owned by the requesting account — an `id` belonging to another account returns `404`, not `403`, so you can't use this endpoint to probe for the existence of other accounts' log rows.

## Related

* [Log that the review popup was shown, dismissed, or submitted](/api-reference/management-api/campaign/user-log-create) — creates the row this endpoint updates.
* [Get your dismissal state for the active campaign](/api-reference/management-api/campaign/user-log-status) — read the current state of this row.
* [Get the active review campaign](/api-reference/management-api/campaign/active) — the campaign this log row applies to.
* [Management API overview](/api-reference/management-api/overview) — the auth scheme and quota rules that apply to this endpoint.


## OpenAPI

````yaml api-reference/openapi/management-api.json PATCH /campaign/user-log/{id}/
openapi: 3.1.0
info:
  title: Scanova Management API (v2)
  description: >-
    The complete Scanova Management API — every endpoint available at
    api.scanova.io (QR codes, folders, tags, leads, forms, analytics, plans,
    shared users & roles), plus the token-creation and usage-stats endpoints
    used to authenticate against it. Every path and request/response shape below
    was verified live against a real API key and the actual running backend
    (Phase 7, 2026-08-16) — not guessed from reading urls.py alone.
  version: 2.0.0
servers:
  - url: https://api.scanova.io
    description: Management API — QR/folder/tag/lead/form/analytics/plans endpoints
security:
  - apiKeyAuth: []
paths:
  /campaign/user-log/{id}/:
    patch:
      summary: Update your campaign log (partial update)
      description: >-
        Scoped to log rows owned by the requesting account — `id` values
        belonging to another account return 404, not 403. `is_popup_disabled` is
        read-only on this serializer and can't be set through either PATCH or
        PUT despite appearing as a model field.
      operationId: partialUpdateManagedCampaignUserLog
      parameters:
        - name: id
          in: path
          required: true
          schema:
            type: integer
      requestBody:
        content:
          application/json:
            schema:
              type: object
              properties:
                last_shown:
                  type: string
                  format: date-time
                last_dismissed:
                  type: string
                  format: date-time
                last_submitted:
                  type: string
                  format: date-time
            example:
              last_dismissed: '2026-08-21T09:02:00Z'
      responses:
        '200':
          description: Log row updated.
          content:
            application/json:
              example:
                id: 118
                last_shown: '2026-08-20T10:15:00Z'
                last_dismissed: '2026-08-21T09:02:00Z'
                last_submitted: null
                is_popup_disabled: false
components:
  securitySchemes:
    apiKeyAuth:
      type: apiKey
      in: header
      name: Authorization
      description: >-
        Send your Management API key as the raw value of the Authorization
        header — no "Bearer " or "Token " prefix, and no other characters.
        Example: `Authorization: 401f7ac837da42b97f613d789819ff93537bee6a`. A
        header containing more than one space-separated part is rejected
        outright. Requests also require the request's Host header to be the
        management API host (e.g. api.scanova.io) — the same key sent to the
        regular API host will not authenticate.

````