---
sourceDocument: Xanadu IT Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/xanadu/it-operations-management

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Connector domain metadata

# Connector domain metadata {#ariaid-title1}

* Release version: Xanadu
* 
* Updated August 1, 2024
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

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.

## Domain metadata parameters {#connector-domain-metadata__section_mvv_kjg_1yb}

{#connector-domain-metadata__table_dyj_4jg_1yb__entry__3}

| Name | Description | Overrides System Property |
|-|-|-|
| connectorDomainInfoTableName | Name of the table containing the records with the domain information. | evt_mgmt.connector_domain_info_table_name * Type: string * Default value: core_company {#connector-domain-metadata__ul_z4f_bv2_lzb} |
| connectorDomainInfoColumnName | Name of the column that has a value that should be matched with the domain identifier. For example, you might want to identify a record in the Domain Info table that has a matching value in the company_name field. | evt_mgmt.connector_domain_info_column_name * Type: string * Default value: name {#connector-domain-metadata__ul_zdw_dv2_lzb} |
| connectorDomainIdColumnName | Name of the table column that stores the domain ID. | evt_mgmt.connector_domain_id_column_name * Type: string * Default value: sys_domain {#connector-domain-metadata__ul_lyd_2v2_lzb} |
| connectorDomainPathColumnName | Name of the table column that stores the domain path. | evt_mgmt.connector_domain_path_column_name * Type: string * Default value: sys_domain_path {#connector-domain-metadata__ul_mbr_2v2_lzb} |
[ ]

{#connector-domain-metadata__table_dyj_4jg_1yb}

## Order of preference for accessing domain metadata {#connector-domain-metadata__section_x3y_jbg_1yb}

You must provide domain metadata to configure personalized push connector domains. The metadata in preferred accessing order are:

1. Push connector parameters
2. URL query parameters
3. HTTP headers
4. Request body (payload)
5. Default system properties
{#connector-domain-metadata__ol_fnd_pbg_1yb}

## URL query parameters {#connector-domain-metadata__section_w42_rtl_1yb}

Push connectors have the following URL syntax:

* Instance Type: `https://<instance-name>.service-now.com/api/sn_em_connector/em/inbound_event?source=<connector-source>`
* MID Server type: `http://<MID_Server_IP>:<MID_Web_Server_Port>/api/mid/em/inbound_event?Transform=<connector-transform-script-name>`

{#connector-domain-metadata__ul_nvj_vfm_1yb}

You can include domain metadata as additional query parameters in the ServiceNow push connector webhook URL. For example, if the domain information source is the sys_user table, the URL could be
`https://<instance-name>.service-now.com/api/sn_em_connector/em/inbound_event?source=<connector-source>&connectorDomainInfoTableName=sys_user`

## Request headers {#connector-domain-metadata__section_ahr_jqn_1yb}

Any of the domain metadata properties can be passed as part of HTTP request headers. Check the documentation from your third-party monitoring tool for information about how request headers are set.

## Request body (payload) {#connector-domain-metadata__section_rcd_5rn_1yb}

You can reference domain metadata from the request body (JSON payload) by setting the metadata parameters as root-level keys in the payload. The following example shows how the connectorDomainInfoTableName and connectorDomainInfoColumnName parameters might be passed as part of the request body:

{
:   "source": "Azure Monitor",
:   "host": "127.0.0.1",
:   "company": "ServiceNow",
:   "connectorDomainInfoTableName": "sys_user",
:   "connectorDomainInfoColumnName": "first_name"
:   }
{#connector-domain-metadata__parml_wpf_f4c_5xb}  
Note:  
For information on connector parameters, see [Personalize domains for push connector events to use in event creation](https://www.servicenow.com/docs/CJ0bx7yll3Q9I4vl8XRFhQ "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.").