opens not getting uodated for a delivery | Community
Skip to main content
D
DishaSharma
Level 4
August 30, 2024
Solved

opens not getting uodated for a delivery

  • August 30, 2024
  • 1 reply
  • 833 views

Hi all

I am facing issue in  QA environment where

opens are not getting updated for a delivery 

while chekcing in Tracking tab of delivery

i have executed Technical workflowtracking wkf couple of times but opens are not getting updated at all

 

is there any workaround or manually or via wkf i can update tracking logs for that delivery

 

my delivery has only 3 recipeints--so I am looking fir a way to uodate opens fir those recipients fir tbose delivery

 

 

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by MeitMedia

Hi @dishasharma ,

 

It's important to note that instead of manually inserting or updating records in these tables, which could lead to more significant issues, it’s better to focus on resolving the root cause of why opens are not being tracked. Fixing the underlying issue ensures long-term stability and accuracy in your tracking data.

 

Though for your query on manual data insertion, you are right, the @type attribute you mentioned is not in the nms:trackingLogRcp schema but rather in the nms:trackingUrl schema. This attribute is an enumeration field, and its possible values are defined in the nms:trackingUrlInfo table. example: value "2" represents an open, "1" represents an email click. Also, to manually update open tracking logs with some sample data, it is crucial to ensure that the information in the nms:trackingLogRcp table is updated along with its linked tables, such as nms:trackingUrl, to maintain the integrity of your tracking data. Any inconsistency between these tables could lead to inaccurate reporting and other issues.

 

Best regards,

MEIT MEDIA (https://www.meitmedia.com)

Find us on LinkedIn

Contact Us: infomeitmedia@gmail.com

 

 

1 reply

MeitMedia
MeitMedia
Level 4
August 30, 2024

Hi @dishasharma ,

 

When facing an issue in Adobe Campaign Classic where opens are not being updated for a specific delivery, even after executing the technical workflow "tracking", here are the steps you can take to troubleshoot and resolve the problem:

1. Verify Tracking Configuration:

  • Always check the “Tracking and Images” section in the Delivery. Ensure that Activate Tracking & Opens Tracking options are ticked. Without these being activated, opens will not be tracked.
  • Review the Images tab within the “Tracking and Images” section of the delivery template. Ensure there are no errors related to image hosting. The open tracking pixel, embedded within the HTML, must be successfully downloaded for the opens to be recorded.

2. Understand the Tracking Mechanism:

  • The opens are recorded only when the open tracking pixel is downloaded by the recipient. If the recipient’s email client blocks images or does not download the tracking pixel, the opens will not be recorded. This is a standard functionality across all email marketing platforms, including Adobe Campaign, and there’s no automatic configuration to record opens without the pixel being downloaded.

3. Check Tracking Logs:

  • Review the tracking logs for any errors or warnings. These logs can provide insights into why the opens are not being recorded. Look for entries related to your specific delivery and recipients.

4. Manually Update Tracking Logs:

If necessary, you can manually create open records to simulate opens for the recipients. Here’s how:

  • Create an Excel Sheet: List the relevant data for your opens, including fields like logDate, recipientId, deliveryId, etc.
  • Data Loading Activity: Use the Data Loading (file) activity in your workflow to load the Excel sheet containing the open records.
  • Update Data Activity: Follow this with an Update Data activity to insert the loaded records into the nms:trackingLogRcp schema.
  • Recalculate Delivery Indicators: After inserting the records, recalculate the indicators for the delivery to reflect the updated data.

 

Best regards,

MEIT MEDIA (https://www.meitmedia.com)

Find us on LinkedIn

Contact Us: infomeitmedia@gmail.com

 

 

    D
    DishaSharmaAuthor
    Level 4
    September 1, 2024

    hello @meitmedia 

     

    I have tried the above 3points mentioned by you but no luck,

    however I also tried exploring the 4th point mentioned by you:

     

    • Update Data Activity: Follow this with an Update Data activity to insert the loaded records into the nms:trackingLogRcp schema.
    • Recalculate Delivery Indicators: After inserting the records, recalculate the indicators for the delivery to reflect the updated data.

    Queries: If I update the trackingLogRcp schema via UPDATE DATA ACTIVITY Then I think opens are being tracked under URL schema with attribute type

    I am not able to understand how should I update Type attribute to 'open'

    can u please help more how can i achieve this

    I am not able to understand how to flow this,

    can you please help me how exactly you are doing the same

     

      MeitMedia
      MeitMediaAccepted solution
      Level 4
      September 1, 2024

      Hi @dishasharma ,

       

      It's important to note that instead of manually inserting or updating records in these tables, which could lead to more significant issues, it’s better to focus on resolving the root cause of why opens are not being tracked. Fixing the underlying issue ensures long-term stability and accuracy in your tracking data.

       

      Though for your query on manual data insertion, you are right, the @type attribute you mentioned is not in the nms:trackingLogRcp schema but rather in the nms:trackingUrl schema. This attribute is an enumeration field, and its possible values are defined in the nms:trackingUrlInfo table. example: value "2" represents an open, "1" represents an email click. Also, to manually update open tracking logs with some sample data, it is crucial to ensure that the information in the nms:trackingLogRcp table is updated along with its linked tables, such as nms:trackingUrl, to maintain the integrity of your tracking data. Any inconsistency between these tables could lead to inaccurate reporting and other issues.

       

      Best regards,

      MEIT MEDIA (https://www.meitmedia.com)

      Find us on LinkedIn

      Contact Us: infomeitmedia@gmail.com

       

       

      Terms & ConditionsAccessibility statement

      Loading footer...