Google Tag Manager (Improved) icon

Google Tag Manager (Improved)

Use the Google Tag Manager API

Actions27

Container → Update Container

AI-generated

Overview

This node operation updates a Google Tag Manager (GTM) Container within a specified GTM Account. It is useful for modifying container settings or configurations programmatically via the GTM API. For example, a user can update container details such as name, usage context, or other metadata by providing the necessary account and container IDs along with the update data.

Use Case Examples

  1. Updating a GTM Container's name or description by specifying the Account ID, Container ID, and the new container details in the request body.
  2. Automating container configuration updates as part of a CI/CD pipeline for GTM setups.

Properties

Name Meaning
Account ID The GTM Account ID where the container resides. Required to identify the account for the update operation.
Container ID The GTM Container ID to be updated. Required to specify which container to update within the account.
Optional Query Parameters Additional optional parameters that can modify the update request behavior, such as fingerprint for concurrency control.
Request Body The JSON object containing the container data to update, such as new container settings or metadata.

Output

JSON

  • accountId - The ID of the GTM Account associated with the container.
  • containerId - The ID of the updated GTM Container.
  • name - The name of the GTM Container.
  • usageContext - The contexts in which the container is used.
  • fingerprint - The fingerprint of the container for concurrency control.
  • path - The API path of the container resource.

Dependencies

  • Google Tag Manager API with OAuth2 credentials

Troubleshooting

  • Missing required parameters such as Account ID or Container ID will cause the operation to fail with an error indicating the missing parameter.
  • Incorrect or expired OAuth2 credentials will result in authentication errors when calling the GTM API.
  • Providing an invalid or mismatched fingerprint in optional query parameters may cause update conflicts.
  • Ensure the request body JSON is correctly formatted and contains valid container data to avoid API errors.

Links

Discussion