Setting up an additional event subscriber

An additional subscriber lets one organization (the direct subscriber) share event data with another organization (the additional subscriber). Both organizations must be tenants of the same Pismo client.

Use an additional subscriber when multiple organizations need access to the same event stream for reporting, analytics, integrations, or operational workflows. Events can be delivered through real-time streaming, batch file delivery, or both.

The following event delivery architecture image shows how a direct subscriber shares events with an additional subscriber through real-time streams and batch files.

How it works

• The direct subscriber forwards events to the additional subscriber.

• Delivery can be via real-time streaming, batch file, or both.

• The additional subscriber can receive events from multiple organizations and distinguish them by using org_id.

• Event delivery supports AWS, GCP, and Azure environments.

• You can use event filtering to control which events are shared.

📘

Organizations can use different cloud providers as long as both organizations are tenants of the same Pismo client.

Prerequisites

Before you submit a request, confirm the following:

• The direct subscriber (source org) is configured on the Pismo data platform
• The additional subscriber (destination org) is a tenant of the same client
• The additional subscriber has data integration configured (can receive events)

Open a service desk ticket

1. Go to: https://pismolabs.atlassian.net/servicedesk/customer/portal/10
2. Select Settings.
3. Enter a short description of the request in the Summary field.
4. For Category, select Data.
5. For Sub-Category, select Additional Subscriber.
6. Copy the request template into the Description field and enter your values:

CONFIGURATION REQUEST — Additional Event Subscriber
====================================================

Requester Name:        Your Name
Contact Email:         [email protected]
Environment:           Production / Sandbox

Source Org ID:         TN-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
  (the organization that generates the events)

Destination Org ID:    TN-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
  (the organization that will receive the shared events)

Delivery Type:         Real-Time Streaming / Batch File Delivery / Both
Cloud Provider (Dest): AWS / GCP / Azure

Event Filtering:       Yes / No
  (If Yes, please also open an Event Filtering request
   or list the filtering patterns below)
Filtering Patterns:    domain.* / *.event_type / domain.event_type

7. When a Control Center request fails, the application automatically displays a popup message. You can add this message in the Report Log field.
8. Select a value for Priority.
9. Select the appropriate Environment.
10. Select Send to submit the request.

📘

Use lowercase values for all Org IDs.

⏱️

Important: After Pismo completes the initial configuration, you have 24 hours to adjust permissions/access on your side. If Pismo cannot deliver events within this window, the integration is paused and you will need to open a new ticket to resume.

📘

Need Pismo-specific details? Information such as Pismo's AWS Account ID, single-tenant SFTP endpoints, consumer role ARNs, or external IDs can be obtained from your Technical Account Manager (TAM) or the implementation engineer assigned to your project.

Review example event data

Events from a direct subscriber include the org_id field, allowing the additional subscriber to identify the source:

{
    "event_id": "252212bf-cde2-43f9-b28f-33ea2b452b32",
    "domain": "onboarding",
    "event_type": "succeeded",
    "schema_version": 1,
    "org_id": "TN-a1db4e4e-315f-4a67-9036-ecacd370b561",
    "cid": "8a3f650b-c80c-451f-993d-7368dba4c715",
    "timestamp": "2019-07-20T19:03:00.000Z",
    "data": {}
}

If the additional subscriber receives events from multiple organizations, use org_id to identify and filter the source organization.

Validate the configuration

After Pismo confirms the configuration, use the Prerequisites checklist and the troubleshooting table to verify that event delivery works as expected.

Troubleshooting table