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 over 1 year ago

ANSWERED

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 almost 2 years ago

ANSWERED

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 about 2 years ago

ANSWERED

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 about 2 years ago

1500 3000 301 400 401 403 404 429 4_flows 500 503 90_days access_token account account_creation account_id account_level account_level_block account_type accounts activity_schedule actual_cpc advertiser_id advertisers allowed_accounts alphabetic api_access api_changes api_key api_newsletter api_secret audience audience_onboarding audience_segments audience_targeting audiences audit_trail authorization_code auto_targeting aws_downtime aws_server balance base basic_authentication bi bid bid_modifier bid_modifiers billing billing_cycle block block_publisher block_publishers brand_safety browser_breakdown bulk_create bulk_update bulk_update_campaigns by_audience by_campaign by_hour_of_day caching campaign campaign_day campaign_day_breakdown campaign_fields campaign_learning campaign_level campaign_owner campaign_site_day campaign_summary campaigns city_targeting click_id clicks client_credentials code_snippet connector content-type conversion_data conversion_rule conversions conversions_value cors countries country country_codes cpa_actions cpa_actions_num cpc cpc_macro create_campaign create_item create_time creation_date custom_audience custom_audience_rule custom_conversion_rule custom_conversions cut_off daily_cap daily_spend data_freshness data_studio data_studio_connector day day_dimension delay delete dictionary different_account discrepancy docs_issue documentation domain duplicate duplicate_campaign empty_response end_date event_based exelate feature_request fetch_level filters first_party_audience flow full_authentication get_account_details google_apps_script google_script google_sheets hidden_audience hidden_segments hourly hourly_reporting hourly_spend html html_login_page html_response ias implicit_flow inactive_accounts include_multi_conversions inclusions integration internal_support_ticket ip_address is_atomic item items ixudra_curl java_client_sdk java_sdk javascript js jupyter_notebook laravel learning_state limit list_of_publishers lookalike_audience lookalike_audiences lookback_window loss_of_scale macros malformed_json marketplace marketplace_audiences max_campaigns max_items max_results minimum_bid minimum_cpc mixedanalytics my_audiences network network_account new_feature null numeric_site_id oauth2 os_breakdown page_view paging partner_type password_credentials patch pause permissions php pixel_lookalike placement placement_breakdown placement_filter placement_name platform_targeting postman precanned prerequisites_not_met publisher publisher_bid_modifier publisher_blocks publisher_id publisher_name publisher_network publisher_reports publisher_targeting publisher_url publishers python python_client r rate_limit real_time real_time_reporting recommendation_api redirect_uri rejected_campaigns remove_all report_caching reporting reporting_discrepancy reports retention_period revenue revenue_summary revenue_summary_report roadmap s2s safety_rating sales sandbox scale site site_breakdown site_name slow slowness sort_filter special_chars spend spending_limit ssl sso status sub_accounts supermetrics support_ticket ta taboola_ads taboola_pixel targeting tcc test_account theoptimizer timeout timezone tls top_campaign_content top_content tracking_code typo ui unblock_publishers unknown_publisher update_item upload_image url user_accounts user_segments utm value video video_campaign_summary video_campaigns video_completions video_item video_items views visit_value voluum web_hooks whitelist x-www-form-urlencoded yearly_reporting נ