Adobe Target at.js 2.11.7 trackEvent() does not send delivery request for custom mbox conversion (VEC Activity)) | Community
Skip to main content
Level 1
July 28, 2026
Question

Adobe Target at.js 2.11.7 trackEvent() does not send delivery request for custom mbox conversion (VEC Activity))

  • July 28, 2026
  • 2 replies
  • 31 views

Hi Everyone,

I’m facing an issue with Adobe Target (at.js 2.11.7) where adobe.target.trackEvent() does not send any Target request.

Environment

  • Adobe Target Launch Extension: v2.11.7
  • at.js implementation
  • VEC Activity
  • Initial page load request:/rest/v1/delivery
  • Decision Method: Server-side only
  • Reporting tested with:
    • Adobe Target
    • A4T
  • Same behavior in both cases

Activity Configuration

  • Activity Type: A/B Test(VEC)
  • Goal Metric:
    • Conversion
    • Viewed an Mbox
    • Mbox Name: ClickTracking

Code

document.addEventListener('click', function(e){
const btn = e.target.closest("a.secondary.iconPresent");
if(!btn) return;
adobe.target.trackEvent({
mbox: "ClickTracking",
params:{
clicked: "ElementClicked"
},
success: function () {
console.log("SUCCESS");
},
error: function (err) {
console.log("ERROR", err);
}
})
})

What works

  • Activity renders correctly
  • Initial /rest/v1/delivery request is sent.
  • Experience loads successfully.
  • Click handler executes.
  • Adobe Client Data Layer push executes.

Problem

​​​​​​​​​​​​​​When trackEvent() is called:

  • No /rest/v1.delivery request is sent.
  • No /notifications request is sent.
  • Success callback in never called.
  • Error callback is never called.
  • No Javascript errors.

Troubleshooting already performed

  • Verified trackEvent() is invoked using a wrapper.
  • Verified adobe.target.trackEvent exists.
  • Verified sendNotifications() exists.
  • Tested from browser console.
  • Tested inside VEC custom code.
  • Tested with Adobe Target reporting & A4T.
  • Added the same at_property used by the page load request.
  • Same issue occurs in existing activities and newly created activities.

Question

Has anyone seen trackEvent() silently do nothing (no network request, no callbacks) while page-load delivery works correctly?

 

Could this be related to:

  • Launch Extension v2.11.7?
  • Decision Method = Serve-side only?
  • Workspace/Property configuration?
  • Any known limitation with custom mbox conversions in at.js 2.11.7?

Any suggestions or similar experiences would be appreciated.

Thanks!

 

2 replies

Level 3
July 29, 2026

Hi ​@DevakrishnaRa3 ,

 

The code looks correct and it should trigger a call. Can you check if the code is actually getting executed or if the btn is not present and function returns before trackEvent gets triggered. Also can you check if you are getting a response just by calling trackEvent in console.

 

Seems like it could be selector issue. Try this and let me know.

 

Hope this helps!

Level 1
July 29, 2026

Update:

I did some additional debugging based on the suggestion.

Code:

document.addEventListener('click', function(e){
const btn = e.target.closest("a.secondary.iconPresent");
if(!btn) return;
console.log("Button Clicked", btn);
adobe.target.trackEvent({
mbox: "ClickTracking",
params:{
clicked: "ElementClicked"
},
success: function () {
console.log("SUCCESS");
},
error: function (err) {
console.log("ERROR", err);
}
});
console.log("trackEvent invoked");
})

Results:

  • “Button clicked” is looged.
  • “trackEvent invoked” is logged.
  • No additional /rest/v1/delivery (or notification) request is sent.
  • Neither the success nor error callback is executed.
  • The same behavior occurs even when calling adobe.target.trackEvent() directly from the browser console.