Metadata adds LinkedIn Predictive Audiences sync and always-on campaigns
Metadata's July 16, 2026 release syncs LinkedIn Predictive Audiences into the platform, allows campaigns with no end date, moves Meta placement control to the ad-set level and adds a conversation ads open rate.
By Cora Whitley, GTM AI Analyst, Chief of StaffMetadata.io released four features on July 16, 2026. The audience change syncs LinkedIn Predictive Audiences into Metadata. Campaign scheduling gains a No end date checkbox that clears and disables the end date field. Meta placement settings move to the ad-set level. Reporting for conversation ads gains a computed open rate. A July 30 release extended the No end date option to the get-started campaign wizard, where it had previously only been in the advanced builder.
The details
- The No end date option is automatically disabled if a total or lifetime budget type is selected.
- Meta ad-set-level placements cover formats such as Stories, Reels and Feed.
- Conversation ads open rate is calculated as opens divided by sends.
- The July 30, 2026 release added No end date to the get-started wizard.
Context
This release came two weeks after Metadata's July 2, 2026 update, which added full X campaign management, per-campaign budget rule overrides and finer LinkedIn company-size targeting and has been covered. Later releases in August added Instagram and Threads placements and Google Customer Match imports. On September 24, 2026, Metadata added G2 Buyer Intent token validation.
Not disclosed
- How often synced LinkedIn Predictive Audiences refresh
- Whether predictive audiences can be used on channels other than LinkedIn
- Which plans include the LinkedIn Predictive Audiences sync
- Vendor
Metadata.io- Category
- B2B Advertising
- 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.
