Connect X (Twitter) Ads to Supabase
Send X (Twitter) Ads campaigns, accounts, funding instrument and 4 more report types to Supabase on a schedule. Pick the ad accounts and filter by date. Refresh as often as every 15 minutes.
twitter_ads
campaignaccountfunding_instrumentad_group_line_itemmedia_creative- 2 more report types
How to connect X (Twitter) Ads and Supabase
7 steps. You can preview the X (Twitter) Ads data in Coupler.io before anything reaches Supabase.
Step 1 of 7
Connect X (Twitter) Ads
Sign in to X (Twitter) Ads and authorize Coupler.io. There's no API key to copy.
Step 2 of 7
Choose what to export
Pick the X (Twitter) Ads data you want in Supabase.
Step 3 of 7
Set the report period
Choose the date range the report covers.
Step 4 of 7
Pick metrics and dimensions
Choose what to measure and how to break it down.
Step 5 of 7
Fine-tune the export
Optional settings for this X (Twitter) Ads export.
Step 6 of 7
Connect Supabase
Enter the connection details from your Supabase project's Connect panel, then the schema and table for the X (Twitter) Ads data.
Show 3 more fields Show fewer fields
Step 7 of 7
Choose a write mode and schedule
Every run either replaces or appends the data in Supabase. Run it as often as every 15 minutes.
Each run deletes the existing rows in campaign and loads fresh X (Twitter) Ads data.
Coupler.io made it easy to create dashboards and reports from different data sources. The sync is reliable and the user experience is amazing.
Take your data analytics to the next level
Sign Up with Google
Sign Up with MICROSOFT
SIGN UP WITH EMAIL
By signing up to Coupler.io, you agree to our Privacy Policy and Terms of Use.
Build your X (Twitter) Ads integrations with these destinations
Get the most of X (Twitter) Ads to Supabase integration
Gather data
Understand data
Automate data
Act on data
7 report types, including Campaign, Account, Funding instrument, Ad group (Line item) and Media creative.
You sign in to X (Twitter) Ads and authorize Coupler.io. There's no API key to copy.
Yes. Set the start date and end date to cover the period you need. Splitting the data by period is available too.
Yes. On the first successful run, Coupler.io creates the twitter_ads schema and the campaign table if the database user has the privileges to do so, and detects column types from the X (Twitter) Ads data.
Its writes aren't governed by RLS policies, and the tables it creates have RLS turned off. Keep X (Twitter) Ads data in a schema your app doesn't expose through the Data API.
On a schedule you choose, from monthly down to every 15 minutes, depending on your Coupler.io plan.
Yes. Add more sources to the same data flow, for example Google Ads or Facebook Ads, and join or append them before the data reaches Supabase.