Community Discussion
Blocking is not reflecting on backstage
When blocking a publisher from the Backstage platform, the change is immediately reflected in the campaign publisher_targeting object via the API.
But when updating this object (publisher_targeting) via the API, the change is not reflected in the Backstage platform - even after a page refresh.
This is the call we make to block publishers:
patch: https://backstage.taboola.com/backstage/api/1.0/[redacted]/campaigns/5602922
Payload: {"patch_operation": "ADD", "publisher_targeting": {"publishers": ["lemaleadmachine-tipsandtricks"]}}
Could that be a UI cache on the Backstage platform? Or are we missing something?
Posted by Igor about 3 years ago
Reporting delay through API
Hi, is there any delay in reporting through API for clicks / spend that took place ?
For example, if there's click / spend event that takes place now, how soon is this information available for the reporting API ?
Thanks
Posted by Jack Qian over 3 years ago
Questions on Spend data
Hi there, are the Spend numbers coming from Taboola’s API ever inaccurate, in terms of costs related to real-time clicks? Are they ever ahead or behind, or inflated to predict Spend associated with future clicks? We’re seeing hourly data that reflects the possibility of Spend increasing before the clicks associated with it come through.
Also, what time zone Taboola’s API is using?
Thanks!
Posted by Justin Farber over 3 years ago
Retroactively changing data
Hi everyone!
There’s the following note in API guide:
“It’s important to note that data in Taboola reports can (and will) change retroactively during the Taboola billing cycle.
This means that when fetching report data from Taboola for a data warehouse or BI solution, the data for the entire billing cycle (current calendar month + previous calendar month up to the 5th in any given month) should be periodically refreshed.”
Does it mean that if we update report data daily, then today (for example) we need to request data for the period 5th of Jan - today?
2. There is a field “last_used_rawdata_update_time” in response. What does this value stand for? Does it indicate the date when the report was lastly updated? So if today we get a report with last_used_rawdata_update_time = 6th of Feb then we don’t need to update our DWH as nothing changed since this date?
Posted by Ivan Korsakov over 3 years ago