What are the best practices for custom tags?

When you tag a product with a custom tag, it allows your organization to classify products in meaningful ways. Tags improve your users’ search capability and can help organizations generate targeted lists of tools for your educators. 

When classifying products, using custom tags make it easier to find them in your product library. It also becomes easier to group and associate products with initiatives from your organization.

This guide includes sample case studies to help you consider how to best incorporate custom tags into your overall edtech management process.

Note: To create or manage custom tags as an administrator, learn how to use, add, and configure product tags.

Case Studies


Tag Type Case Study
Program-specific tools
  • Identify edtech tools used or associated with a specific program.
 Springfield School District has a career preparedness program called the Career-Ready Educational Development System (CREDS).

Springfield tags all supporting tools with CREDS. Participants and educators now have a current, targeted list by searching CREDS in their product library.
Grant-supported tools
  • Identify when product subscriptions are paid or supported by specific grants.
  • Users can easily search grant tag to view resources.
 A North Carolina District participates in the GROW Grant and receives assistance with Pre-Kindergarten targeted tools.

This district tags products with GROW Grant to return all qualifying edtech tools when a parent or educator searches the grant.
School-specific tools
  • Districts can maintain a comprehensive org library, and create school associations for particular products.
  • Identify products utilized by a specific school.

 A district in Utah, with five member schools, set up their organization library for all of their five member schools. They also wanted each user to have visibility of tools specific to their own school (elementary, middle, or high school).

They tagged all tools available for Newman Elementary with the Newman tag/badge so that searching for Newman would return all tools in use by that school.

The custom tags included the individual school logos for a visual association.
Security or privacy-related tags
  • Identify any tools that have passed a security scan or have unique privacy considerations.
 A district will not allow tools in their library if they collect more than two pieces of PII. This district tags the products that do not meet this requirement with No Go.

Other products have murky privacy policies. The district tags these with Use With Caution.
IT support levels
  • Districts indicate the level of IT support with custom tags.
 Districts can leverage their policies indicating how much support they are willing or able to provide for certain products. A district uses a color-coded tag badge (red, yellow, and green) to indicate whether the IT team provides full, partial, or no support for that tool.
Pedagogical methods
  • Schools can tag their pedagogical approach to a tool with custom tags.
 Clarkson County uses Headspace among others as a supporting tool for socio-emotional learning. They tag Headspace with Socio-Emotional and when parents search for this method, they get more context of how their child is taught and what tools are being used.

System tags are already associated with edtech tools, and are assigned by product providers or LearnPlatform. These tags cannot be removed, but they can be hidden.

View Custom Tags

View Custom Tags

To find products associated with custom tags, view your organization's product library and enter the tag in the Search field [1]. Any products with that custom tag display in the search results [2]. To view the badge and product information, hover your cursor over the product tile and click the Details link [3].

You can also filter products by custom tags in the library by clicking the filter options [4].