Home > Destinations > PostgreSQL > Teads

Connect Teads to PostgreSQL

Connect Teads to PostgreSQL and export selected accounts, metrics, and dimensions to your PostgreSQL project.

Configure the historical window, destination table, and recurring schedule without maintaining a Teads API pipeline.

Used by the world's leading companies

Export Teads data to PostgreSQL

Catchr handles extraction, normalization, and loading automatically.

Centralize

Centralize Teads data in PostgreSQL

Bring all your Teads data into your warehouse and make it available for analytics, machine learning, and internal applications.

Data freshness

Keep your PostgreSQL tables up to date

Automatically sync new data from Teads so every dashboard, model, and report works with fresh information.

Analysis

Unify Teads with the rest of your business data

Join marketing, finance, CRM, and product data inside the same warehouse.

Teads metrics and dimensions available in PostgreSQL

Access 56 metrics and 78 dimensions from Teads connectors including Impressions, Clicks, Clickthrough Rate, Budget Spent, Post Click Conversions, Post View Conversions, Video Completion Rate, Valid and Viewable %, Date, Campaign Name, Advertiser Name, Line Item Name, Creative Name, Device, Country Name, Website or App, Video or Display and many more...

56

Metrics availables

78

Dimensions availables

Connect Teads to PostgreSQL in minutes

Move your data from Teads to PostgreSQL with a simple setup. Once connected, Catchr handles the ingestion automatically so your warehouse stays up to date without manual work.

Step one

Connect your Teads account

Authenticate your Teads account securely in Catchr. No custom scripts, API maintenance, or engineering work required.

Client A · Connected sources
5 sources ready
Teads 3 advertising accounts Connected
Google Ads 2 advertising accounts Connected
Google Analytics 4 1 web property Connected
HubSpot 1 CRM portal Connected
Step two

Choose the PostgreSQL destination

Add the database host and credentials once. Catchr checks the connection so your exports start with a reachable destination.

Destination / PostgreSQL Required fields
Host Required
warehouse.company.net
Username Required
catchr_writer
Password Required
••••••••••••
Database Required
marketing
Step three

Keep your PostgreSQL tables updated

Choose the fields, initial history, partition field, and recurring schedule for the job. Catchr refreshes the configured import window in your PostgreSQL table.

Export job / PostgreSQL Example
Schema Destination
marketing_raw
Table Per job
linkedin_ads_daily
Recurring schedule Choose a cadence
Every 6 hours
Daily · 07:00
Weekly · Mon
First sync scheduledSelected fields · configured history
07:00 UTC

Review 30-day Teads campaign delivery in SQL.

This example summarizes spend, impressions, clicks, and click-through rate by campaign.

Teads.sql
BigQuery SQL
30-day window
SELECT
  campaign_name,
  SUM(spend) AS spend,
  SUM(impressions) AS impressions,
  SUM(clicks) AS clicks,
  SAFE_DIVIDE(
    SUM(clicks),
    SUM(impressions)
  ) AS ctr
FROM `your_project.marketing_raw.teads_daily`
WHERE date >= DATE_SUB(
  CURRENT_DATE(),
  INTERVAL 30 DAY
)
GROUP BY campaign_name
ORDER BY spend DESC;
Illustrative SQL — adapt it to the fields and schema selected in your export. Standard SQL

Choose what to load into PostgreSQL.

Each connector has its own entities, fields, historical limits, and reporting uses. Open a source page for the details that belong to that platform.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Before you schedule the job.

Answers about PostgreSQL setup, available source data, schedules, table updates, and SQL use cases.

How do I start a scheduled Teads import into PostgreSQL?

Start with a connected Teads source and an existing PostgreSQL database. Create a datastream between them, then configure the accounts, fields, schedule, and "accounts" table.

Which Teads entities can become PostgreSQL tables?

Select concrete Teads fields such as Billable Events, Budget Delivered Total Ad Cost - Cost per Result, Budget Delivered Total Ad Cost - CPC, and Day of the month. You can rename the chosen columns, preview the result, and write them to PostgreSQL tables such as accounts, advertisers, and campaigns.

Does Catchr support an initial fetch for Teads data in PostgreSQL?

Set an initial fetch period for Teads, then choose the frequency and lookback window for the job writing to "accounts". Catchr rewrites that selected period on each run.

Which partition setting keeps Teads PostgreSQL rows updated?

The partition field tells Catchr which Teads rows in "accounts" belong to the period being refreshed. If you omit it, every run appends records rather than updating them.

What is a practical SQL use case for Teads data?

With Teads data, a PostgreSQL query can summarize spend, impressions, clicks, and click-through rate by campaign. A query built around Billable Events and Budget Delivered Total Ad Cost - Cost per Result can support trend reviews, account comparisons, and operational reporting.

Does my PostgreSQL database need to exist before I connect it?

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

Can I load several marketing sources into the same Postgres 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.

Still have a question ? 

Our teams is always here to responds to any question you could have about our data connector. 

Your next database import should not start with five exports.

Connect your marketing platforms and build a data workflow your entire agency can use.

14 days free-trial
No credit-card required
100+ sources