---
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


---

# Personalize domains for push connector events to use in event creation

# Personalize domains for push connector events to use in event creation {#ariaid-title1}

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

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.

## Before you begin

Make sure that you have the following setup:  
* You have read access to the domain information table for the evt_mgmt_integration role (default table: core_company). For more information, see [Configure an ACL rule](https://www.servicenow.com/docs/access?context=t_CreateAnACLRule&version=yokohama&pubname=yokohama-platform-security&ft:locale=en-US).
* You enabled the evt_mgmt.connector_enable_custom_domain_separation .system property.
* You installed the following plug-ins in the ServiceNow AI Platform® instance:
  * Event Management (com.glideapp.itom.snac)
  * Event Management connectors (sn_em_connector)
  * Domain Support - Domain Extensions Installer (com.glide.domain.msp_extensions.installer)

    You
    can download the plug-ins from the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do).
  {#personalize-domain-separation-push-connectors__ul_d3q_5mh_11c}
{#personalize-domain-separation-push-connectors__ul_rmd_y4v_mxb}Role required: evt_mgmt_admin

## Procedure

1. Navigate to AllEvent ManagementIntegrationsPush Connectors.
2. Open a push connector.
3. On the Push Connector screen, scroll down to the Push Connector Configurations list and select New.  
   Note:  
   If this list is not displayed, you must create a push connector configuration parameter. For more information, see [Create a push connector configuration parameter](https://servicenow-prod.fluidtopics.net/vUCePFSHBi2Miq~~qtqgZg "Some connectors have no parameters that are shipped out of the box. Therefore, it’s necessary to create and add the parameter to the push connector configurations list in the form layout before adding the new parameter.").
4. In the Push Connector Configurations screen, determine whether events should be created in the provided domain or the domain provided in the payload of each event.

   | Domain creation location | Parameter and values |
   | The provided domain | * Field name: payloadDomainInfoFieldValue * Value: domain-identifier {#personalize-domain-separation-push-connectors__ul_stq_3cc_d1c} |
   | The domain provided in the payload of each event | * Field name: payloadDomainInfoFieldName * Value: field-name-in-payload {#personalize-domain-separation-push-connectors__ul_z3g_kcc_d1c} Example: If the payload key "company" holds the domain identifier, then "company" is the value. "company" :   { :   "source": "Solarwinds", :   "host": "127.0.0.1", :   "company": "ServiceNow" :   } |
   |-|-|

   {#personalize-domain-separation-push-connectors__choicetable_jm5_rmb_d1c}  
   Note:  
   If both the payloadDomainInfoFieldValue and the payloadDomainInfoFieldName parameters are provided, then the payloadDomainInfoFieldName takes precedence.
5. Select Submit.

## Result

Events are created in the domain referred to by the domain identifier.  
Note:  
The table that stores domain information records (for example, core_company) must be domain separated. For more information, see [Domain-separate a custom table](https://www.servicenow.com/docs/access?context=bp-ds-custom-table&version=yokohama&pubname=yokohama-platform-security&ft:locale=en-US).
**Related tasks**   

* [Integrate with push connectors](https://servicenow-prod.fluidtopics.net/fflpxkIq3CsQDAbBfe7dxA "Integrate with a push connector to connect to an external event source. Push connectors process the collected event messages and transform them to the required event format.")  
**Related reference**   

* [Connector domain metadata](https://servicenow-prod.fluidtopics.net/Qs2PfJVVK_uXIWfzu3ImOw "Override push connector default domain metadata values installed with Event Management with the values in the event HTTP request, including the URL, headers, request body (payload), and connector parameters. Override pull connector domain metadata values with connector parameters only.")

*[\>]: and then