Configure reporting identifiers, webhooks, and outbound data settings

Tags: product:data-integrations intent:webhook intent:reporting-settings intent:external-id

Use Online Giving > Reporting > Settings to select optional report fields and product-specific identifiers, such as fields needed by the institution's CRM or GC Connect reporting. Use the campaign or Giving Form's own reporting settings when the field applies only to that object; use a custom report when a separate reusable layout is required.

To assign a campaign-specific reporting code, open Online Giving > Campaigns > [campaign] > Tracking & Analytics > Links & Appeal Codes > Internal Reporting and save the Unique Backend Identifier. Depending on the editor, the same field can appear under the campaign or Giving Form's Form Settings & Display > Internal Reporting. It is intended for values such as an appeal code, fund code, or campaign code and can be added to donation reports. When Blackbaud NXT gift export is enabled, select the Blackbaud appeal's Lookup ID, not its system ID, because this value is used as the exported Appeal ID.

Go to Online Giving > School-Level Settings > Webhooks to enable or disable webhooks, enter the institution's endpoint, and select Donations and/or Num Donors as the webhook type. Donation webhooks can be limited to selected donation states. All selected types are delivered to the same endpoint and are distinguished by the payload's type value.

The page shows an example payload for each enabled type and a delivery history with the event, sent time, delivered status, response, and data. Donation payload columns follow Online Giving > Reporting > Settings, including custom aliases. The receiving system must authenticate, deduplicate, and monitor events; a delivered status does not prove that the downstream system completed its own processing.

Keep external identifiers stable after data begins flowing. Changing an identifier or output column can break downstream reconciliation even when the GiveCampus screen saves successfully. Coordinate changes with the receiving system and test in a non-production workflow where possible.