---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Event Management Connectors domain personalization

# Event Management Connectors domain personalization {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Create events in different domains for all Event Management connectors using just a single connector instance by personalizing domain separation of Event Management connectors.

## How the domain is identified {#domain-separation-connectors-personalization__section_sr5_nhv_1zb}

In a ServiceNow instance, events are created within the logged-in or MID Server user domains. However, you can create events in a different domain by providing metadata values in the event HTTP request, including the URL, headers, request body (payload), and connector parameters.

The logged-in user or the MID Server user must have access to the provided domain. The connector resolves the domain based on the provided identifier and creates events in that domain.

System properties provide the default metadata that sets the domain-separated table to identify the domain. For more information, see [Domain properties installed with Event Management](https://servicenow-prod.fluidtopics.net/RkUUNo5voYrcx_n1eqvTPQ "Use the domain properties installed with Event Management to provide the metadata that points to the appropriate table to identify the domain so that you know which domain to create the event in.").

## Connector Exceptions {#domain-separation-connectors-personalization__section_zcx_ggv_1zb}

You cannot personalize domain separation for the following pull connectors:

* SCOM
* IBM Netcool (supports only IBM Netcool_v2)
* HPOM
* Hyperic
{#domain-separation-connectors-personalization__ul_c45_zrv_mxb}  
You cannot personalize domain separation for the following push connectors:

* SAP SolMan Transform Script
* bmcTrueSight Transform Script
* Transform Generic Events MID
* TransformEvents_xmlSample
{#domain-separation-connectors-personalization__ul_xw2_nrv_mxb}
* **[Personalize domains for pull connector events to use in event creation](https://servicenow-prod.fluidtopics.net/klCp5FpyBBkIiKsGadcL4g)**   
  Configure pull connectors to personalize domain separation of events so you can use them to create events in domains other than the user's currently logged-in or MID Server domain.
* **[Personalize domains for push connector events to use in event creation](https://servicenow-prod.fluidtopics.net/GhlIHsoZJgiwZOyDwBURBg)**   
  Configure push connectors to personalize domain separation of events so you can use them to create events in different domains other than the user's currently logged-in or MID Server domain.

**Related concepts**   

* [Domain separation and Event Management](https://servicenow-prod.fluidtopics.net/_GZvkGj4nmU8IHZyWBZIqw "Domain separation is supported in Event Management. Domain separation enables you to separate data, processes, and administrative tasks into logical groupings called domains. You can control several aspects of this separation, including which users can see and access data.")