Clicks are not reporting correctly

[ArslanNa]

Hi, 

I'm running an AB test via Target, and changes are to swap the hero banner with another banner which is below the fold and track clicks on each banner. I've setup click tracking in Adobe Target as the reporting source, but clicks are not looking being reported correctly at all. Not sure what is the cause of this issue. Please see the screenshot.
You should see the DOPE banner as hero banner in variation: http://bulk.com/nl/

Thanks,

Arslan

[bjoern__koth]

Hi Arslan,

is it just the high numbers that look off? How have you set in up in the Web SDK? Are you using the automatic click collection?

One important side note: since you're EU and GDPR applies, I would strongly urge you to check your cookie consent setup.
It is setting quite some cookies (among them the Experience Platform cookies) which I don't think is legally compliant.

The initial Web SDK "set-consent" should not trigger until the OneTrust banner has been interacted with, even if the default consent is "n".

[pradnya_balvir]

Hi @ArslanNa ,

Common Causes to Check

1. Click Tracking Setup in Adobe Target

• Ensure you're using trackEvent() properly in your experience code or using the Visual Experience Composer (VEC) click tracking.

• If you're using VEC:

  • Make sure the element selector (like a button, img, or a tag) is correctly targeted.

  • Check that the element exists on page load (especially if content is loaded dynamically).

2. Element Visibility & Lazy Load

• Since the DOPE banner was moved from below the fold to the hero, make sure:

  • The element is present and visible in the DOM at the time of click tracking.

  • Lazy-loading or JavaScript rendering isn't delaying the banner load beyond Target's script initialization.

3. Click Happens Before Target Is Ready

• Add a console log or break to check if the adobe.target.trackEvent() fires on click.

• If not, the click might be happening before Target finishes loading, especially on fast connections or lightweight pages.

4. Single Page App (SPA) or Client-side Rendering

• If the site is a SPA or has AJAX content swaps, ensure you:

  • Re-trigger trackEvent() after DOM updates.

  • Use Adobe Target's SPA support or triggerView() properly.

5. No Success Metric Configured

• In Adobe Target’s reporting setup, did you define the click goal as a success metric for your activity?

  • If not, Target won’t attribute click events to your experience.