Documentation

Tracking workflow performance issue in Adobe Campaign Classic

Last update: Sat Dec 20 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

This article explains how to improve processing times for your Strategic instance’s tracking workflow in Adobe Campaign Classic, aligning them closer to those observed in your Tactical instance.

Description description

Environment

Product: Adobe Campaign Classic Hosted
Version: Classic v7

Issue/Symptoms

In an on-premise instance of Adobe Campaign Classic, there is a noticeable discrepancy in the performance of the tracking workflow between two production instances. The Tactical instance completes its tracking workflow within 30 to 45 minutes, while the Strategic instance takes over 1.5 to 2 hours despite handling fewer email campaigns.

This delay impacts A/B subject line tests as delivery log statistics are not updated promptly, hindering timely decision-making for determining test winners.

Resolution resolution

Follow these steps to resolve the issue:

  1. Optimize log retrieval settings: Adjust the logCountPerRequest parameter in the serverConf.xml file from its default value (1000) to a higher value, such as 8000. This change can improve performance by allowing more logs to be retrieved per request.

  2. Index fragmentation management: Regularly monitor index fragmentation rates on key tables:

    • NmsBroadLogRcp
    • NmsTrackingLogRcp
    • NmsRecipient
    • NmsDelivery
    • NmsTrackingStats
    • NmsDeliveryLogStats

    If any table’s index fragmentation exceeds 30-35%, rebuild those indexes to maintain optimal performance.

  3. Workflow optimization strategy: Consider splitting the existing tracking workflow into two separate workflows:

    • Create duplicates of your current tracking workflow.
    • Name one trackingDownload and configure it only with the -download option.
    • Name the other trackingUpdate and configure it only with the -update option.

    Schedule these workflows strategically; run trackingDownload every few hours and trackingUpdate once daily during low server traffic periods.

  4. Implement a new configuration setting:

    code language-none 
    Option Name: NmsRecompute_Delivery_BatchSize
Data Type: Integer
Value: 600
recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f