Google Tag Manager icon

Google Tag Manager

Use the Google Tag Manager API
Join our community

Actions102

Overview

This node integrates with the Google Tag Manager (GTM) API, specifically supporting operations on Google Tag Configurations among many other GTM resources. The "Delete Google Tag Configuration" operation allows users to delete a specific Google Tag Configuration within a GTM workspace.

Typical use cases include automating the management of GTM configurations, such as cleaning up obsolete or incorrect tag configurations programmatically. For example, if you have multiple environments or containers and want to remove outdated Google Tag Configurations automatically, this node operation can be used in workflows to perform that deletion safely and efficiently.

Properties

Name Meaning
Account ID The GTM Account ID where the Google Tag Configuration exists.
Container ID The GTM Container ID under which the workspace and configuration reside.
Workspace ID The GTM Workspace ID containing the Google Tag Configuration to delete.
Google Tag Configuration ID The unique identifier of the Google Tag Configuration to delete.
Optional Query Parameters Additional optional parameters for the request, including:
- Allow User Permission Feature Update (boolean): Must be true to allow user permission changes.
- Built-In Variable Type (select from many predefined types).
- Container ID (string): ID of container to merge or related operations.
- Container Version ID (string): Specific container version reference.
- Copy Settings (boolean): Whether to copy tag settings when creating new tags.
- Copy Terms Of Service (boolean): Must be true to accept terms of service agreements.
- Copy Users (boolean): Whether to copy users from one tag to another.
- Destination ID (string): Linked destination ID for a GTM container.
- Fingerprint (string): Must match the stored account fingerprint for concurrency control.
- Include Google Tags (boolean): Whether to include accounts associated with Google Tag.
- Page Token (string): Token for paginated results.
- Setting Source (option): Source of config setting after combine (Current, Other, Unspecified).
- Tag ID (string): Tag ID for GTM container.
- Tag Name (string): Name for newly created tag.
- Trigger ID (string): Triggers to move to folder.
- Variable ID (string): Variables to move to folder.

Output

The output is a JSON array containing the response from the Google Tag Manager API for the delete operation. Typically, for a delete operation, the response may be empty or contain metadata confirming the deletion.

  • json: Contains the parsed JSON response from the API call.
  • No binary data is output by this operation.

Dependencies

  • Requires an OAuth2 credential configured for Google Tag Manager API access.
  • The node uses the Google Tag Manager API base URL: https://www.googleapis.com/tagmanager/v2.
  • Proper permissions must be granted to the OAuth2 token to manage GTM accounts, containers, workspaces, and Google Tag Configurations.

Troubleshooting

  • Missing Credentials: If the OAuth2 credentials are not set or invalid, the node will throw an error indicating missing credentials.
  • Required Parameter Missing: Errors will occur if any required parameter (Account ID, Container ID, Workspace ID, or Google Tag Configuration ID) is missing for the delete operation.
  • API Errors: Any errors returned by the Google Tag Manager API (e.g., permission denied, resource not found) will be surfaced with the message prefix "Error calling GTM API".
  • Fingerprint Mismatch: If using the optional fingerprint parameter, ensure it matches the current stored fingerprint to avoid concurrency conflicts.
  • User Permission Feature Update: If the operation involves user permissions, the allowUserPermissionFeatureUpdate flag must be set to true; otherwise, the operation will fail.

Links and References

This summary focuses on the "Delete Google Tag Configuration" operation within the Google Tag Configuration resource, describing its inputs, outputs, dependencies, and common troubleshooting points based on static analysis of the provided source code and property definitions.

Discussion