AT.JS 2.0.1 Not Reporting Clicked an Element Conversion

[#1]

We upgraded to at.js 2.0.1 on May 15th. Since then, Adobe Target has stopped reporting "clicked an element" conversion events. I've reached out to Adobe Target support and have been told that this is a known issue and is scheduled to be fixed the week of June 3rd.

My question is, are others experiencing the same issue with at.js 2.0.1? If you are, are you just waiting for the fix or have you found a way to capture and report clicks using A4T?

Thanks,

Keith

[#2]

@keithf73253183

Thanks for reaching out. Do you mind getting the internal engineering ticket# and sharing it with us in here so that it can be documented? Thank you!

Mihnea Docea | Technical Support Consultant | Customer Experience | Adobe | (:: 1 (800) 497-0335

[#3]

I'll ask for the ticket.

I was told to watch https://docs.adobe.com/content/help/en/target/using/release-notes/target-release-notes.html ​

Is this the first time that this issue has been reported on the forum?

Thanks,

Keith

[#4]

@keithf73253183

Nice to see ya out here in the forums.

I believe the issue that you are facing is similar to: Chrome CORB Blocking Response?

"This issue affects both at.js 1.x click-tracking requests, as well as at.js 2.x display and click-tracking notifications."

Hope that helps!

[#5]

@keithf73253183,

That is a good place to watch those are the release notes. I'm personally curious if an official ticket Jira# has been opened with Engineering in regards to this or not so that I can look over it as well. Thank you!

Mihnea Docea | Technical Support Consultant | Customer Experience | Adobe | (:: 1 (800) 497-0335

[#6]

The internal JIRA ticket number is : TNT-32290 .

[#7]

@keithf73253183,

Internal ticket#: TNT-32290 is scheduled to be fixed in Target version: 19.5.0 Release date tentative for: Early June. Aaccording to that ticket: Engineering confirmed that all the tracking calls pass through fine and are properly logged on Target side, the only minor problem is that a warning gets logged to the console which should not be there.

Mihnea Docea | Technical Support Consultant | Customer Experience | Adobe | (:: 1 (800) 497-0335

[#8]

So, does that point to another issue? Should our banner clicks be reporting?

Thanks,

Keith

[#9]

@keithf73253183,

It could be the same issue or related please confirm via the support ticket thread. Thanks for all the information you have shared with us on the forum here.

Mihnea Docea | Technical Support Consultant | Customer Experience | Adobe | (:: 1 (800) 497-0335

[#10]

Hey Keith

Sent over another email regarding the selector modifications for the banner, as well as a follow up question

Hope it helps