Connect Amazon DSP to PostgreSQL

Add Amazon DSP in Sources and connect the existing PostgreSQL database in Storage. A datastream defines the route, while the job loads the chosen fields into "ad groups".

Select concrete Amazon DSP fields such as 3P Fees, 3P Pre Bid Fee, 3P Pre Bid Fee Double Verify, and Normalized Week of the year. You can rename the chosen columns, preview the result, and write them to PostgreSQL tables such as accounts, advertisers, and campaigns.

Define the first Amazon DSP fetch, run frequency, and lookback window in the "ad groups" job. Each scheduled run replaces data inside the configured period.

Use a supported date field to partition "ad groups". Recurring Amazon DSP runs can then update the selected window instead of adding another copy of the same period.

With Amazon DSP data, a PostgreSQL query can summarize spend, impressions, clicks, and click-through rate by campaign. Model 3P Fees and 3P Pre Bid Fee in SQL, then expose the result to dashboards, internal tools, or recurring client reports.

Yes. Connect an existing PostgreSQL database first. The Catchr job creates and populates the destination table you configure inside that database.

Yes. Create a separate datastream and job for each source, write each export to its own table, then combine the data downstream with SQL, views, or your BI tool.