The Google Tag Manager logo is the interlocking double-diamond mark Google uses for its tag management product. It shows that Tag Manager, a tool that lets you deploy tags on a site or app from a web interface instead of editing code, is attached to a page. It is not proof that your tracking works.
This page does three things fast: it helps you confirm you are looking at the right mark, points you to the official place to get a licensed copy, and explains what each version of that icon tells you. The goal is that you never have to bounce between five pages to identify a logo or check a container.
The path in 5 steps
The steps of this page, in order.
-
01 Identify the mark Confirm the icon you saw is the GTM double-diamond and not a related Google product.
-
02 Get the asset Download the format you need from an official source with clear usage terms.
-
03 Read the context Work out which screen you saw it on and what state that screen represents.
-
04 Verify tracking Use Tag Assistant and Preview mode to confirm tags actually fire.
-
05 Decide and publish Fix or publish the container, then re-check before going live.
01 / 09
What does the Google Tag Manager logo look like?
It is an interlocking double-diamond mark in Google's blue-to-teal gradient, paired with the words "Google Tag Manager" in the official lockup.
Read the shape first: two diamonds joined at a point, like a tilted figure eight. A single diamond in that blue-to-teal gradient, or the plain Google "G", is a different product mark. On a container list, a mark sitting beside an ID that starts with GTM- is almost certainly Tag Manager.
The mark ships in two forms: the standalone icon, and the full lockup with the product name. Use the lockup in a slide title or a docs heading, and the icon alone where space is tight, such as a 32-pixel favicon slot.
The standalone icon
The double-diamond mark on its own, with no words attached. It is the version you place in tight, square spaces where a full product name would be unreadable.
- Shape
- Two interlocking diamonds
- Use case
- Favicon, app tile, icon row
Key pointSave the icon as a square file and check it still reads at 32 pixels.
The full lockup
The mark paired with "Google Tag Manager" in the official typeface, with fixed spacing between the two parts. It is the version intended for headings, title slides and documentation covers.
- Shape
- Mark plus product name
- Use case
- Slide titles, docs headers
Key pointNever retype or re-space the name; take the lockup as one image.
Not this one
The Google "G" and the GA4 mark belong to other products. Seeing either next to a tag list tells you nothing about Tag Manager specifically, because those marks are shared across Google's broader product set.
- Shape
- Single "G" or GA4 bars
- Use case
- Other Google products
Key pointMatch the mark to the product ID before you trust the association.
Going further
Why a separate mark?
Concept
Why Tag Manager has its own mark at all
Tag Manager carries its own mark because it is a separate product from Analytics and Ads, and Google uses distinct marks to tell them apart in shared interfaces.
Google Marketing Platform bundles several products that a single team often touches on the same day: Analytics for measurement, Ads for campaigns, Tag Manager for deploying and organizing the tags that feed the others. A shared "G" would blur which product a container list, permission screen or billing line actually refers to, so each carries its own mark.
That is why the mark is a useful diagnostic, not decoration. When you see the double-diamond next to an item, the surrounding text is naming Tag Manager as the product in play, not Analytics and not the wider Google account.
- Shape checkInterlocking double diamond, not a single diamond and not the Google "G".
- Color checkBlue-to-teal gradient, not flat single-color.
- Context checkLook for a nearby ID starting with GTM- before assuming Tag Manager.
- Product checkGA4 and Google Ads marks are separate products and mean something different on screen.
02 / 09
Where do I get an official copy I can use?
Get it from Google's own brand resources, not from a third-party icon site, then read the usage terms before you publish it.
Start at Google's brand resource center (about.google/brand-resource-center): that is where the current Tag Manager mark, its file formats, and the terms that govern use live. A product page such as tagmanager.google.com may host its own asset copy; treat that as the canonical source too.
Third-party icon libraries (SVGrepo, uxwing, GitHub repos) can hand you a file in seconds, but their license covers the file, not Google's trademark. Downloading there gives you no permission to use the mark, especially for client work or anything that could imply Google endorsement.
-
Open Google's brand resource center
Go to about.google/brand-resource-center and search for Tag Manager. That page, not a third-party repo, is where the current mark and its terms live.
-
Find the Tag Manager listing
Locate the Tag Manager entry and confirm it is the product mark you need, not a generic Google 'G'.
-
Pick the format
Download the asset in the format that fits your surface. Google typically offers SVG for UI and PNG for documents.
-
Read the usage terms before publishing
Check the brand terms on that same page. For client decks, dashboards, or anything that implies a partnership, use the mark without decorative styling and link to the Tag Manager product page instead of suggesting endorsement.
Going further
Asset sources compared
Rule to know
Official assets vs. icon libraries
Official Google assets come with a clear license path; third-party libraries give you a file but never the trademark rights.
Google's brand resource center publishes the marks it owns and the rules for using them. That is the only place where the current Tag Manager logo, its file formats, and its permission terms are stated together. A repost on an icon site is a copy of the file, not a grant of rights.
Icon libraries such as SVGrepo or uxwing operate under their own licenses, which cover the file itself. They do not extend Google's trademark rights to you. If you use their copy on a client site or in a sales deck, you are relying on a license that does not exist for that purpose.
The practical split: use official Google assets when you need a clean, licensed version of the mark for a legitimate reference; use third-party icons only when the context is internal and no trademark claim is implied. When the use is commercial or client-facing, check Google's brand terms first.
- SourceConfirm the asset came from Google's brand resource center or the Tag Manager product page, not a third-party library.
- TermsRead the usage terms on the same page you downloaded from; they govern the mark, not just the file.
- Implied endorsementIf the placement could suggest a partnership with Google, link to the product page instead of styling the mark as a badge.
- Date checkedNote when you last verified the page, because brand resources and terms can change.
03 / 09
SVG, PNG or WebP: which file should I use?
Use SVG for anything that scales, and fall back to PNG or WebP only when a platform refuses vector files.
SVG is vector data, so the diamond stays sharp at any size, web headers, docs, slide decks, resizable dashboards. A PNG is a fixed grid of pixels: fine at its export size, soft the moment anything scales it up.
WebP is the better raster pick when you need transparency and a small file. Keep one PNG for older email and document tools that reject both SVG and WebP, that fallback order covers almost every situation.
Which GTM logo file to use, and where it fails
| Format | Best use | Where it breaks down |
|---|---|---|
| SVG | Logos in site headers, docs, slide decks, resizable dashboards, any size, stays crisp | Some email clients and older document tools refuse to render vector files |
| PNG | Fixed-size placements: email signatures, printed handouts, tools that only accept raster | Scales up and the diamond edges go soft, visible on retina screens and zoomed dashboards |
| WebP | Web placements needing transparency at a small file size | Not accepted by some older email clients and document editors |
Vector first; raster only when a platform forces it. No pricing involved, these are format choices, not licensing decisions.
Going further
Format swap steps
Method
How to swap formats without losing the edges
The order matters: start from the vector master, then export one raster per size, so nothing is ever scaled up from a bad source.
Export once from the vector file and let the raster be a byproduct. If you begin from a PNG and scale it up, every later step inherits the blur. Keep the SVG as your master, name it clearly, and store it where the team can find it.
For each destination, pick the smallest raster that covers the largest on-screen size it will ever hit. A dashboard tile rendered at 96px does not need a 1024px PNG. A retina display doubles the pixel requirement, so a 48px slot wants a 96px raster at minimum.
Fallback order that works in practice: SVG first, WebP second for web with transparency, PNG last for email and documents. When a tool rejects a format, drop one step down the list rather than resizing what you already have.
- Vector masterKeep the original SVG as the single source; export every raster from it, never from another raster.
- Pixel budgetMatch raster dimensions to the largest slot the file will fill, doubled for retina screens.
- Fallback orderSVG → WebP → PNG. If a platform refuses a format, step down rather than upscaling.
- Edge testZoom a dashboard tile to 200% and confirm the diamond edges stay straight before shipping.
04 / 09
I saw the icon somewhere, what does it mean there?
The same mark means different things depending on the screen it sits on, so the location is the signal, not the logo.
Treat the mark as a status indicator, not a badge of correct setup. In your own workspace it names a container; in a browser extension list it means that add-on is active; on a site you are inspecting it usually means a Google Tag Manager container is loaded.
The implication shifts with the screen. A container you own but have not published, one loaded while tags are blocked by consent, and one loaded and firing are three different states, the icon looks identical in all three.
Where the GTM mark appears and what it implies
| Where you see it | What it shows | Tracking implication | What to check next |
|---|---|---|---|
| Google Tag Manager workspace (container list) | A named container in the account | No signal about live data, could be unpublished | Whether latest changes have been published |
| Browser extensions settings | Third-party add-on is installed and active | A tool is present, not proof of tag behavior | Extension permissions and last update |
| A site's source or admin toolbar | A container is loaded on the page | Page may send data, or not | Container ID matches the one you manage |
| Web panel from a consent tool | Container likely loaded but tags gated | Consent state governs which tags fire | Consent-mode or CMP configuration |
| Container detail page (tag list) | Tags inside a container | Tags configured, not necessarily triggered | Preview mode or Tag Assistant run |
Read location first, then assume nothing about live tracking.
05 / 09
Does the logo mean my tags are working?
No, it only tells you Tag Manager is attached; it says nothing about whether any tag fired.
The mark only means the container loaded. A published container can fire while every tag inside it is paused, blocked by a consent tool, or scoped to a trigger that never matches the page you are on. Seeing the icon is no evidence that a single hit reached your analytics.
Treat the logo as "the plumbing is connected," not as proof of measurement. The only evidence is the data that arrives in your analytics platform. Also keep official Google assets separate from third-party icon libraries: those sites license the file, not the Google trademark, so their terms do not grant you brand rights.
Container loaded, not tag fired
Open the browser console or Tag Assistant and confirm a network request actually left the page. The icon alone does not show this.
Paused tags inside the container
Check the container's Tags list for a paused status. A paused tag loads with the container but never executes.
Trigger scoped to another page
Read the trigger's condition. If it is limited to a path or event you did not visit, nothing fires, yet the container still loads.
Consent tool blocking the tag
If a consent management tool runs before GTM, it can suppress tags until the visitor accepts. Test with and without consent granted.
Data reaching your analytics
Look for the actual event or pageview in your analytics platform's real-time view. That arrival is the evidence, not the logo.
06 / 09
How do I actually check that tracking works?
Use Tag Assistant and container Preview mode, those two, not the logo, confirm a tag fired.
Tag Assistant shows which tags a page requested and flags common errors, making it the fastest public check on any site you can load in a browser. Preview mode in GTM loads your unpublished container so you can watch triggers fire event by event before you publish, Google's own guidance is to preview and debug first.
Once a tag fires correctly in Preview, publish and re-run the check on the live page: a published container behaves differently from a previewed one, so the two checks are not interchangeable.
-
Open Tag Assistant
Install the Tag Assistant Companion extension and start a recording on the page you want to inspect.
-
Load the page
Reload the page in the recorded tab and watch which tags Tag Assistant lists as requested.
-
Open Preview mode
In GTM, click Preview and connect it to the same page to load your unpublished container.
-
Watch the triggers fire
Click through the site and confirm each trigger and tag fires on the event you expect, event by event.
-
Publish and re-check
Publish the container, then reload the live page in Tag Assistant to confirm the tag still fires.
07 / 09
What should I do next?
Confirm the mark, grab the right file, then close the loop with a real verification before you publish.
If you came for the asset, download the SVG from Google's brand resources, keep a PNG fallback, and check the usage terms before it goes into client-facing work. If you were diagnosing, note which screen showed the mark, then run Tag Assistant and Preview the container. Fix what fails before publishing.
Write the container ID next to the check you ran, so the next person can repeat the verification instead of trusting the icon.
-
Confirm the mark
Match what you saw against the official Google Tag Manager logo: a blue tag manager symbol, not a third-party lookalike.
-
Get the right file
Pull the SVG from Google's brand resources, keep a PNG fallback, and review the usage terms before client-facing use.
-
Run Tag Assistant
Open Tag Assistant and load the page to see which tags fire and which fail.
-
Preview the container
Use Preview mode in Google Tag Manager to test the container on the live site and catch errors before publishing.
-
Record the check
Write down the container ID next to the tag or page you verified, so the next person can repeat the same test.
08 / 09
Frequently asked questions
09 / 09










