Create the same tag, trigger or variable in every brand at once

When to create, and when to copy

Both Create and Copy put the same item into many containers in one batch. Which one to use depends on where the item comes from:

• Create when the item is one of GTM's built-in types and doesn't exist in any of your containers yet, for example a new GA4 event for a lead form you are launching everywhere.
• Copy when the item already works in one container, or when it is a type the form doesn't cover: Community Template tags and variables, Trigger Groups and YouTube Video triggers. See Copy a working setup from one brand to the rest.

If in doubt, build it once in one container with Create, test it there, and then copy it to the rest.

Open the form and choose the type

Extract the brands that need the item first; the extract supplies the target containers. Then use + New tag, + New trigger or + New variable above the table. A drawer opens and follows GTM's own editor:

1. Name, using your naming convention. This same name will exist in every target container.
2. Type, from GTM's grouped picker, with the same names and categories as GTM. Tags are grouped under Google Analytics, Google Ads & Marketing Platform and Custom. Triggers are grouped under Page View, Click, User Engagement and Other. Variables are grouped under Navigation, Page Variables, Page Elements and Utilities.
3. Configuration, the type's own fields with GTM's labels and defaults. Required fields are marked, and the form won't add an item with one missing.
4. Notes (optional). A good place for the ticket or brief reference.

You can type a {{Variable}} reference into any field that accepts one, just as in GTM.

Triggering by name

A new tag picks its firing triggers and exceptions by name, because the same trigger has a different internal ID in every container. The picker lists every trigger name found in the target containers, plus triggers you are creating in the same batch.

When a name exists in only some targets, the picker says so, for example in 6 of 8 targets. The tag will be created in the six containers that have that trigger. The other two will be skipped, and the preview will say why. Under Advanced: Tag firing option you can choose once per event, once per page or unlimited.

Creating a trigger works the same way. Choose the type, then set its Trigger conditions with Add condition: a variable, an operator and a value, as in GTM. A Custom Event trigger also takes its Event name.

Choose the target containers

Under Targets, tick every container that should get the item. They are grouped by GTM account.

• On Free, targets are limited to one GTM account. You can still tick every container in it.
• On Premium, you can target containers across accounts.

Press Add to batch. The item appears in the table as a new pending row in each target container. Until you apply, each row can be reviewed and removed independently. Select a row and press Revert to drop it.

Build a complete set in one batch

Most real launches need more than one item. Say you are adding lead tracking to eight brands. You can stage the whole set in one batch:

1. New variable: Data Layer Variable DLV - form_id, reading form_id. Target all eight containers.
2. New trigger: Custom Event CE - generate_lead, with event name generate_lead. Target all eight.
3. New tag: Google Analytics: GA4 Event GA4 - Event - generate_lead. Event name generate_lead, a parameter form_id = {{DLV - form_id}}, firing on CE - generate_lead. Target all eight.

When you apply, each container gets the variable first, then the trigger, then the tag. The tag can rely on items created moments earlier in the same batch. That is 24 items in eight workspaces, from one review.

When a brand is missing a trigger or variable

Brands rarely match perfectly. If a target container has no trigger with a name your tag uses, or no variable your configuration references, ODDVX doesn't guess. That container's item is skipped, with the reason in the preview, for example trigger "CE - generate_lead" not found. The other containers still go ahead.

To close the gap, do one of these:

• Add the missing trigger or variable to the same batch, targeting the brands that lack it.
• Apply what you can now, add the missing item, and run the batch again. Items that already landed are skipped as already existing.

Built-in variables are switched on where needed

If your new item uses a GTM built-in variable, such as {{Click Classes}} or {{Page Path}}, and a target container hasn't enabled it, ODDVX enables it in that container's workspace. The preview lists each one, for example enables {{Click Classes}}, so nothing is switched on without you seeing it.

What the form doesn't cover

The Create form covers GTM's common built-in types. Some things it deliberately leaves out:

• Trigger Groups and YouTube Video triggers. Copy them from a container that has them.
• Community Template tags and variables. Copy them; the template is installed where it is missing. See Roll out a Community Template tag.
• Consent settings. Set them in GTM, or copy a tag that already has them.
• Folders and tag sequencing. New items land at the container root.

Nothing is written until Review & apply, and nothing is published by ODDVX.

Keep going

• Use case: build once, stage it in every brand
• Copy a working setup from one brand to the rest
• Workspaces, publishing and recovery