# Gateway tag overload. How to not subscribe to all tags **URL:** \ **Category:** Ignition\ **Tags:** ignition81, perspective\ **Created:** [April 29, 2025, 9:49pm UTC](https://forum.inductiveautomation.com/t/gateway-tag-overload-how-to-not-subscribe-to-all-tags/105710 "2025-04-29T21:49:35Z")\ **Posts on this page:** 1\ **Showing post:** 6
**Author:** ![ryan.white](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ryan.white/32/73193_2.png) [@ryan.white](https://forum.inductiveautomation.com/u/ryan.white)\ **Post date:** [April 29, 2025, 10:29pm UTC](https://forum.inductiveautomation.com/t/gateway-tag-overload-how-to-not-subscribe-to-all-tags/105710/6 "2025-04-29T22:29:27Z")
You can use this import tool from the exchange: > **[Ignition Exchange](https://inductiveautomation.com/exchange/2660/overview)** > > Discover, share, and download community made Ignition resources in collaboration with your organization or the Ignition community. or you can script the creation of tags/udts using [`system.tag.configure`](https://www.docs.inductiveautomation.com/docs/8.1/appendix/scripting-functions/system-tag/system-tag-configure) Good advice from a different thread on optimizing on PLC side: > [@Ignition & Logix Best Practice Tips for better communications](https://forum.inductiveautomation.com/t/ignition-logix-best-practice-tips-for-better-communications/60386/3): > > Consolidate scattered tag instances into arrays or nest them in structures. The fundamental unit of optimization when polling is the tag. Multiple items won’t be in consecutive memory locations, and therefore be retrievable together, unless they are part of the same tag. If you must, you can use aliases in the PLC to retain the prior logical structure, but access from Ignition via the consolidated tag(s). --- _[View the full topic](https://forum.inductiveautomation.com/t/gateway-tag-overload-how-to-not-subscribe-to-all-tags/105710)._