Reporting issue with top-campaign-content
Hi, We are requesting for this report(/reports/top-campaign-content/dimensions/item_breakdown) several times a day. But , server returned 503 status code in a few accounts. This problem starts since September 21st and it is remaining. I tried it for a several time , but the result doesn't change. Please tell me why it's happening and what we can do to solve this. response headers: <?xml version="1.0" encoding="utf-8"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html> <head> <title>503 backend read error</title> </head> <body> <h1>Error 503 backend read error</h1> <p>backend read error</p> <h3>Guru Mediation:</h3> <p>Details: cache-tyo11974-TYO 1632721947 3457093885</p> <hr> <p>Varnish cache server</p> </body> </html>
Posted by Shohei Takahashi about 1 year ago
Revenue day_site_placement_country_platform_breakdown report returns double reveue
Hello, The report /api/1.0/_networkId_/reports/revenue-summary/dimensions/day_site_placement_country_platform_breakdown returns 'subtotal' row site country platform with empty placement Basicly if we have two rows US DESKTOP placement1 X US DESKTOP placement2 Y the report will include 3rd row US DESKTOP X+Y Can't find anything in docs/a way to switch this off. We can just ignore rows with empty placements but the concern is the report can change one day and empty placements will have a different meaning (like missing placement info) Please advice Thanks Misha
Posted by Misha Makarevsky about 1 year ago
Api Authorization Problem
Hi! Yesterday starting from 7PM GMT+1 we faced API authorization problems. We work with Ubuntu 16.04, which is located on Amazon. The problem is when we try to get the token we get the "401" response. Sreenshot: https://prnt.sc/snzqlc The authorization code is absolutely the same on the working PC, and everything works correctly. Screenshot: https://prnt.sc/snzskf Also, everything works correctly via Postman. Screenshot: https://prnt.sc/snztko Please help us find and solve the problem.
Posted by Ivan Borokh over 2 years ago
Custom audience ids change?
Hello, We are not able to set custom audiences using API Everything was working fine ~14 hours ago but on some point custom audience ids changed and updating custom audience fails. After checking the current values I noticed (for example) https://backstage.taboola.com/backstage/api/1.0/giveitlove-sc/campaigns/4594930/targeting/my_audiences The value in "collection" array used to appear as string "226875" and now its a number 1642268. The new id is not in a dictionary we are getting from /universal_pixel/custom_audience_rule This change is permanent and if so where we can get new ids? Thanks Michael
Posted by Misha Makarevsky over 2 years ago