Click tracking doesn't work anymore

Created on 10 June 2025, 2 days ago

Problem/Motivation

Unfortunately, with the current 11.x version, click tracking using the local event tracker does not seem to work anymore.

Steps to reproduce

  • Install the ad_track module
  • use the local event tracker
  • click on an advertisement
  • see in the admin ad view that the impression was tracked, but not the ad

Proposed resolution

Find out what changes are causing the problem and fix it.

Remaining tasks

User interface changes

API changes

Data model changes

🐛 Bug report
Status

Active

Version

11.0

Component

ad module

Created by

🇩🇪Germany lrwebks Porta Westfalica

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

  • Issue created by @lrwebks
  • Merge request !13Resolve #3529329 "Click tracking doesnt" → (Open) created by lrwebks
  • 🇩🇪Germany lrwebks Porta Westfalica
  • 🇩🇪Germany Anybody Porta Westfalica

    @lrwebks did it work in 4.x?

  • 🇩🇪Germany lrwebks Porta Westfalica

    @anybody: As far as I'm aware it did work in 4.x, yes.

    I have searched for a bit and can't seem to really grasp how the click track system is supposed to work. It uses a route and controller, which then passes the track event on to the tracker via trackClick(). So far, so good. But, the route that is used for that doesn't seem to appear anywhere or be requested/called/opened anywhere. Does 11.x require a rewrite of that system, possibly?

    @grevil: Perhaps you could take a look at what is the problem here?

  • 🇩🇪Germany Anybody Porta Westfalica

    @lr:

    @anybody: As far as I'm aware it did work in 4.x, yes.

    Then it shouldn't be hard to find for you? Just look up how it worked and what broke it?

  • 🇩🇪Germany lrwebks Porta Westfalica

    Well, I was so focused on my research within the ad_track module, that I somehow missed changing the ad content formatter from “Ad content” to “Ad content with click tracking”… So it still works. Another mystery solved.

    There is one thing bugging me, though: This formatter lies within the ad_content module, but is specifically designed for the ad_track module. I think that is bad, because they are supposed to be independent and exchangeable pieces of the ad puzzle. But I also don't know if putting the formatter into the ad_track module would help any better than the current approach. @anybody, do you think this needs a change?

Production build 0.71.5 2024