Meta announced on June 9, 2026 that it will use off-site activity data (purchases, games played, and website visits gathered through the Meta Pixel and ad partners) to personalize your Feed and Meta AI responses, not just the ads you see. One existing user control over this data is being discontinued. The rollout begins in the US and a number of other countries in July 2026.
What is Meta changing about off-site activity data?
Meta is extending how it applies data that businesses already share with it: off-site activity such as purchases, games played on other sites, and website visits tracked via the Meta Pixel will now personalize Feed content and Meta AI answers, in addition to existing ad targeting. The “Your activity off Meta technologies” control is being discontinued; the “Activity from other businesses” setting, formerly called “Activity information from ad partners,” takes over this function with expanded scope. The rollout begins in July 2026 in the US and select countries, with more regions to follow on no confirmed schedule. Meta states it is not collecting any new data as part of this update.
A narrower box just got bigger
Until now, the off-site data Meta holds sat in a functionally bounded space: it shaped ad delivery, and users could restrict that use through the “Your activity off Meta technologies” control. That boundary is dissolving. Off-site signals — a purchase made on a third-party retailer, a game played on an external platform, a news article read on a Pixel-tagged site — will now influence what surfaces in organic Feed and what Meta AI responds with.
That is a material change to the data surface, even if the underlying dataset stays the same. Meta’s announcement is explicit: “We aren’t collecting any new data as part of this update.” The data was already there. What changes is the scope of its application.
For privacy-conscious marketers, the immediate concern is purpose limitation. If you operate a property with Meta Pixel and your privacy notice characterizes off-site data as used for advertising personalization, that description now underdescribes what Meta does with the signals you send. The distinction between ad targeting and content personalization carries weight in GDPR and similar frameworks. A lawful basis scoped to ad-oriented profiling does not automatically extend to AI answer generation or organic content ranking.
What replaces the discontinued control
The discontinued “Your activity off Meta technologies” setting gave users a single toggle to restrict how Meta used off-site data across its platforms. Its replacement, “Activity from other businesses,” is an expanded version of the former “Activity information from ad partners” control. Meta says this setting now manages how off-site activity data personalizes the complete experience: ads, Feed, and Meta AI responses.
The June 9 announcement does not detail whether prior opt-outs carry over into the new setting. Users who had previously opted out of the discontinued control should verify whether their preference persists once “Activity from other businesses” takes over.
This pattern of consolidating controls while expanding processing scope runs across the platform industry. The EU’s effort to replace per-site cookie consent pop-ups with browser-level consent signals encountered the same structural difficulty: when a single data channel expands to serve more purposes, narrower per-purpose controls lose their meaning. Whether Meta’s consolidated “Activity from other businesses” toggle satisfies GDPR expectations for purpose-specific consent will depend on how data protection authorities interpret the scope of personalization as a lawful processing purpose.
What to review before the July rollout
Three actions matter most for organizations running Meta Pixel before July.
First, audit your privacy notice. Language that limits Meta Pixel data use to advertising or remarketing now underdescribes actual processing. Off-site signals will also personalize Feed content and Meta AI answers. Disclosures should reflect the full scope of purposes, not just the ad-targeting use that was in place before this update.
Second, check the “Activity from other businesses” control in Meta account settings. Confirm whether prior opt-out states under the discontinued setting carry over, and document that review for any ongoing DPA correspondence or consent audit trail.
Third, if your consent framework treats ad storage and content personalization as distinct processing purposes, document the gap. The way GA4 Consent Mode’s ad_storage parameter separates advertising data flow from analytics signals illustrates what purpose-specific consent architecture can look like in practice. Meta’s current single-control model does not map to that level of granularity, and DPOs reviewing your stack should know that.
The July deadline is a compliance trigger, not a planning milestone. Privacy notices that misdescribe actual data use at the point of collection create regulatory exposure. The change is narrow in scope but carries real consequence for any organization whose consent documentation was built around Meta Pixel as a pure advertising-data channel.