[Also applies to v8]{class="badge positive" title="Also applies to Campaign v8"}
Delivery dashboard delivery-dashboard
The delivery dashboard is key to monitor your deliveries and eventual issues encountered during the sending of messages.
It allows you to retrieve information on a delivery and edit it if necessary. Note that tab contents may no longer be changed once the delivery has been sent.
Here are the information you can monitor using the several tabs that are available in the dashboard:
Related topics:
Delivery summary delivery-summary
The Summary tab contains the characteristics of the delivery: delivery status, channel used, information about the sender, subject, information concerning execution.
Delivery reports delivery-reports
The Reports link, which is accessible from the Summary tab, lets you look at a set of reports related to the delivery action: general delivery report, detailed report, delivery report, distribution of failed messages, opening rate, clicks and transactions, etc.
The contents of this tab can be configured according to your requirements. For more on delivery reports, refer to this section.
Delivery logs, history and exclusions delivery-logs-and-history
The Delivery tab gives a history of the occurrences in this delivery. It contains the delivery logs, i.e. the list of messages sent and their status and the associated messages.
For a delivery, you can display (for example) only recipients with a failed delivery or an address in quarantine. To do this, click the Filters button and select By state. Then select the state in the drop-down list. Various statuses are listed in this page.
The Display the mirror page for this message… link lets you view the mirror page for the contents of the delivery selected from the list in a new window.
The mirror page is available only for deliveries for which HTML content has been defined. For more on this, refer to Generating the mirror page.
Delivery tracking logs and history tracking-logs
The Tracking tab lists the tracking history for this delivery. This tab displays tracking data for the messages sent, i.e. all URLs subject to tracking by ۶Ƶ Campaign. The tracking data is updated hourly.
Tracking configuration is performed at the appropriate stage in the delivery assistant. See How to configure tracked links.
Tracking data is interpreted in the delivery reports. See this section.
Inbox rendering delivery-rendering
The Inbox rendering tab allows you to preview the message in the different contexts in which it may be received and check the compatibility in major desktops and applications.
This way, you can make sure that your message will be displayed to the recipients in an optimal way on a variety of web clients, web mails and devices.
For more on inbox rendering, refer to this page
Delivery audit delivery-audit-
The Audit tab contains the delivery log and all the messages concerning the proofs.
The Refresh button lets you update the data. Use the Filters button to define a filter on the data.
Special icons enable you to identify errors or warnings. See Analyzing the delivery.
The Proofs sub-tab lets you view the list of proofs that have been sent.
You can modify the information displayed in this window (and that of the Delivery and Tracking tabs) by selecting the columns to be displayed. To do this, click the Configure list icon located in the lower right-hand corner. For more on configuring list display, refer to this section.
Delivery dashboard synchronization delivery-dashboard-synchronization
From your delivery dashboard, you want to check the processed messages and delivery logs to be sure that your delivery was successfully sent.
Some indicators or status can be incorrect or not up-to-date, this may be resolved with the following solutions:
-
If your delivery status is incorrect, check that all necessary approvals have been done for this delivery or that the operationMgt and deliveryMgt workflows are running without errors. This can also be due to the delivery using an affinity not configured on the sending instance.
-
If your delivery indicators are still at zero and if you are on a mid-sourcing configuration, check the Mid-sourcing (delivery counters) technical workflow. Start it if its status is not Started. You can then try to recompute the indicators by right-clicking the relevant delivery in the ۶Ƶ Campaign explorer and selecting Actions > Recompute delivery and tracking indicators. For more information on tracking indicators, refer to this section.
-
If your delivery counter does not match your delivery, try to recompute the indicators by right-clicking the relevant delivery in the ۶Ƶ Campaign explorer and selecting Actions > Recompute delivery and tracking indicators to resynchronize. For more information on tracking indicators, refer to this section.
-
If your delivery counter is not up-to-date for mid-sourcing deployments, check that the Mid-Sourcing (Delivery counters) technical workflow is running. For more on this, refer to this page.
You can also track your deliveries with different reports via the delivery dashboard. For more on this, refer to this section.
Use case: Adding senders’ IP addresses to the logs use-case
In this section, you will learn how add to the delivery logs information regarding the IP address that sent each email in a delivery.
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 <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.
Step 3: Validate the modification
To confirm everything worked correctly, you need to update delivery logs screen.
To do this, access the delivery logs and add the “IP identifier” column.
Below is what you should see in the Delivery tab after modifications:
