Clay Ads syncs CRM-based audiences and exclusion lists to LinkedIn and Meta
Clay's February 25, 2026 changelog adds automatic syncing of CRM-based ad audiences to LinkedIn and Meta, dynamic exclusion lists and enriched lookalike audiences, with daily or every-two-day refresh.
By Cora Whitley, GTM AI Analyst, Chief of StaffClay published a changelog entry on February 25, 2026 covering three Ads capabilities for LinkedIn and Meta: CRM-powered audience syncing, dynamic exclusion lists and enriched lookalike audiences for Meta. The entry describes setup through the Actions menu and Salesforce filters, and says audiences update automatically as CRM data changes, with new opportunities suppressed the following day. Clay states the workflow replaces manual CSV uploads to each ad platform, and links to setup documentation.
The details
- Audiences sync to LinkedIn and Meta on a daily or every-two-day schedule.
- One Clay table can feed both LinkedIn and Meta audiences.
- Exclusion lists update as leads become opportunities or trials convert to customers.
- Clay says enriching with personal emails or mobile numbers raises Meta match rates from about 30% to over 70%.
Context
Clay later expanded Ads in August 2026 with Vibe, Bing and Reddit as audience destinations, which we covered on August 4. Its changelog also lists LinkedIn company list syncing in September 2026. Other 2026 Clay launches in our coverage include Audiences in June, Workflows in beta in August and Sequencer general availability in September.
Not disclosed
- Pricing or credit cost for ad audience syncs
- Whether CRMs other than Salesforce are supported as sources
- Methodology behind the match rate and cost per lead figures
- Vendor
Clay- Category
- Data & Enrichment
- Announcement type
- Feature update
Report an error
Vendors and readers can flag a factual error in this story, or ask for an image or logo to be removed. Email Cora, the editor, with the link. Image and logo removals happen within one business day. For factual corrections, Cora replies with next steps and a ForgeX lead approves the fix before it is published.
