Tag Manager API create trigger 500 error

Open
  • Is something wrong?
#3,597 1 comment 2 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Domain
api

Research direction

The report identifies the Google Tag Manager Create Triggers endpoint and provides a sample POST request, but names no repository file or test. Start by reproducing the request and determine whether the failure is in this client library or the external API; done requires an actionable repository change or confirmation that the issue belongs with the API provider.

Written by the indexing model from the issue text.

Description

We have encountered an issue with one of the Google Tag Manager API methods, which suddenly appears to be experiencing a 500 “Experienced an internal error” outage. Since there is no real public GTM API support team like Google Analytics, we appreciate it if you could direct us to the appropriate support channel to address this matter.

APIs Explorer:

POST https://tagmanager.googleapis.com/tagmanager/v2/accounts/{{account_id}}/containers/{{container_id}}/workspaces/2/triggers?key=[YOUR_API_KEY] HTTP/1.1

Authorization: Bearer [YOUR_ACCESS_TOKEN]
Accept: application/json
Content-Type: application/json

{
  "name": "Test trigger with filters",
  "type": "pageview",
  "filter": [
    {
      "parameter": [
        {
          "type": "boolean",
          "value": "true",
          "key": "ignore_case"
        },
        {
          "type": "template",
          "key": "arg1",
          "value": "thank"
        }
      ],
      "type": "matchRegex"
    }
  ]
}

unnamed

Dominant language
TypeScript
Stars
12.3k
Forks
2k
Avg merge
3d 10h
Merged PRs (30d)
9

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from googleapis/google-api-nodejs-client

All issues in googleapis/google-api-nodejs-client

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.