Global List Site Mapping

Last Updated: October 23, 2026

Global list site mapping is a feature that ensures that events are automatically created in the correct client site based on a unique identifier within the incoming raw ingestion data. This ensures proper site-level segregation, making events accessible only within their assigned site.

To enable this mapping, the integration connection must be configured with the Site field set to Shared to Client Sites.

Impact of Connection Site Configuration on Global List Site Mapping

The Setup Okta dialog, General Settings step, with Site set to Shared to Client Sites
Site Configuration: Shared to Client Sites

The New Schedule Data Source dialog, with the connection and the Global List for Site Mapping fields highlighted
Connection Site: Shared to Internal Sites | Global List for Site Mapping: absent

Before setting up global list site mapping, MSSPs must coordinate with their clients to identify the field in the incoming ingestion data that will provide the unique identifier for site mapping. Consider the following as the expected incoming ingestion data:

sample data

JSON
{
    "demoField1": "value1",
    "demoField2": "value2",
    "demoField3": {
        "demoField3A": "value3A",
        "demoField3B": {
            "keyToTheUniqueIdentifier": "uniqueIdentifier"
        }
    },
    "demoField4": [
        "value4A",
        "value4B",
        "value4C"
    ],
    "demoField5": "value5"
}


The D3 system will extract the (line 7) value of keyToTheUniqueIdentifier (uniqueIdentifier) and match it against a key in a selected global list to determine the correct client site for event creation.

The demo global list open on the Global List page, its JSON content showing a unique identifier mapped to a site name
  • If a match is found (i.e., uniqueIdentifier), the corresponding value (demo-site) will be used to determine the site where the event will be stored.

  • If no match is found, the event will be assigned to the Unknown Client Site.

Ensuring Correct Site Mapping in Global List

NOTICE

D3 currently does not support moving events between sites once they have been created. Users are advised to double-check that the unique identifier extracted from the incoming data has a corresponding key in the global list and that it maps to an existing client site.

Organization Management, Sites, with a client site's details open beside the site list
Verifying Global List Values Against Existing Sites

Once the unique identifier has been defined and communicated to clients, and a corresponding global list has been established, users can proceed with configuring data ingestion. Two pieces of information are needed before completing ingestion setup:

  • The JSON path to locate the unique identifier key ($.demoField3.demoField3B.keyToTheUniqueIdentifier for the sample data above )

  • The name of the global list storing the site mappings (Demo Global List)

Ingestions and Results

Webhook Push
  1. Select Configuration > Data Ingestion.

  2. Select New > Webhook.

    The Data Ingestion page on the Event Intake tab, with New and then Webhook highlighted
  3. In the New Webhook Data Source window, choose the Integration with the pre-configured Shared to Client Sites connection, then set up its API Keys for Shared to All Client Sites (API Key authentication for this demonstration), generating an API key if one does not already exist.

    The New Webhook Data Source panel with the connection set to Shared to All Client Sites, and the New API Key dialog beside it
  4. Select Shared to All Client Sites from the dropdown.

    The connection panel, with the site dropdown set to Shared to All Client Sites and the request URL above it
  5. Copy the Request URL (POST) from D3 and paste it into Postman.

    The connection panel's Request Header Key and Request Header Value fields

    The request URL pasted into the API client, with Send highlighted
  6. Copy the Request Header Key and Request Header Value from D3 and paste them into Postman.

    The API client's Headers tab, with the request header key added to the header list


  7. Under Additional Settings, enter the JSON Path for Site to locate the unique identifier key, then select the Global List for Site Mapping.

    The webhook's Additional Settings, showing JSON Path for Site and Global List for Site Mapping
    1. JSON path: $.demoField3.demoField3B.keyToTheUniqueIdentifier

    2. Global list: Demo Global List

  8. Copy and paste the following code into Postman, then click on the Send button.

    {
        "demoField1": "value1",
        "demoField2": "value2",
        "demoField3": {
            "demoField3A": "value3A",
            "demoField3B": {
                "keyToTheUniqueIdentifier": "uniqueIdentifier"
            }
        },
        "demoField4": [
            "value4A",
            "value4B",
            "value4C"
        ],
        "demoField5": "value5"
    }
    

    The API client's Body tab holding the sample JSON payload, with the 200 OK response below it
  9. Go back to the Data Ingestion page, verify event creation and note the eventId.

    The Data Ingestion page after the push, with the new event's id highlighted
    Event 4312516 Created
  10. In the sidebar, select Events to find the event.

    The Events list, with the newly created event highlighted
    Unmatching Sites from Demo Global List Will Not Have Access to Event 4312516

    The Events list seen from a site the global list does not map, where the event does not appear
    Only demo-site Will Contain Event 4312516
Scheduled Pull
  1. Copy and paste the following Python code into a custom Fetch Event command:

    Python
    def fetchEvent(startTime, endTime, TopN, SearchCon):
        
        eventData = {
            "id": str(uuid.uuid4()),  # Generate a unique ID for the event
            "demoField1": "value1",
            "demoField2": "value2",
            "demoField3": {
                "demoField3A": "value3A",
                "demoField3B": {
                    "keyToTheUniqueIdentifier": "uniqueIdentifier"
                }
            },
            "demoField4": [
                "value4A",
                "value4B",
                "value4C"
            ],
            "demoField5": "value5"
        }
    
        return pb.returnOutputModel(eventData, eventData, None, eventData, eventData, None)
    

    The custom integration command editor, showing the command's implementation
  2. Add a connection with the Site field set to Shared to Client Sites.

    A connection being added with the Site field set to Shared to Client Sites
  3. Test the command and verify that the output contains the intended structure.

    The Test Result dialog, with the command's Return Data output
  4. Submit the command.

    The command editor's footer, with Submit highlighted
  5. Set up a new schedule (see Data Ingestion).

    A new ingestion schedule, with the JSON Path for Site and Global List for Site Mapping fields set
    1. On the Data Ingestion page, select New > Schedule.

    2. In the Schedule Your Command window, choose the INTEGRATION and the Connection added above.

    3. Expand Additional Settings. The two site-mapping fields appear only when the connection is shared to client sites.

    4. Set the JSON Path for Site to $.demoField3.demoField3B.keyToTheUniqueIdentifier.

    5. Set the Global List for Site Mapping to Demo Global List.

  6. Go to the Data Ingestion page, verify event creation and note the eventId.

    The Data Ingestion page for the scheduled fetch, with the created event's id highlighted
    Event 4312749 Created
  7. In the sidebar, select Events to find the event.

    The Events list, with the event created by the scheduled fetch highlighted
    Unmatching Sites from Demo Global List Will Not Have Access to Event 4312749

    The Events list seen from a site the global list does not map, where the scheduled event does not appear
    Only demo-site Will Contain Event 4312749

READER NOTE

If the value of keyToTheUniqueIdentifier does not match any key in the selected global list (webhook push step 7b or scheduled pull step 5e), the system performs a case-insensitive name search across all sites of Client type. If a matching site is found, that site is used. Otherwise, the ingested event is routed to the (Unknown Client Site) site.