Some fields needed to run for Amazon Seller central and Amazon Ads#1958

Sponsored Products targeting data is missing key fields. The amazon_ads connector’s sponsored_products_targeting table returns keyword/campaign/performance metrics (clicks, cost, sales, ACOS, etc.) but has no bid, match_type, or enabled/paused state field. Ask them to add these — without them, Windsor’s Amazon Ads data can’t support any bid-management or optimization use case, only reporting.

Amazon Ads data is capped at a 60-day lookback. Confirmed via an explicit error: “Amazon Advertising API returns data only for the last 60 days.” Ask whether Windsor maintains its own historical warehouse once an account is connected (so day 61+ isn’t lost once it ages out of Amazon’s live API), or if 60 days is a hard ceiling regardless of connection length. If it’s the latter, ask if there’s a workaround (e.g., a standing export/sync you can trigger periodically to build your own history over time).

Per-ASIN (childasin-dimensioned) queries on amazon_sp time out. Tested across every window size (60d, 30d, 7d) with and without explicit ASIN filters — all timed out except one lucky last_7d pull with no explicit date range. Account-level (non-ASIN) queries on the same connector worked fine even at 60 days, so this looks like a specific performance issue with that dimension for this account, not a general capacity problem. Can you please check backend query performance for childasin on account [bluepoppy] specifically.

Settlement report queries time out entirely. Note: I see settlement_report_data_flat_file_v2 was updated with new fields (Transaction status, Transaction Release Date) about a month ago per your community forum, so I know this report is actively maintained — which makes the consistent timeout on all queries (90d/30d/7d, all within your stated 90-day limit) look like an account-specific performance issue rather than a report-level problem. Can you check why queries against this report aren’t completing for account [bluepoppy]?

No Subscribe & Save data source. Confirmed no subscription-related table exists anywhere in the amazon_sp schema (checked ~914 fields for anything matching “subscribe” or “sns” — nothing). Is this on your roadmap?