Community Discussion
Blocking publishers via API
I am trying to block a publisher within a single company via a POST request to a URL:
https://backstage.taboola.com/backstage/api/1.0/account-id/campaigns/campaign-id
Request body:
{
"publisher_targeting": {
"type": "EXCLUDE",
"value": [
"my-publisher"
],
"href": null
}
}
Next, I go to the control panel, where all the publishers of the campaign are located. Here I can see that the publishers I specified in the request body specified above are not blocked after the POST request is executed. What could be the problem? Perhaps there is a delay in the web interface until the actual data appears?
Posted by Danil Makogon over 3 years ago
API report delay. API numbers are not the same as the UI numbers
Hello there!
We use /api/1.0/{account}/reports/top-campaign-content/dimensions/item_breakdown API URI to request report for current date. However, the API response metric numbers is not the same as the number in UI.
Posted by Mark Wise about 4 years ago
Data Mismatch in conversions.
There is a huge diff in conversions in the API and the UI.
Posted by Dileep about 4 years ago
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 4 years ago