TAG Mapping: What do you need to consider?

To ensure we can prepare your integration quickly and avoid follow-up questions, it’s important that you think about TAG mapping in advance.

In keelearning, TAGs are the central element for organizing your users and controlling access to content. 

What are TAGs used for?

The primary purpose of TAGs is access management for courses and content. In a course’s settings, you define via “TAG assignment” which user group (e.g. “Sales” or “Location Berlin”) can see the course in your app. In addition, TAGs enable you to:

• Targeted reporting: Use filters to view statistics and reports for specific TAG groups.
• Individual communication: Send push notifications or emails to specific user groups.
• Automation: Use TAGs to automatically unlock new content after a course has been completed.

Automatic TAG mapping via interfaces

When connecting external systems (such as HR software), we can define rules according to which TAGs are automatically created and assigned in keelearning.

Standard package:
Our standard interface package includes mapping organizational attributes such as departments, cost centers, or business units directly as TAGs in keelearning. This ensures that your learning platform always reflects your current organizational structure. If you have additional ideas about which data from your HR system should be represented as TAGs, feel free to contact us!

What we need from you for TAG mapping

To set up the interface in the best possible way, we need the following information from you:

1. A clear rule: We need to know the logic according to which TAGs should be created (e.g. “Department_Name”).
2. Data access & authorization: A way to locate the relevant data in your HR system, as well as the technical permission to read it.
3. Technical details: Ideally, please provide us with an API endpoint and/or the specific field ID.

You can easily share this information with us via our technical checklist.

Alternative: Meta fields for personal data

Not all information from your systems needs to exist as TAGs. Data that is not required to control course access can be transferred as meta fields instead. Meta fields are always assigned directly to an individual user and are ideal for:

• Employee ID numbers
• Assigned manager / supervisor
• Start and end dates of employment

These fields do not appear in the TAG selection for course access, but can be viewed in User Management.