What must container_id be set to when interacting with custom elements via the APIs?

When interacting with custom elements via the APIs, setting the container_id to tenant is essential because it defines the scope of the custom elements within the context of a specific tenant in the Adobe Experience Platform. Each tenant represents a separate environment and set of resources, ensuring that the interactions and data associated with custom elements are uniquely identified and managed within that tenant.

This approach enables clear separation of data and configurations across different tenants, preventing overlap and potential data conflicts. By using the tenant identifier, you ensure that any modifications or interactions are confined to the intended scope, allowing for better organization and security of the resources.

In contrast, other identifiers such as global, user, or admin do not accurately represent the necessary context for managing custom elements through the APIs. Global may imply a broader scope that isn't applicable to tenant-specific interactions. User and admin could reference individual user settings or administrative privileges rather than the tenant-specific environment needed for properly managing custom elements.