Skip to content
GTM Tech News
Back to All news

Metadata adds X campaign management and finer LinkedIn company-size targeting

Metadata's July 2 release notes added X ad campaign controls and split LinkedIn's 1,000 to 5,000 employee band into four buckets.

Metadata's Classic platform release notes for July 2, 2026 added management of X ad campaigns, per-campaign overrides of budget-group rules and finer LinkedIn company-size targeting. Users can launch, pause, restart and edit X campaigns with text, image, video and carousel promoted posts through the X Ads API. LinkedIn's 1,000 to 5,000 employee range is now split into four targeting buckets. A July 16 release followed with campaigns that run without an end date and LinkedIn predictive audience sync.

The details

  • Per-campaign overrides let users set custom CPC or CPV parameters on individual campaigns within a budget group.
  • Budget groups can pause campaigns when goals are met and move remaining budget to other campaigns or experiments.
  • The new LinkedIn buckets are 1,000 to 2,000, 2,001 to 3,000, 3,001 to 4,000 and 4,001 to 5,000 employees.
  • Campaigns with no end date cannot use total or lifetime budgets.
  • The July 16 release also applied Meta placements at the ad-set level and added an open-rate column for Conversation Ads experiments.

Context

Metadata publishes Classic release notes every 14 days, and the page lists 17 releases with 88 features and 22 fixes. The site also offers MetadataONE as a separate product, and a September 10, 2026 release added a login chooser for users with access to both platforms. On September 24 Metadata added G2 Buyer Intent token validation and LinkedIn permission checks. The July releases do not mention MetadataONE.

Not disclosed

  • Pricing or plan availability for X campaign management
Discuss this with peers in the ForgeX Community
Announcement type
Feature update
Release notes from Metadata.io, published Jul 2, 2026
help.metadata.io
Added to GTM Tech News on Jul 2, 2026. Written up by ForgeX from the source; the vendor did not review it.
Open
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.

cora@forgex.ai