How logs are getting updated in backend in ACC | Community
Skip to main content
S
Sujith_02kumar
Level 4
April 24, 2025
Solved

How logs are getting updated in backend in ACC

  • April 24, 2025
  • 2 replies
  • 661 views

Hi Everyone,

 

Can someone help me understand how logs are updated on the backend in Adobe Campaign? Specifically, I'd like to know whether its based on delivery ID, broadLog ID, message ID, recipient ID or delivery counter.

I'm trying to update my delivery logs and tracking for custom channels like WhatsApp, RCS and would like to understand exactly how the process works behind the scenes. I've gone through the documentation but couldn't find a clear explanation of what's happening in the backend.

 

Regards,

Sujith kumar

Best answer by Vishwadeep1

Hi @sujith_02kumar ,

 

Whenever a communication is triggered, a unique message ID (@broadLog-id) is generated and stored in the "nms:providerMsgId" field.You can extend this schema to include an additional field for an external message identifier, where you can store the response message ID received from WhatsApp, RCS or other custom channels.

When using custom connectors to send messages via channels like WhatsApp or RCS, you can store the message ID in the relevant schema. Later, you can use it to map logs received through reverse feeds from those platforms and using a custom workflow, insert/update the broadlog and trackinglog schemas accordingly by referencing the @broadLog-id.

This is a high-level overview—I hope it helps to a certain extent in updating your delivery and tracking logs for custom channels.

 

Regards,

Vishwadeep

 

2 replies

S
Sujith_02kumarAuthor
Level 4
April 26, 2025

Does anyone have an idea here? Any input would be appreciated

 

@parthasarathy , @campaignerforlife 

 

Regards,

Sujith kumar 

V
Vishwadeep1Accepted solution
Level 2
May 20, 2025

Hi @sujith_02kumar ,

 

Whenever a communication is triggered, a unique message ID (@broadLog-id) is generated and stored in the "nms:providerMsgId" field.You can extend this schema to include an additional field for an external message identifier, where you can store the response message ID received from WhatsApp, RCS or other custom channels.

When using custom connectors to send messages via channels like WhatsApp or RCS, you can store the message ID in the relevant schema. Later, you can use it to map logs received through reverse feeds from those platforms and using a custom workflow, insert/update the broadlog and trackinglog schemas accordingly by referencing the @broadLog-id.

This is a high-level overview—I hope it helps to a certain extent in updating your delivery and tracking logs for custom channels.

 

Regards,

Vishwadeep

 

    Terms & ConditionsAccessibility statement

    Loading footer...