Community Discussion
Publisher Reporting API Limitations
Hi there,
we would like to integrate the Publisher Revenue Reporting API and have a few questions around limitations.
Currently, the endpoint only supports a daily breakout.
1. Is there any non-documented feature that would allow hourly?
The docs only show the option of UTM CAMPAIGN and UTM SOURCE + MEDIUM.
2. Is there any other option to get more granular data e.g. UTM CAMPAIGN + SOURCE + MEDIUM (ideally also TERM and CONTENT)?
There is a Custom Key/Value report. With the account in use, these are always undefined. We couldn't find any documentation on how to set them and what the limits are.
3. Can you point us in the right direction?
Posted by Nils about 3 years ago
how can I get 'site' breackdown
Hey
I'm using the premade report (campaign summary report) and I don't get the site dimension. how can I retrieve it?
Thx
Posted by [email protected] over 1 year ago
Reporting: site breakdown - no `site_url` is provided
Hello! I getting `campaign-summary` report using `campaign_site_day_breakdown`:
https://backstage.taboola.com/backstage/api/1.0/<account_id>/reports/campaign-summary/dimensions/campaign_site_day_breakdown?start_date=2021-02-24&end_date=2021-02-24
API response is:
{
// omitted...
"results": [
{
"date": "2021-02-24 00:00:00.0",
"site": "site-string-id",
"site_name": "Site pretty name",
"site_id": 1053067
// omitted... "site_url" field is not provided
}
}
but there is no property containing `site_url`. How can I get it?
Posted by Skorokhodov Egor about 3 years ago
Uploading Customer List?
Does anyone know where the Customer List upload button is? I don't see it populated in the Audience section.
Posted by Angelo Lozano over 1 year ago
Client ID and Client Secret from your Taboola contac
I try to connect my account to power my analytics, i need Client ID and Client Secret. Where can I find it?
Posted by Igor Fostenko almost 2 years ago
All exelate marketplace audiences were removed?
Hello,
We getting lot of errors when coping marketplace audiences from one campaign to another (the same country and account): "Targeting: [111983] is not available in the targeted countries due to limited scale.
In Taboola UI exelate audiences does not have size and when we trying to remove them getting a popup telling that the audience is no longer available.
We will check market place audiences dictionary to filter out non available audiences or parse returned error and retry unless there are other reconditions
1. exelate audiences are gone and they not coming back?
2. lot of our campaigns lost audiences targeting (some even lost all targeting) - any recommendations what to do with them?
Thanks
Michael
Posted by Michael Makarevsky almost 4 years ago
Resource Not Found when requesting a campaignItem
When we try to pull a campaignItem we get a βResource not foundβ error, although the item is actually existing and visible through the Taboola UI. This is preventing us to update the campaignItem with imageUrl and headline.
As an example:
https://backstage.taboola.com/backstage/api/1.0/inpowered-sc/campaigns/4636610/items/2900178486
Can you please help to understand why this is happening?
Posted by Filippo Portolano almost 4 years ago
Bulk Update for Bid Modifier?
Hi everyone, as the title suggests, I'm trying to see if it's possible to do a bulk update for publisher_bid_modifer. Looking at https://developers.taboola.com/backstage-api/reference/bulk-update-campaigns, publisher_bid_modifier is.... not an option, but when having to do thousands of sites individually as PATCH operations... At some point it may be so long that the cronjob won't be finished before it kicks off again 24 hours later.
I don't know if it's possible, BUT... if it is, I'm POSTing to:
https://backstage.taboola.com/backstage/api/1.0/{$accountId}/campaigns/bulk-update
and my payload looks something like:
{"campaigns":[12345],"update":{"publisher_bid_modifier":{"values":[{"target":"abc123","cpc_modification":1.5}]}}}
Whenever I post it, I get back a 400, the error is usually something like:
{"http_status":400,"message":"Bad request","message_code":"api.action.bad_request.null"}
So... Is this possible, or do I have to patch? What's wrong with my payload that I'm posting, IF this is something we're able to do? Thank you!
Posted by James Taylor over 1 year ago
Duplicate A Campaign
## H3 Looks like something went wrong!
**Our server reports an error occurring while preparing this page. Please try again later once we have solved the problem.**
---
Every time [duplicate API](https://developers.taboola.com/backstage-api/reference#duplicate-a-campaign) is executed, 200 OK status with above error msg is received in HTML. Is this API ready to be used or is the sample call (below) constructed incorrectly?
https://backstage.taboola.com/backstage/api/1.0/`{{account id}}`/campaigns/`{{campaign id}}`/duplicate
with JSON body:
`{"name":"duplicate-or-clone-this-campaign"}`
Posted by Melody Song almost 4 years ago
Why do we can not update Lookalike Audience Targeting for the specified campaign?
We have a problem with updating Lookalike Audience Targeting for the specified campaign (https://developers.taboola.com/backstage-api/reference#update-lookalike-audience-targeting).
Here is an example request:
curl --location --request POST 'https://backstage.taboola.com/backstage/api/1.0/definitionorg-sc/campaigns/4074776/targeting/lookalike_audience' \
--header 'Authorization: bearer {token}' \
--header 'Content-Type: application/json' \
--data-raw '{"collection":[{"collection":[{"rule_id":238699,"similarity_level":5}],"type":"INCLUDE"}]}'
Here is the response:
{
"http_status": 400,
"message": "Collection contains invalid rule ids for targeting: [238699]",
"offending_field": "lookalike_audience_targeting.collection[0].collection"
}
Although if we check 238699 audience, we can see that it belongs to the same ad account as the campaign.
curl --location --request GET 'https://backstage.taboola.com/backstage/api/1.0/definitionorg-sc/universal_pixel/conversion_rule/238699' \
--header 'Authorization: bearer {token}'
What are we doing wrong? Please help us to resolve this problem.
Posted by Alex Kolesnykov about 4 years ago