# getTagManager() and getClientTagProvider() usage in CLIENT scope

**URL:** <https://forum.inductiveautomation.com/t/gettagmanager-and-getclienttagprovider-usage-in-client-scope/24992>\
**Category:** Module Development\
**Tags:** ignition80\
**Created:** [May 14, 2019, 4:59pm UTC](https://forum.inductiveautomation.com/t/gettagmanager-and-getclienttagprovider-usage-in-client-scope/24992 "2019-05-14T16:59:53Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![mazeyrat](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mazeyrat/32/10955_2.png) [@mazeyrat](https://forum.inductiveautomation.com/u/mazeyrat)\
**Post date:** [May 14, 2019, 4:59pm UTC](https://forum.inductiveautomation.com/t/gettagmanager-and-getclienttagprovider-usage-in-client-scope/24992/1 "2019-05-14T16:59:53Z")

</div>

In the client scope we have :

```auto
clientContext.getTagManager().getClientTagProvider(<name>).getTagConfigsAsync(...)

```

the name parameter is the name of the gateway tag’s provider ? or is the name of the client tag’s provider ???

```auto
clientContext.getTagManager().getTagConfigsAsync(...)

```

does this function use “default” tag’s provider or “client” tag ?

```auto
gatewayContext.getTagManager().getTagProvider(<name>).getTagConfigsAsync(...)

```

this function is for the gateway tag’s provider “name”.