> Note: This page is part of the DataDoe Docs. You can find the root of the documentation at `https://www.datadoe.com/hub/docs/basics/introduction-to-datadoe`. > JSON Table of Contents: `https://www.datadoe.com/hub/docs/toc.json`. > Data Scheme (Markdown index, one page per table): https://api.datadoe.com/api/v1/spec/data-scheme.md. Full JSON: https://api.datadoe.com/api/v1/spec/data-scheme. > Other pages in the DataDoe Docs: > - DataDoe Basics/Access & Users: `https://www.datadoe.com/hub/docs/basics/access-user-management.md` > - DataDoe Basics/Benefits: `https://www.datadoe.com/hub/docs/basics/benefits.md` > - DataDoe Basics/Connecting Accounts: `https://www.datadoe.com/hub/docs/basics/connecting-accounts.md` > - DataDoe Basics/External Invitation Links: `https://www.datadoe.com/hub/docs/basics/external-invitation-links.md` > - DataDoe Basics/Integrations: `https://www.datadoe.com/hub/docs/basics/integration-customization.md` > - DataDoe Basics/Introduction to DataDoe: `https://www.datadoe.com/hub/docs/basics/introduction-to-datadoe.md` > - DataDoe Basics/Subscription and pricing: `https://www.datadoe.com/hub/docs/basics/subscription-pricing.md` > - DataDoe Data/Data Fetch Periods: `https://www.datadoe.com/hub/docs/datadoe-data/data-fetch-periods.md` > - DataDoe Data/Data Sources: `https://www.datadoe.com/hub/docs/datadoe-data/data-sources.md` > - DataDoe Data/Initial Loads: `https://www.datadoe.com/hub/docs/datadoe-data/initial-loads.md` > - DataDoe Data/Managing Data Tables: `https://www.datadoe.com/hub/docs/datadoe-data/managing-data-tables.md` > - DataDoe Data/Migrating from SellerBoard: `https://www.datadoe.com/hub/docs/datadoe-data/migrating-from-sellerboard.md` > - DataDoe Data/SQP Data: `https://www.datadoe.com/hub/docs/datadoe-data/search-query-performance.md` > - DataDoe Data/Timezones: `https://www.datadoe.com/hub/docs/datadoe-data/orders-purchase-date-timezones.md` > - DataDoe Data/Uploading COGS: `https://www.datadoe.com/hub/docs/datadoe-data/uploading-cogs.md` > - DataDoe Data/Uploading Vendor Codes: `https://www.datadoe.com/hub/docs/datadoe-data/uploading-vendor-codes.md` > - DataDoe Features/Actions: `https://www.datadoe.com/hub/docs/datadoe-features/actions.md` > - DataDoe Features/Actions - Manage Images: `https://www.datadoe.com/hub/docs/datadoe-features/actions-manage-images.md` > - DataDoe Features/Amazon Marketing Cloud: `https://www.datadoe.com/hub/docs/datadoe-features/amc.md` > - DataDoe Features/AMC query templates: `https://www.datadoe.com/hub/docs/datadoe-features/amc-query-templates.md` > - DataDoe Features/Features Overview: `https://www.datadoe.com/hub/docs/datadoe-features/overview.md` > - DataDoe Features/Files: `https://www.datadoe.com/hub/docs/datadoe-features/files.md` > - DataDoe Features/Plugins: `https://www.datadoe.com/hub/docs/datadoe-features/plugins.md` > - DataDoe Features/Usage Logs: `https://www.datadoe.com/hub/docs/datadoe-features/usage-logs.md` > - DataDoe Features/Webhooks: `https://www.datadoe.com/hub/docs/datadoe-features/webhooks.md` > - DataDoe Features/White label: `https://www.datadoe.com/hub/docs/datadoe-features/white-label.md` > - DataDoe MCP/Overview: `https://www.datadoe.com/hub/docs/datadoe-mcp/overview.md` > - DataDoe MCP/Using Antigravity: `https://www.datadoe.com/hub/docs/datadoe-mcp/antigravity.md` > - DataDoe MCP/Using ChatGPT: `https://www.datadoe.com/hub/docs/datadoe-mcp/chatgpt.md` > - DataDoe MCP/Using Claude: `https://www.datadoe.com/hub/docs/datadoe-mcp/claude.md` > - DataDoe MCP/Using Claude Agent SDK: `https://www.datadoe.com/hub/docs/datadoe-mcp/claude-agents-sdk.md` > - DataDoe MCP/Using Claude Code: `https://www.datadoe.com/hub/docs/datadoe-mcp/claude-code.md` > - DataDoe MCP/Using Codex: `https://www.datadoe.com/hub/docs/datadoe-mcp/codex.md` > - DataDoe MCP/Using Codex Sites: `https://www.datadoe.com/hub/docs/datadoe-mcp/codex-sites.md` > - DataDoe MCP/Using CrewAI: `https://www.datadoe.com/hub/docs/datadoe-mcp/crewai.md` > - DataDoe MCP/Using Cursor: `https://www.datadoe.com/hub/docs/datadoe-mcp/cursor.md` > - DataDoe MCP/Using Excel + Claude: `https://www.datadoe.com/hub/docs/datadoe-mcp/excel.md` > - DataDoe MCP/Using Gemini CLI: `https://www.datadoe.com/hub/docs/datadoe-mcp/gemini-cli.md` > - DataDoe MCP/Using Glama MCP Inspector: `https://www.datadoe.com/hub/docs/datadoe-mcp/glama.md` > - DataDoe MCP/Using Grok: `https://www.datadoe.com/hub/docs/datadoe-mcp/grok.md` > - DataDoe MCP/Using GrokBot: `https://www.datadoe.com/hub/docs/datadoe-mcp/grokbot.md` > - DataDoe MCP/Using Gumloop: `https://www.datadoe.com/hub/docs/datadoe-mcp/gumloop.md` > - DataDoe MCP/Using Hermes Agent: `https://www.datadoe.com/hub/docs/datadoe-mcp/hermes.md` > - DataDoe MCP/Using Littlebird: `https://www.datadoe.com/hub/docs/datadoe-mcp/littlebird.md` > - DataDoe MCP/Using n8n: `https://www.datadoe.com/hub/docs/datadoe-mcp/n8n.md` > - DataDoe MCP/Using NanoClaw: `https://www.datadoe.com/hub/docs/datadoe-mcp/nanoclaw.md` > - DataDoe MCP/Using OpenAI Agents SDK: `https://www.datadoe.com/hub/docs/datadoe-mcp/openai-agents-sdk.md` > - DataDoe MCP/Using OpenClaw: `https://www.datadoe.com/hub/docs/datadoe-mcp/openclaw.md` > - DataDoe MCP/Using OpenCode: `https://www.datadoe.com/hub/docs/datadoe-mcp/opencode.md` > - DataDoe MCP/Using PowerPoint + Claude: `https://www.datadoe.com/hub/docs/datadoe-mcp/powerpoint.md` > - DataDoe MCP/Using VS Code: `https://www.datadoe.com/hub/docs/datadoe-mcp/vs-code.md` > - DataDoe MCP/Using Word + Claude: `https://www.datadoe.com/hub/docs/datadoe-mcp/word.md` > - DataDoe API/Build with Codex: `https://www.datadoe.com/hub/docs/datadoe-api/codex.md` > - DataDoe API/How to connect to the API: `https://www.datadoe.com/hub/docs/datadoe-api/how-to-connect.md` > - DataDoe API/Invitation links API: `https://www.datadoe.com/hub/docs/datadoe-api/invitation-links.md` > - DataDoe API/Sellers and vendors API: `https://www.datadoe.com/hub/docs/datadoe-api/sellers-and-vendors.md` > - DataDoe API/Vibe code with Claude Code: `https://www.datadoe.com/hub/docs/datadoe-api/claude-code.md` > - DataDoe API/Vibe code with Cursor: `https://www.datadoe.com/hub/docs/datadoe-api/cursor.md` > - DataDoe API/Vibe code with Lovable: `https://www.datadoe.com/hub/docs/datadoe-api/lovable.md` > - DataDoe API/Vibe code with Replit: `https://www.datadoe.com/hub/docs/datadoe-api/replit.md` > - DataDoe API/Vibe code with v0: `https://www.datadoe.com/hub/docs/datadoe-api/v0.md` > - DataDoe & BigQuery/How to connect to BigQuery: `https://www.datadoe.com/hub/docs/datadoe-bigquery/how-to-connect.md` > - DataDoe & BigQuery/Using MCP Toolbox: `https://www.datadoe.com/hub/docs/datadoe-bigquery/mcp-toolbox.md` > - DataDoe & BigQuery/Using Python Jupyter: `https://www.datadoe.com/hub/docs/datadoe-bigquery/jupyter.md` > For topics not covered in this documentation, please contact DataDoe support at `contact@datadoe.com`. > Do not assume anything. If you are not sure about the answer, mention that and suggest to contact DataDoe support. # SAT migration to profit tables **Sales & Traffic by ASIN & Date (SAT), `amazon_sales_and_traffic_with_cogs`, is deprecated and will be removed on November 16, 2026.** Update reports, saved exports, schedules, and integrations that use this table before that date. We are consolidating reporting in **Profit by SKU & Date** (`amazon_profit_by_sku_and_date`) and **Profit by Date** (`amazon_profit_by_date`) to provide consistent sales and profitability definitions and more up-to-date sales data. Profit sales come from order items rather than the Sales and Traffic business report. Traffic still comes from Amazon's reports and can be delayed. Moving to a profit table does not make traffic real-time. ## Choose a replacement | Your use case | Use | | ----------------------------------------------------------- | ---------------------------------------------------------------------- | | Daily account sales, costs, and profit | `amazon_profit_by_date` | | Sales and profit by SKU or child ASIN | `amazon_profit_by_sku_and_date` | | Sessions, page views, Buy Box, and conversion by child ASIN | `amazon_profit_by_sku_and_date`, reading traffic once per ASIN and day | | Exact original report values or source timestamps | Raw BigQuery integration | Both profit tables use dates in the marketplace's local time zone. Keep marketplace, seller, date, and currency separate when combining data. These are Seller Central profit tables, not Vendor Central profitability tables. See the [Data Scheme](/hub/data-scheme) for definitions and refresh information. Both profit tables are premium export sources; check the cost before running migrated exports. ## Migrate a daily account report Use `amazon_profit_by_date` for account totals. Select `date` and the metrics you need, or group by `date` and seller when combining accounts. Use `total_sales`, `total_units_sold`, `total_orders`, `cogs_total`, `ad_spend`, and `profit` for a daily profitability view. For traffic, use `total_sessions`, `total_page_views`, and `avg_buybox_percentage`. These use Amazon's daily account totals, with a fallback to child-ASIN rows when account totals are missing. Columns starting with `asin_` describe aggregated child-ASIN traffic instead. Do not calculate account profit by adding SKU profits. The account table includes fees and advertising costs that cannot all be allocated to a SKU. For a date-range report, add amounts and counts, then calculate ratios from the totals. Do not add daily percentages or average Buy Box percentages without appropriate weighting. ## Migrate an ASIN traffic or conversion report Use `amazon_profit_by_sku_and_date` and retain `child_asin` and `date`. Sales and costs are per SKU, but traffic describes the child ASIN and repeats on its SKU rows. For each seller, marketplace, child ASIN, and day: - Add SKU sales, sold units, and costs. - Take `max` of `total_sessions`, `total_page_views`, and `avg_buybox_percentage` to read ASIN traffic once. - Apply the same rule to browser, mobile, and B2B traffic fields. - Keep traffic rows whose `sku` is null; an ASIN can have traffic without SKU sales activity that day. For several days, read traffic once per ASIN and day, then add daily sessions and page views. Taking `max` across the whole period returns only the largest daily value. Choose a consistent units definition when comparing conversion rates. A rate calculated from shipped units will not necessarily match Amazon's ordered-unit conversion percentage. ## Map SAT columns to profit columns These are the supported migration choices. Sales, units, order counts, and costs can change because the new tables use order and profitability definitions. | SAT column | Profit column and behavior | | -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `session` | `total_sessions`. Read once per ASIN and day in the SKU table. | | `browser_session` | `browser_sessions`. Read once per ASIN and day. | | `mobile_session` | `mobile_sessions`. Read once per ASIN and day. | | `page_views` | `total_page_views`. Prefer the current column over the legacy alias. | | `buybox_percentage` | `avg_buybox_percentage`. Prefer the current column. | | `buybox_percentage_b2b` | `avg_buybox_percentage_b2b`. Percentages are 0 to 100. | | `units_session_percentage` | `unit_session_percentage`. Keep report percentages separate from rates you calculate. | | `total_units` | `total_units_sold` for shipped sales; `total_units_b2b` + `total_units_b2c` for non-cancelled ordered quantities. Neither choice guarantees the original report value. | | `total_sales` | `total_sales`. SAT is ordered product sales; profit sales are shipped item revenue plus buyer-paid shipping, minus shipping promotions. | | `total_orders` | `total_orders`. SAT counts report order items; profit tables count distinct shipped orders within their grouping. | | `cogs_item_value` | `cogs_item`. Per-unit item cost becomes an aggregated shipped-item cost. | | `cogs_shipping_value` | `cogs_shipping`. Per-unit shipping cost becomes an aggregated cost. | | `cogs_total_value` | `cogs_total`. Includes shipped-item costs and lost/damaged or missing-return adjustments. | | `cogs_currency` | `currency` for profit reporting. Profit currency replaces the uploaded-cost currency field. | | `cogs_present` | `cogs_present`. Checks cost coverage across contributing shipped items and returns. | | `item_supplier_name` | `item_supplier_name`. Returns a comma-separated list of distinct suppliers for shipped items. | | `dt_created`, `dt_updated` | Raw report timestamps. No equivalent profit columns. | Keep fields such as `child_asin`, `parent_asin`, `product_name`, `browser_page_views`, `mobile_page_views`, and the matching B2B traffic fields where available. A matching name does not always mean the same calculation: profit `total_units_b2b` comes from non-cancelled order-item quantities. The SKU table's `units_refunded`, `refund_rate`, and shipped report fields remain report metrics per ASIN. In Profit by Date, these are account-level report metrics. Financial `refund_count` and physical `return_units` measure different events and are not substitutes for report refunded units. ## Update exports, schedules, and integrations 1. Find the replacement by its name or table name. For the application programming interface (API), use `GET /api/v1/exports/sources`; for Model Context Protocol (MCP), use `exports_sources_get`. 2. Read its columns. In MCP, call `exports_source_get` until `columnsMeta.hasNextPage` is false. Copy the returned source ID rather than constructing one. 3. Update the source, selected columns, aggregation inputs, grouping, filters, and sort fields. Keep aggregation aliases if you need the same output labels. 4. Update or recreate saved and scheduled exports with the replacement source. Existing SAT exports and schedules do not migrate automatically. 5. Run a sample for a completed period. Check field names, row counts, currency, and ordered-versus-shipped differences before switching your downstream report. For example, an export that sums `session` as `sessions` needs to sum `total_sessions` on Profit by Date. On the SKU table, read `max(total_sessions)` per ASIN and day instead. Update the aggregation input as well as the output name. ## Additional columns available after migration The following columns are in the profit tables but were not in SAT. Some are renamed replacements; others add sales, fees, advertising, or profitability detail. Supplier name already existed in SAT and is retained in both profit tables. ### Available in both profit tables | Area | Columns | | ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Profitability | `profit`, `total_cost`, `acos`, `tacos`, `roi` | | Sales and account detail | `sales_tax`, `sales_tax_missing_items`, `total_sales_b2b`, `total_sales_b2c`, `unshipped_sales`, `total_units_b2c`, `total_units_sold`, `total_units_sold_b2b`, `total_units_sold_b2c`, `currency` | | Refunds and returns | `refund_count`, `refund_cost`, `return_units` | | COGS and inventory adjustments | `return_cogs`, `cogs_item`, `cogs_shipping`, `lost_damaged_by_amazon`, `missing_returns`, `cogs_total` | | Amazon fees | `total_fees`, `total_selling_fees`, `total_fees_tax`, `total_fees_net`, `total_selling_fees_tax`, `total_selling_fees_net`, `fba_fees_tax`, `fba_fees_net`, `fba_fees`, `awd_fees` | | Advertising | `ad_spend`, `ad_sales`, `ad_orders`, `ad_units_sold`, `ad_clicks`, `ad_impressions` | | Traffic and conversion | `avg_buybox_percentage`, `avg_buybox_percentage_b2b`, `avg_buybox_percentage_b2c`, `total_sessions`, `sessions_b2c`, `total_page_views`, `page_views_b2c`, `browser_sessions`, `browser_sessions_b2b`, `mobile_sessions`, `mobile_sessions_b2b`, `browser_page_views_b2b`, `mobile_page_views_b2b`, `unit_session_percentage`, `unit_session_percentage_b2b` | ### Additional columns in Profit by SKU & Date | Area | Columns | | ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Product information | `sku`, `product_brand`, `product_category_root`, `product_category_node`, `product_image_url`, `product_url` | | Traffic and conversion | `browser_sessions_b2c`, `mobile_sessions_b2c`, `browser_page_views_b2c`, `mobile_page_views_b2c`, `session_percentage`, `session_percentage_b2b`, `page_views_percentage`, `page_views_percentage_b2b`, `browser_session_percentage`, `browser_session_percentage_b2b`, `mobile_session_percentage`, `mobile_session_percentage_b2b`, `browser_page_views_percentage`, `browser_page_views_percentage_b2b`, `mobile_page_views_percentage`, `mobile_page_views_percentage_b2b` | ### Additional columns in Profit by Date | Area | Columns | | ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Advertising | `sponsored_tv_ad_spend` | | Target reporting | `ad_target_reported_spend`, `ad_target_reported_sales`, `ad_target_count`, `ad_target_costed_sales`, `ad_target_costed_spend`, `ad_target_unsupported_sales`, `ad_target_missing_cost_sales`, `ad_target_costed_estimated_profit_after_ads`, `ad_target_mature_spend_without_sales` | | Search-term reporting | `ad_search_term_reported_spend`, `ad_search_term_reported_sales`, `ad_search_term_count`, `ad_search_term_costed_sales`, `ad_search_term_costed_spend`, `ad_search_term_unsupported_sales`, `ad_search_term_missing_cost_sales`, `ad_search_term_costed_estimated_profit_after_ads`, `ad_search_term_mature_spend_without_sales` | | Sales and account detail | `average_sales_per_order_item`, `average_sales_per_order_item_b2b`, `average_sales_per_order_item_b2c`, `average_units_per_order_item`, `average_units_per_order_item_b2b`, `average_units_per_order_item_b2c`, `average_offer_count`, `average_parent_items` | | Claims | `claims_granted`, `claims_granted_b2b`, `claims_granted_b2c`, `claims_amount`, `claims_amount_b2b`, `claims_amount_b2c` | | Feedback | `feedback_received`, `feedback_received_b2b`, `feedback_received_b2c`, `negative_feedback_received`, `negative_feedback_received_b2b`, `received_negative_feedback_rate`, `received_negative_feedback_rate_b2b` | | Traffic and conversion | `order_item_session_percentage`, `order_item_session_percentage_b2b` | | ASIN traffic | `asin_browser_sessions`, `asin_browser_sessions_b2b`, `asin_browser_sessions_b2c`, `asin_mobile_sessions`, `asin_mobile_sessions_b2b`, `asin_mobile_sessions_b2c`, `asin_browser_page_views`, `asin_browser_page_views_b2b`, `asin_browser_page_views_b2c`, `asin_mobile_page_views`, `asin_mobile_page_views_b2b`, `asin_mobile_page_views_b2c`, `asin_session_percentage`, `asin_session_percentage_b2b`, `asin_page_views_percentage`, `asin_page_views_percentage_b2b`, `asin_browser_session_percentage`, `asin_browser_session_percentage_b2b`, `asin_mobile_session_percentage`, `asin_mobile_session_percentage_b2b`, `asin_browser_page_views_percentage`, `asin_browser_page_views_percentage_b2b`, `asin_mobile_page_views_percentage`, `asin_mobile_page_views_percentage_b2b`, `asin_unit_session_percentage`, `asin_unit_session_percentage_b2b` | Target and search-term summaries overlap and must not be added together or added to account profit. Use each for its documented advertising analysis. ## Keep original report data with Raw BigQuery The underlying data remains available after integrated SAT is removed. Set up a **Raw data** integration using the [BigQuery connection guide](/hub/docs/datadoe-bigquery/how-to-connect). An Integrated data subscription does not provide access to the Raw dataset. Use `raw_sp_api_report_sales_and_traffic` for Amazon's child-ASIN report values, including `orderedProductSales`, `unitsOrdered`, `totalOrderItems`, and source timestamps. Raw field names differ from integrated names. For uploaded costs and suppliers, use `raw_amazon_cogs` with the appropriate product, connection, and effective date. The raw report does not include SAT's COGS join. Choose the applicable dated COGS record and avoid duplicate report rows. Raw access preserves source data, including Amazon's reporting delays and revisions. It does not reproduce SAT's integrated columns automatically. ## Need help? If you have questions about choosing a replacement, updating a schedule, or matching an existing report, [contact us or open a support ticket](https://forms.clickup.com/9015200219/f/8cnj2ev-38615/AOYF9I35QFOXWJQXIG?type=Form&source=hub-sat-migration-docs). Include the current source, columns, date range, and the result you need.