Update
|
|||||
|
|
Updates a GTM Environment
Authorization
To use this building block you will have to grant access to at least one of the following scopes:
- Manage your Google Tag Manager container and its subcomponents, excluding versioning and publishing
Input
This building block consumes 19 input parameters
Name | Format | Description |
---|---|---|
path Required |
STRING |
GTM Environment's API relative path. Example: accounts/{account_id}/containers/{container_id}/environments/{environment_id} |
fingerprint |
STRING |
When provided, this fingerprint must match the fingerprint of the environment in storage |
accountId |
STRING |
GTM Account ID |
authorizationCode |
STRING |
The environment authorization code |
authorizationTimestamp |
OBJECT |
A Timestamp represents a point in time independent of any time zone or local calendar, encoded as a count of seconds and fractions of seconds at nanosecond resolution. The count is relative to an epoch at UTC midnight on January 1, 1970, in the proleptic Gregorian calendar which extends the Gregorian calendar backwards to year one. All minutes are 60 seconds long. Leap seconds are "smeared" so that no leap second table is needed for interpretation, using a 24-hour linear smear. The range is from 0001-01-01T00:00:00Z to 9999-12-31T23:59:59.999999999Z. By restricting to that range, we ensure that we can convert to and from RFC 3339 date strings. ExamplesExample 1: Compute Timestamp from POSIX Timestamp timestamp; timestamp.set_seconds(time(NULL)); timestamp.set_nanos(0); Example 2: Compute Timestamp from POSIX struct timeval tv; gettimeofday(&tv, NULL); Timestamp timestamp; timestamp.set_seconds(tv.tv_sec); timestamp.set_nanos(tv.tv_usec * 1000); Example 3: Compute Timestamp from Win32 FILETIME ft; GetSystemTimeAsFileTime(&ft); UINT64 ticks = (((UINT64)ft.dwHighDateTime) << 32) | ft.dwLowDateTime; // A Windows tick is 100 nanoseconds. Windows epoch 1601-01-01T00:00:00Z // is 11644473600 seconds before Unix epoch 1970-01-01T00:00:00Z. Timestamp timestamp; timestamp.set_seconds((INT64) ((ticks / 10000000) - 11644473600LL)); timestamp.set_nanos((INT32) ((ticks % 10000000) * 100)); Example 4: Compute Timestamp from Java long millis = System.currentTimeMillis(); Timestamp timestamp = Timestamp.newBuilder().setSeconds(millis / 1000) .setNanos((int) ((millis % 1000) * 1000000)).build(); Example 5: Compute Timestamp from current time in Python. timestamp = Timestamp() timestamp.GetCurrentTime() JSON MappingIn JSON format, the Timestamp type is encoded as a string in the RFC 3339 format. That is, the format is "{year}-{month}-{day}T{hour}:{min}:{sec}[.{frac_sec}]Z" where {year} is always expressed using four digits while {month}, {day}, {hour}, {min}, and {sec} are zero-padded to two digits each. The fractional seconds, which can go up to 9 digits (i.e. up to 1 nanosecond resolution), are optional. The "Z" suffix indicates the timezone ("UTC"); the timezone is required. A proto3 JSON serializer should always use UTC (as indicated by "Z") when printing the Timestamp type and a proto3 JSON parser should be able to accept both UTC and other timezones (as indicated by an offset). For example, "2017-01-15T01:30:15.01Z" encodes 15.01 seconds past 01:30 UTC on January 15, 2017. In JavaScript, one can convert a Date object to this format using the standard toISOString() method. In Python, a standard |
authorizationTimestamp.nanos |
INTEGER |
Non-negative fractions of a second at nanosecond resolution. Negative second values with fractions must still have non-negative nanos values that count forward in time. Must be from 0 to 999,999,999 inclusive |
authorizationTimestamp.seconds |
INTEGER |
Represents seconds of UTC time since Unix epoch 1970-01-01T00:00:00Z. Must be from 0001-01-01T00:00:00Z to 9999-12-31T23:59:59Z inclusive |
containerId |
STRING |
GTM Container ID |
containerVersionId |
STRING |
Represents a link to a container version |
description |
STRING |
The environment description. Can be set or changed only on USER type environments |
enableDebug |
BOOLEAN |
Whether or not to enable debug by default for the environment |
environmentId |
STRING |
GTM Environment ID uniquely identifies the GTM Environment |
fingerprint |
STRING |
The fingerprint of the GTM environment as computed at storage time. This value is recomputed whenever the environment is modified |
name |
STRING |
The environment display name. Can be set or changed only on USER type environments |
path |
STRING |
GTM Environment's API relative path |
tagManagerUrl |
STRING |
Auto generated link to the tag manager UI |
type |
ENUMERATION |
The type of this environment |
url |
STRING |
Default preview page url for the environment |
workspaceId |
STRING |
Represents a link to a quick preview of a workspace |
= Parameter name
= Format
path STRING Required GTM Environment's API relative path. Example: accounts/{account_id}/containers/{container_id}/environments/{environment_id} |
fingerprint STRING When provided, this fingerprint must match the fingerprint of the environment in storage |
accountId STRING GTM Account ID |
authorizationCode STRING The environment authorization code |
authorizationTimestamp OBJECT A Timestamp represents a point in time independent of any time zone or local calendar, encoded as a count of seconds and fractions of seconds at nanosecond resolution. The count is relative to an epoch at UTC midnight on January 1, 1970, in the proleptic Gregorian calendar which extends the Gregorian calendar backwards to year one. All minutes are 60 seconds long. Leap seconds are "smeared" so that no leap second table is needed for interpretation, using a 24-hour linear smear. The range is from 0001-01-01T00:00:00Z to 9999-12-31T23:59:59.999999999Z. By restricting to that range, we ensure that we can convert to and from RFC 3339 date strings. ExamplesExample 1: Compute Timestamp from POSIX Timestamp timestamp; timestamp.set_seconds(time(NULL)); timestamp.set_nanos(0); Example 2: Compute Timestamp from POSIX struct timeval tv; gettimeofday(&tv, NULL); Timestamp timestamp; timestamp.set_seconds(tv.tv_sec); timestamp.set_nanos(tv.tv_usec * 1000); Example 3: Compute Timestamp from Win32 FILETIME ft; GetSystemTimeAsFileTime(&ft); UINT64 ticks = (((UINT64)ft.dwHighDateTime) << 32) | ft.dwLowDateTime; // A Windows tick is 100 nanoseconds. Windows epoch 1601-01-01T00:00:00Z // is 11644473600 seconds before Unix epoch 1970-01-01T00:00:00Z. Timestamp timestamp; timestamp.set_seconds((INT64) ((ticks / 10000000) - 11644473600LL)); timestamp.set_nanos((INT32) ((ticks % 10000000) * 100)); Example 4: Compute Timestamp from Java long millis = System.currentTimeMillis(); Timestamp timestamp = Timestamp.newBuilder().setSeconds(millis / 1000) .setNanos((int) ((millis % 1000) * 1000000)).build(); Example 5: Compute Timestamp from current time in Python. timestamp = Timestamp() timestamp.GetCurrentTime() JSON MappingIn JSON format, the Timestamp type is encoded as a string in the RFC 3339 format. That is, the format is "{year}-{month}-{day}T{hour}:{min}:{sec}[.{frac_sec}]Z" where {year} is always expressed using four digits while {month}, {day}, {hour}, {min}, and {sec} are zero-padded to two digits each. The fractional seconds, which can go up to 9 digits (i.e. up to 1 nanosecond resolution), are optional. The "Z" suffix indicates the timezone ("UTC"); the timezone is required. A proto3 JSON serializer should always use UTC (as indicated by "Z") when printing the Timestamp type and a proto3 JSON parser should be able to accept both UTC and other timezones (as indicated by an offset). For example, "2017-01-15T01:30:15.01Z" encodes 15.01 seconds past 01:30 UTC on January 15, 2017. In JavaScript, one can convert a Date object to this format using the standard toISOString() method. In Python, a standard |
authorizationTimestamp.nanos INTEGER Non-negative fractions of a second at nanosecond resolution. Negative second values with fractions must still have non-negative nanos values that count forward in time. Must be from 0 to 999,999,999 inclusive |
authorizationTimestamp.seconds INTEGER Represents seconds of UTC time since Unix epoch 1970-01-01T00:00:00Z. Must be from 0001-01-01T00:00:00Z to 9999-12-31T23:59:59Z inclusive |
containerId STRING GTM Container ID |
containerVersionId STRING Represents a link to a container version |
description STRING The environment description. Can be set or changed only on USER type environments |
enableDebug BOOLEAN Whether or not to enable debug by default for the environment |
environmentId STRING GTM Environment ID uniquely identifies the GTM Environment |
fingerprint STRING The fingerprint of the GTM environment as computed at storage time. This value is recomputed whenever the environment is modified |
name STRING The environment display name. Can be set or changed only on USER type environments |
path STRING GTM Environment's API relative path |
tagManagerUrl STRING Auto generated link to the tag manager UI |
type ENUMERATION The type of this environment |
url STRING Default preview page url for the environment |
workspaceId STRING Represents a link to a quick preview of a workspace |
Output
This building block provides 17 output parameters
Name | Format | Description |
---|---|---|
accountId |
STRING |
GTM Account ID |
authorizationCode |
STRING |
The environment authorization code |
authorizationTimestamp |
OBJECT |
A Timestamp represents a point in time independent of any time zone or local calendar, encoded as a count of seconds and fractions of seconds at nanosecond resolution. The count is relative to an epoch at UTC midnight on January 1, 1970, in the proleptic Gregorian calendar which extends the Gregorian calendar backwards to year one. All minutes are 60 seconds long. Leap seconds are "smeared" so that no leap second table is needed for interpretation, using a 24-hour linear smear. The range is from 0001-01-01T00:00:00Z to 9999-12-31T23:59:59.999999999Z. By restricting to that range, we ensure that we can convert to and from RFC 3339 date strings. ExamplesExample 1: Compute Timestamp from POSIX Timestamp timestamp; timestamp.set_seconds(time(NULL)); timestamp.set_nanos(0); Example 2: Compute Timestamp from POSIX struct timeval tv; gettimeofday(&tv, NULL); Timestamp timestamp; timestamp.set_seconds(tv.tv_sec); timestamp.set_nanos(tv.tv_usec * 1000); Example 3: Compute Timestamp from Win32 FILETIME ft; GetSystemTimeAsFileTime(&ft); UINT64 ticks = (((UINT64)ft.dwHighDateTime) << 32) | ft.dwLowDateTime; // A Windows tick is 100 nanoseconds. Windows epoch 1601-01-01T00:00:00Z // is 11644473600 seconds before Unix epoch 1970-01-01T00:00:00Z. Timestamp timestamp; timestamp.set_seconds((INT64) ((ticks / 10000000) - 11644473600LL)); timestamp.set_nanos((INT32) ((ticks % 10000000) * 100)); Example 4: Compute Timestamp from Java long millis = System.currentTimeMillis(); Timestamp timestamp = Timestamp.newBuilder().setSeconds(millis / 1000) .setNanos((int) ((millis % 1000) * 1000000)).build(); Example 5: Compute Timestamp from current time in Python. timestamp = Timestamp() timestamp.GetCurrentTime() JSON MappingIn JSON format, the Timestamp type is encoded as a string in the RFC 3339 format. That is, the format is "{year}-{month}-{day}T{hour}:{min}:{sec}[.{frac_sec}]Z" where {year} is always expressed using four digits while {month}, {day}, {hour}, {min}, and {sec} are zero-padded to two digits each. The fractional seconds, which can go up to 9 digits (i.e. up to 1 nanosecond resolution), are optional. The "Z" suffix indicates the timezone ("UTC"); the timezone is required. A proto3 JSON serializer should always use UTC (as indicated by "Z") when printing the Timestamp type and a proto3 JSON parser should be able to accept both UTC and other timezones (as indicated by an offset). For example, "2017-01-15T01:30:15.01Z" encodes 15.01 seconds past 01:30 UTC on January 15, 2017. In JavaScript, one can convert a Date object to this format using the standard toISOString() method. In Python, a standard |
authorizationTimestamp.nanos |
INTEGER |
Non-negative fractions of a second at nanosecond resolution. Negative second values with fractions must still have non-negative nanos values that count forward in time. Must be from 0 to 999,999,999 inclusive |
authorizationTimestamp.seconds |
INTEGER |
Represents seconds of UTC time since Unix epoch 1970-01-01T00:00:00Z. Must be from 0001-01-01T00:00:00Z to 9999-12-31T23:59:59Z inclusive |
containerId |
STRING |
GTM Container ID |
containerVersionId |
STRING |
Represents a link to a container version |
description |
STRING |
The environment description. Can be set or changed only on USER type environments |
enableDebug |
BOOLEAN |
Whether or not to enable debug by default for the environment |
environmentId |
STRING |
GTM Environment ID uniquely identifies the GTM Environment |
fingerprint |
STRING |
The fingerprint of the GTM environment as computed at storage time. This value is recomputed whenever the environment is modified |
name |
STRING |
The environment display name. Can be set or changed only on USER type environments |
path |
STRING |
GTM Environment's API relative path |
tagManagerUrl |
STRING |
Auto generated link to the tag manager UI |
type |
ENUMERATION |
The type of this environment |
url |
STRING |
Default preview page url for the environment |
workspaceId |
STRING |
Represents a link to a quick preview of a workspace |
= Parameter name
= Format
accountId STRING GTM Account ID |
authorizationCode STRING The environment authorization code |
authorizationTimestamp OBJECT A Timestamp represents a point in time independent of any time zone or local calendar, encoded as a count of seconds and fractions of seconds at nanosecond resolution. The count is relative to an epoch at UTC midnight on January 1, 1970, in the proleptic Gregorian calendar which extends the Gregorian calendar backwards to year one. All minutes are 60 seconds long. Leap seconds are "smeared" so that no leap second table is needed for interpretation, using a 24-hour linear smear. The range is from 0001-01-01T00:00:00Z to 9999-12-31T23:59:59.999999999Z. By restricting to that range, we ensure that we can convert to and from RFC 3339 date strings. ExamplesExample 1: Compute Timestamp from POSIX Timestamp timestamp; timestamp.set_seconds(time(NULL)); timestamp.set_nanos(0); Example 2: Compute Timestamp from POSIX struct timeval tv; gettimeofday(&tv, NULL); Timestamp timestamp; timestamp.set_seconds(tv.tv_sec); timestamp.set_nanos(tv.tv_usec * 1000); Example 3: Compute Timestamp from Win32 FILETIME ft; GetSystemTimeAsFileTime(&ft); UINT64 ticks = (((UINT64)ft.dwHighDateTime) << 32) | ft.dwLowDateTime; // A Windows tick is 100 nanoseconds. Windows epoch 1601-01-01T00:00:00Z // is 11644473600 seconds before Unix epoch 1970-01-01T00:00:00Z. Timestamp timestamp; timestamp.set_seconds((INT64) ((ticks / 10000000) - 11644473600LL)); timestamp.set_nanos((INT32) ((ticks % 10000000) * 100)); Example 4: Compute Timestamp from Java long millis = System.currentTimeMillis(); Timestamp timestamp = Timestamp.newBuilder().setSeconds(millis / 1000) .setNanos((int) ((millis % 1000) * 1000000)).build(); Example 5: Compute Timestamp from current time in Python. timestamp = Timestamp() timestamp.GetCurrentTime() JSON MappingIn JSON format, the Timestamp type is encoded as a string in the RFC 3339 format. That is, the format is "{year}-{month}-{day}T{hour}:{min}:{sec}[.{frac_sec}]Z" where {year} is always expressed using four digits while {month}, {day}, {hour}, {min}, and {sec} are zero-padded to two digits each. The fractional seconds, which can go up to 9 digits (i.e. up to 1 nanosecond resolution), are optional. The "Z" suffix indicates the timezone ("UTC"); the timezone is required. A proto3 JSON serializer should always use UTC (as indicated by "Z") when printing the Timestamp type and a proto3 JSON parser should be able to accept both UTC and other timezones (as indicated by an offset). For example, "2017-01-15T01:30:15.01Z" encodes 15.01 seconds past 01:30 UTC on January 15, 2017. In JavaScript, one can convert a Date object to this format using the standard toISOString() method. In Python, a standard |
authorizationTimestamp.nanos INTEGER Non-negative fractions of a second at nanosecond resolution. Negative second values with fractions must still have non-negative nanos values that count forward in time. Must be from 0 to 999,999,999 inclusive |
authorizationTimestamp.seconds INTEGER Represents seconds of UTC time since Unix epoch 1970-01-01T00:00:00Z. Must be from 0001-01-01T00:00:00Z to 9999-12-31T23:59:59Z inclusive |
containerId STRING GTM Container ID |
containerVersionId STRING Represents a link to a container version |
description STRING The environment description. Can be set or changed only on USER type environments |
enableDebug BOOLEAN Whether or not to enable debug by default for the environment |
environmentId STRING GTM Environment ID uniquely identifies the GTM Environment |
fingerprint STRING The fingerprint of the GTM environment as computed at storage time. This value is recomputed whenever the environment is modified |
name STRING The environment display name. Can be set or changed only on USER type environments |
path STRING GTM Environment's API relative path |
tagManagerUrl STRING Auto generated link to the tag manager UI |
type ENUMERATION The type of this environment |
url STRING Default preview page url for the environment |
workspaceId STRING Represents a link to a quick preview of a workspace |