Skip to content

Unable to see impression or click event #137

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
guybashan opened this issue Dec 22, 2024 · 1 comment
Open

Unable to see impression or click event #137

guybashan opened this issue Dec 22, 2024 · 1 comment

Comments

@guybashan
Copy link

guybashan commented Dec 22, 2024

  • I am simulating both sides: MMP and SSP
  • I am properly getting a call to my endpoint for: "win" and "result".
  • I do not get any class to "imp" and "click" endpoints.
  • I do register these events on both: "generateBid" and "generateScore":
    let clickUri = reporting_address + '/report/click';
    let viewUri = reporting_address + '/report/view';
    const beacons = {'click': clickUri, 'view': viewUri};
    registerAdBeacon(beacons);
  • I also run on the Android device the following code after I get adSelectionId:
mAdClient.reportImpression(request)
mAdSelectionManager.reportEvent(request)
  • I run the "reportEvent" twice. One with "click" and second with "view" as the "eventKey".
  • I force the following services:
db shell cmd jobscheduler run -f com.google.android.adservices.api 5
adb shell cmd jobscheduler run -f com.google.android.adservices.api 3
adb shell cmd jobscheduler run -f com.google.android.adservices.api 7
adb shell cmd jobscheduler run -f com.google.android.adservices.api 14
adb shell cmd jobscheduler run -f com.google.android.adservices.api 20

Any reason why impression and click events are not reported?

Thanks

@erintwalsh
Copy link
Contributor

Hi, thanks for reaching out! Just to clarify, are you not seeing event-level reports delivered? Have you set up debug reports? The first step I'd recommend is enabling verbose debug reports, which will provide more insight into if registrations are failing or not being matched to conversions. You can also enable verbose logging in Logcat with this command adb shell setprop log.tag.adservices VERBOSE. Are you seeing any errors? It would help if you could share any error messages you're seeing, or a full bug report by running adb bugreport.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants