-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
New-tab page: failed to get and fire creative NTP ad and promoted content ad event #14194
Labels
Comments
Closing this out; thx to a bunch of folks, we're now able to get matched ads to catalog, which was the problem, on dev/staging. Working now:
|
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Description
In trying to test and verify #13695, I'm encountering
Failed to get creative new tab page ad
andFailed to fire promoted content ad event for uuid
, when clicking on the promoted-content item on the new-tab page.@tmancey can you confirm the optimal combination of command-line arguments for testing, if not as below? Thanks in advance!
In particular, in
Failed to fire promoted content ad event for uuid
, theuuid
is missing a value.Steps to Reproduce
--args --enable-logging=stderr --vmodule="*/bat-native-ledger/*"=6,"*/brave_rewards/*"=6,"*/bat-native-ads/*"=6,"*/bat-native-confirmations/*"=6,"*/brave_ads/*"=6,"*/brave_user_model/*"=6 --brave-ads-development --brave-ads-debug --rewards=development=true,reconcile-interval=5 --brave-today-host=brave-today-cdn.brave.software
.I've also tried using:
--args --enable-logging=stderr --vmodule="*/bat-native-ledger/*"=6,"*/brave_rewards/*"=6,"*/bat-native-ads/*"=6,"*/bat-native-confirmations/*"=6,"*/brave_ads/*"=6,"*/brave_user_model/*"=6 --brave-ads-debug --brave-today-host=brave-today-cdn.brave.software
but get the same errors.
Start using Brave Rewards
Actual result:
Expected result:
I'd think I should see
view
andclick
events for the promoted-content item?Reproduces how often:
100%
Brave version (brave://version info)
Version/Channel Information:
The text was updated successfully, but these errors were encountered: