Roll out a Community Template tag to every container

Why template tags are copied, not created

Many vendor tags come from GTM's Community Template Gallery, not from the built-in tag types. A template is installed separately in each container, and a tag built on it depends on that installed copy. That is why the Create form doesn't offer gallery templates. Instead, you configure the tag once in one container and copy it to the rest.

So the first step happens in GTM. Install the template in one container, configure and test the tag, and publish it. That container becomes your source.

Copy the tag and let the template follow

Extract the source brand, select the template tag and press Copy to…. Choose the target containers and keep Include its triggers and variables on, so the tag arrives with its triggering and any variables its fields use.

For each target container, the preview shows what will happen to the template:

• Missing: the template is installed in the target, shown as installs template Vendor Pixel.
• Already present: the same gallery template, or a template with the same name, is reused and not installed twice.

Template variables travel the same way: copy them, and their template follows.

Check the template in GTM before publishing

A template runs code a third party wrote, so treat each installed copy as part of the review:

• Permissions. In each container's Templates section, read what the template is allowed to inject, send or read.
• Gallery version. The source container's template may be older or newer than the gallery's latest. Decide which version you want everywhere.
• Consent settings. They come across from the source tag. Confirm they fit each brand's consent set-up.
• Preview mode. Check that the tag fires once and sends what the vendor expects, in each brand, before you publish.

Keep going

• Copy a working setup from one brand to the rest
• Swap a vendor tag across brands in one batch
• Google: Community Template Gallery