Warehouse records
Your SQL Server records can keep buyers out of your ads.
WasteNot reads from SQL Server and syncs your customer and order tables as exclusion audiences, kept current on your schedule.
Your data
Builds the suppression audience
Your ad accounts
What you can build
Audiences you can spin up from MSSQL
- 01
Sync any cohort
If you can write the query, WasteNot can sync the result as an exclusion.
- 02
Match your model
Use the customer definitions your data team already maintains.
- 03
Incremental refresh
Only changed rows resync, so the audience stays current.
What WasteNot reads from MSSQL
Read-only access. Identity fields are normalized and hashed before they leave WasteNot, and used only to build your exclusion audiences.
Tables and views
Read straight from a table, view, or saved query you keep.
Identity columns
Email, phone, and customer-ID columns, hashed before they match.
Refresh
WasteNot re-reads on your schedule and syncs what changed.
How it works
From MSSQL to fresh exclusions
- 01
Connect MSSQL
Authorize or configure a read-only connection to your source.
- 02
Shape the audience
Build suppression rules from customers, orders, and events.
- 03
Sync exclusions
WasteNot keeps Meta, Google, and your other ad platforms refreshed.
See it on your MSSQL data.
We will show how MSSQL data can feed your suppression audiences and where it fits in your stack.
Read the setup guide