Documentation Campaign Campaign Classic v7 Documentation

Advanced: Customize delivery logs customize-delivery-logs

Last update: Thu Dec 04 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

Applies to:
Campaign Classic v7

Topics:
Monitoring

CREATED FOR:

User
Developer

NOTE

Comprehensive guidance on accessing the delivery list and using the delivery dashboard is documented in the Campaign v8 documentation. This content applies to both Campaign Classic v7 and Campaign v8 users.

This page documents Campaign Classic v7-specific advanced customizations for hybrid and on-premise deployments.

For monitoring deliveries in the Campaign UI, refer to the Campaign v8 Monitor deliveries in Campaign UI documentation.

Customize delivery logs use-case

For Campaign Classic v7 hybrid/on-premise deployments, you can customize delivery logs by extending schemas. This section shows how to add senders’ IP addresses to the delivery logs.

NOTE

This customization requires schema extension capabilities available in on-premise deployments. Campaign v8 Managed Cloud Services users should contact Adobe Customer Care for custom delivery log fields.

This modification is different if you are using a single instance or mid-sourcing instance. Before doing the modification, ensure you’re connected to email sending instance.

Step 1: Extend the schema

To add publicID in your delivery logs you need to extend the schema first. You can proceed as follow.

Create a schema extension, under Administration > Configuration > Data Schemas > New.

For more information about schema extensions, refer to this page.

Select broadLogRcp to extend the Recipient delivery logs (nms) and define a custom Namespace. In this case it will be “cus”:

note note
NOTE
If your instance is in Mid-sourcing, you need to work with broadLogMid schema.

Add the new field in your extension. In this sample, you need to replace:

code language-none
`<element img="nms:broadLog.png" label="Recipient delivery logs" labelSingular="Recipient delivery log" name="broadLogRcp"/>`

by:

code language-none

code language-none
`<element img="nms:broadLog.png" label="Recipient delivery logs" labelSingular="Recipient delivery log" name="broadLogRcp"> <attribute desc="Outbound IP identifier" label="IP identifier" name="publicId" type="long"/> </element>`

<element img="nms:broadLog.png" label="Recipient delivery logs" labelSingular="Recipient delivery log" name="broadLogRcp">
<attribute desc="Outbound IP identifier" label="IP identifier"
name="publicId" type="long"/>
</element>

Step 2: Update database structure

Once modifications are done, you need to update database structure so that it is aligned with its logical description.

To do this, follow the steps below:

Click the Tools > Advanced > Update database structure… menu.

In the Edit tables window, the NmsBroadLogRcp table is checked (or the broadLogMid table if your are in a Mid-sourcing environment), as below:

note important
IMPORTANT
Always ensure there is no other modification, except the NmsBroadLoGRcp table (or the broadLogMid table if your are in a Mid-sourcing environment). If so, uncheck other tables.

Click Next to validate. The following screen displays:
Click Next, then Start to start updating database structure. Index building is starting. This step can be long, depending on the number of rows in the NmsBroadLogRcp table.

NOTE

Once the update of the physical structure of the database is successfully completed, you need to disconnect and reconnect so that your modifications are taken into account.