MediaGo is a native-advertising demand-side platform (DSP), part of the Mobvista/Mintegral family of ad-tech products, used by advertisers — particularly cross-border e-commerce brands — to run campaigns across a native ad publisher network. The Daton connector for MediaGo replicates your ad account structure, campaigns, and ad-level creative data, along with campaign-level and ad-level performance reporting at both daily and hourly granularity, including breakdowns of impressions, clicks, spend, and conversions across a range of e-commerce conversion event types (add to cart, purchase, lead, and others).
Prerequisites
An active MediaGo advertiser account with API access enabled.
An API Token for your MediaGo account.
Knowledge of the timezone your MediaGo account uses for reporting (Daton needs this to align report data correctly).
How to Obtain Your Credentials
MediaGo doesn't offer self-serve API token generation in its advertiser UI. The API Token is a Base64-encoded credential issued directly by your dedicated MediaGo Account Manager (AM).
Contact your dedicated MediaGo AM and request your client-level API Token.
Keep the token handy — you'll enter it in the Daton setup wizard along with your account's reporting timezone.
Confirm with your AM the timezone your account's reporting data is generated in, since this determines how you configure the connector.
Steps to Integrate
Integration Name: Enter a name to identify this integration in Daton.
Description (optional): Enter a description to help identify this integration later. You can change this at any time.
Replication Frequency: Choose how often Daton should run replication jobs — 1h, 2h, 3h, 6h, 8h, 12h, or 24h. More frequent replication can affect billing.
Replication Start Date: Select the historical start date for data replication. Note that campaigns are synced incrementally (new and updated records) based on this date; if you need campaign history further back, contact Daton support for a one-time rollback.
Lookback Window For Reports: Choose how many days Daton should look back when pulling report data — 1, 15, 30, or 45 days — to account for attribution changes that MediaGo may apply retroactively to conversion data.
Loading Mode: Choose Append (Daton adds new rows) or Upsert (Daton inserts and updates rows based on primary keys).
Loading Nested Objects: Choose how nested data (such as the ads record in the campaigns table) should be unnested in your warehouse — inherit from warehouse settings, do not unnest, up to one level, or up to two levels.
Authenticate: Enter your API Token and select the Timezone to pull the report from MediaGo (America/New_York, UTC, or Asia/Shanghai).
Select Ad Accounts: Choose which MediaGo ad accounts (by account name and account ID) Daton should sync data for.
Select Tables: Choose which of the available tables (campaigns, campaign_daily_report, campaign_hourly_report, ad_daily_report, ad_hourly_report) to replicate.
Configure Schema/Columns: Review and select the columns to include for each table, and confirm how they'll be structured in your destination warehouse.
Submit: Complete the setup to save and start the integration.
Supported Tables
Table
Full Load Supported
Notes
campaigns
Yes
Campaign metadata, including the account and ads associated with each campaign.
campaign_daily_report
No
Daily campaign-level performance and conversion metrics. Incremental sync only.
campaign_hourly_report
No
Hourly campaign-level performance metrics. Incremental sync only — maximum ~4 days of history available from the MediaGo API.
ad_daily_report
No
Daily ad-level performance and conversion metrics. Incremental sync only.
ad_hourly_report
No
Hourly ad-level performance metrics. Incremental sync only — maximum ~4 days of history available from the MediaGo API.
Table Schemas
campaigns
Column
Type
Description
campaign_id (Primary Key)
STRING
Unique identifier for the campaign.
account_id (Primary Key)
STRING
Identifier of the MediaGo ad account that owns the campaign.
campaign_name
STRING
Name of the campaign.
ads
RECORD (repeated)
Nested list of ads belonging to the campaign. Each entry contains ad_id (STRING) and ad_name (STRING). How this nested data is flattened in your warehouse depends on the Loading Nested Objects setting.
campaign_daily_report
Column
Type
Description
account_id (Primary Key)
STRING
Identifier of the MediaGo ad account.
id (Primary Key)
STRING
Identifier of the campaign for this report row.
date (Primary Key)
DATE
Report date.
name
STRING
Campaign name.
status
NUMERIC
Numeric status code of the campaign at the time of reporting.
cpc
NUMERIC
Average cost per click.
spend
NUMERIC
Total amount spent.
impression
NUMERIC
Total impressions served.
click
NUMERIC
Total clicks recorded.
conversion
NUMERIC
Total conversions recorded.
roas
NUMERIC
Return on ad spend.
cv_search
NUMERIC
Conversion count for the "search" event type.
cv_view_content
NUMERIC
Conversion count for the "view content" event type.
cv_app_install
NUMERIC
Conversion count for the "app install" event type.
cv_complete_registration
NUMERIC
Conversion count for the "complete registration" event type.
cv_add_to_cart
NUMERIC
Conversion count for the "add to cart" event type.
cv_add_paymentInfo
NUMERIC
Conversion count for the "add payment info" event type.
cv_start_checkout
NUMERIC
Conversion count for the "start checkout" event type.
cv_purchase
NUMERIC
Conversion count for the "purchase" event type.
cv_add_to_wishlist
NUMERIC
Conversion count for the "add to wishlist" event type.
cv_lead
NUMERIC
Conversion count for the "lead" event type.
cv_other
NUMERIC
Conversion count for the "other" event type.
cv_lead_qualified
NUMERIC
Conversion count for the "lead qualified" event type.
cv_call_connected
NUMERIC
Conversion count for the "call connected" event type.
cv_appointment_booked
NUMERIC
Conversion count for the "appointment booked" event type.
cv_application_started
NUMERIC
Conversion count for the "application started" event type.
cv_application_approved
NUMERIC
Conversion count for the "application approved" event type.
cv_account_created
NUMERIC
Conversion count for the "account created" event type.
cv_deal_completed
NUMERIC
Conversion count for the "deal completed" event type.
campaign_hourly_report
Column
Type
Description
account_id (Primary Key)
STRING
Identifier of the MediaGo ad account.
campaign_id (Primary Key)
STRING
Identifier of the campaign.
date (Primary Key)
DATETIME
Report date and hour.
spend
NUMERIC
Total amount spent in the hour.
impression
NUMERIC
Total impressions served in the hour.
click
NUMERIC
Total clicks recorded in the hour.
Only spend, impression, and click are available at hourly granularity for campaigns — conversion breakdowns are only available in campaign_daily_report.
ad_daily_report
Column
Type
Description
account_id (Primary Key)
STRING
Identifier of the MediaGo ad account.
ad_id (Primary Key)
NUMERIC
Identifier of the ad.
date (Primary Key)
DATE
Report date.
ad_name
STRING
Name of the ad.
title
STRING
Ad creative title/headline.
img_url
STRING
URL of the ad creative image.
brand_name
STRING
Brand name associated with the ad.
campaign_id
STRING
Identifier of the campaign the ad belongs to.
campaign_name
STRING
Name of the campaign the ad belongs to.
status
NUMERIC
Numeric status code of the ad at the time of reporting.
cpc
NUMERIC
Average cost per click.
spend
NUMERIC
Total amount spent.
impression
NUMERIC
Total impressions served.
click
NUMERIC
Total clicks recorded.
conversion
NUMERIC
Total conversions recorded.
roas
NUMERIC
Return on ad spend.
cv_search
NUMERIC
Conversion count for the "search" event type.
cv_view_content
NUMERIC
Conversion count for the "view content" event type.
cv_app_install
NUMERIC
Conversion count for the "app install" event type.
cv_complete_registration
NUMERIC
Conversion count for the "complete registration" event type.
cv_add_to_cart
NUMERIC
Conversion count for the "add to cart" event type.
cv_add_paymentInfo
NUMERIC
Conversion count for the "add payment info" event type.
cv_start_checkout
NUMERIC
Conversion count for the "start checkout" event type.
cv_purchase
NUMERIC
Conversion count for the "purchase" event type.
cv_add_to_wishlist
NUMERIC
Conversion count for the "add to wishlist" event type.
cv_lead
NUMERIC
Conversion count for the "lead" event type.
cv_other
NUMERIC
Conversion count for the "other" event type.
cv_lead_qualified
NUMERIC
Conversion count for the "lead qualified" event type.
cv_call_connected
NUMERIC
Conversion count for the "call connected" event type.
cv_appointment_booked
NUMERIC
Conversion count for the "appointment booked" event type.
cv_application_started
NUMERIC
Conversion count for the "application started" event type.
cv_application_approved
NUMERIC
Conversion count for the "application approved" event type.
cv_account_created
NUMERIC
Conversion count for the "account created" event type.
cv_deal_completed
NUMERIC
Conversion count for the "deal completed" event type.
ad_hourly_report
Column
Type
Description
account_id (Primary Key)
STRING
Identifier of the MediaGo ad account.
ad_id (Primary Key)
STRING
Identifier of the ad.
date (Primary Key)
DATETIME
Report date and hour.
campaign_id
STRING
Identifier of the campaign the ad belongs to.
spend
NUMERIC
Total amount spent in the hour.
impression
NUMERIC
Total impressions served in the hour.
click
NUMERIC
Total clicks recorded in the hour.
Only spend, impression, and click are available at hourly granularity for ads — conversion breakdowns are only available in ad_daily_report.
Replication & Sync Behavior
Lookback Window For Reports: Choose 1, 15, 30, or 45 days. On each run, Daton re-pulls report data for this trailing window so that conversion and attribution changes MediaGo applies retroactively are captured.
Loading Mode: Append (insert-only) or Upsert (insert and update based on primary keys) — controls how new and changed rows are written to your destination tables.
Loading Nested Objects: Controls how the nested ads record in the campaigns table is unnested into your warehouse — inherit from warehouse settings, do not unnest, or flatten up to one or two levels.
Hourly report history is limited: campaign_hourly_report and ad_hourly_report only expose approximately 4 days of history through the MediaGo API. Even if you select an earlier Replication Start Date, Daton cannot backfill hourly data beyond that window — only the daily report tables support longer historical backfill.
Ad Account selection determines scope: Only the ad accounts you select in the Select Ad Accounts step are synced. To add or remove accounts later, you'll need to reconfigure the integration.
campaigns supports full load; the four report tables (campaign_daily_report, campaign_hourly_report, ad_daily_report, ad_hourly_report) are incremental-only and sync based on the Replication Start Date and Lookback Window settings.
