Community Discussion

Posted by nithu almost 2 years ago

The spent column discrepancies for different dimensions (API reports)

We build a campaign reporting tool, using the Taboola API (among others). What we are trying to do is to see daily/hourly reports that show campaign/hour breakdown for money spent on Taboola per campaign. What is important for us for the hourly report is the ability to see campaign results in nearly real-time (let's say with a 1-hour delay - hence we would like to use the campaign_hour_breakdown dimension). It seems to be working almost fine. However, there are some discrepancies I don't understand. Has anyone experienced such weird behavior? We use the "Campaign Summary Report" with 3 different dimensions - day, campaign_hour_breakdown, and campaign_breakdown. I would expect that the sum of the spent column will always be the same regardless of the dimension we use. However, the numbers are slightly different, e.g. I ran three different reports/breakdowns for the same day. Here are the spent sums per each dimension: - campaign_hour_breakdown: $3,266.07 - day: $3,395.99 - campaign_breakdown: $3,400.41 Can you explain the discrepancy, please? Also, I have noticed the "last-used-rawdata-update-time" attribute. What is its meaning? To me, it looks like all reports are generated with a certain delay. Does that mean we cannot rely on them for our hourly breakdowns? Please advise. Thank you.

real_time_reporting

Posted by Jacek Francuz about 2 years ago

ANSWERED

IS it possible to get actual reporting data without the delay using by_hour_of_day dimension

We are requesting reporting data using the by_hour_of_day dimension. Each start of the hour. And we found out that the values for that same hour are changing from while to while. Can you please tell us, when is the best time to request actual reporting data for the hour that passed. Thanks in advance

data_freshnessreal_time_reportingby_hour_of_dayconversion_datacustom_conversionsprecanned

Posted by Natalia Smirova over 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 client_id client_secret code_snippet connector content-type converesion_rule 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 cta 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 day_parting delay delete dictionary different_account discrepancy docs_issue documentation domain duplicate duplicate_campaign duplicate_campaigns 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 realtime_reports 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 נ

Live Reporting Api

The spent column discrepancies for different dimensions (API reports)

IS it possible to get actual reporting data without the delay using by_hour_of_day dimension