Meta Off-Platform Data Change: What Coaches Should Check

AdvLaunch is the AI agency for coaches and consultants. In our paid community program, we run paid Meta acquisition into paid communities, so a coach's pixel and server events are the first thing we check on every build. We sell that work, so weigh our advice accordingly. Below is Meta's own wording first, then what we would check in your account.

What Meta announced on June 9, 2026

Meta announced that it will stop offering the “Your activity off Meta technologies” setting and will expand “Activity from other businesses” to cover more uses of data that businesses already share with it. The first setting let a person disconnect activity that businesses send Meta from their account. The second, formerly called “Activity information from ad partners,” controls whether Meta uses that activity to personalise what the person sees.

The new part is where the data is used. Meta says it already uses information such as games played or purchases made on other websites to make ads more relevant, and that in future it will also use it to personalise Feed content and AI responses. Meta says it is not collecting any new data. If a person turns the setting off, Meta says it will not use that information to show more relevant ads or other content.

On timing, Meta said the control and data-use changes would take effect the following month in the US and a number of other countries, with more countries to follow. Meta's Help Center page for the setting adds that not everyone can see it in Accounts Center yet.

What the change means for a coach's ads, and what Meta has not said

For a coach running Meta ads, the announcement changes what Meta may do with signals your tracking already sends, not what you have to send. Nothing in Meta's post removes the Pixel, the Conversions API or Custom Audiences, and nothing in it says retargeting pools shrink.

The audience-size effect is where trade commentary and Meta part ways. One advertiser-side analysis expects website retargeting pools and Lookalike seeds to grow, because people who had disconnected their activity may become matchable again. That is an inference. Meta has published no size estimate, and that analysis says outright that no source quantifies the lift. Treat it as a hypothesis to measure in your own account, not a result.

What we could not confirm

Four things are unconfirmed as of October 8, 2026, and a page that skipped them would be guessing:

• The completed rollout date. Meta said the changes would take effect “next month,” meaning July 2026, in the US and a number of other countries. We found no Meta page confirming when each country finished, so check Accounts Center in your own account.
• Any effect on audience sizes or cost per lead. Meta has published no figure, so any percentage you read elsewhere is a guess.
• How the setting interacts with Custom Audiences you build from your own pixel events or customer lists. Meta's announcement does not address it.
• Treatment in the EU, the UK and other regions. Meta names only “the US and a number of other countries.”

The tracking baseline Meta documents: Pixel plus Conversions API

Meta recommends running the Conversions API alongside the Meta Pixel and sending the same events through both. The Conversions API connects your server, website platform or CRM to Meta, and Meta's best-practices page says the redundant setup captures events the Pixel can lose to network connectivity issues or page-loading errors.

Two events describing the same action are deduplicated only if they match. Meta's documentation says the Pixel eventID must equal the Conversions API event_id, and the Pixel event must match the Conversions API event_name. Events are deduplicated only if they arrive within 48 hours of the first event with that ID. Without event IDs, Meta falls back to fbp and external_id plus the event name, which works only when the browser event arrives first.

Events also need customer information so Meta can match them to an account. Meta scores this as Event Match Quality out of 10 per event. Email, phone and name fields are normalised and hashed, while client_ip_address, client_user_agent, fbp and fbc are sent unhashed. Meta also warns that fbp and fbc values can change, so refresh them rather than caching them.

A 30-minute audit to run in Events Manager this week

A tracking audit for a coach takes about half an hour if you work from the funnel backwards. Do these in order, and write each result down.

1. List the events your funnel should send: Lead at sign-up, Schedule or SubmitApplication at booking, Purchase at checkout. Meta's pixel reference marks value and currency as required on Purchase.
2. In Events Manager, confirm each event arrives from the browser and from the server, and that the pair shows as deduplicated rather than double-counted.
3. Check that event_id and event_name are identical on both sides. A mismatch is the usual cause of doubled counts.
4. Read Event Match Quality per event and add email and phone wherever you legitimately collect them. Hash them as Meta's parameter page specifies.
5. Use the Test Events feature while you change anything, and remove the test_event_code from your live payload afterward. Meta notes that events sent with a test code still flow into Events Manager and are used for targeting and measurement.
6. Record your audience sizes and cost per lead now and compare against your last pre-July report, because the change may already have reached your account. That way any change is measured rather than assumed.

Worked example, not a benchmark: your landing page records 120 sign-ups in a week. The browser Pixel catches 100 of them because some pages load slowly or are blocked. Your server sends all 120 through the Conversions API with the same event_id. Events Manager should report about 120 deduplicated Lead events. If it reports 220, the IDs are not matching. If it reports 100, the server path is not sending.

Is the problem tracking, or too few paying members? See what the Launch Pack and the Scale Program cover →

Running your community on Skool? Here is how we think about tracking around it →

Notice, consent and sensitive data: your side of the data flow

Meta's Business Tools Terms put responsibility for notice and consent on the business that sends the data. They require you to give people clear notice that you share event data with Meta and, where law requires consent for cookies or similar storage, to have it before the tools run. They also prohibit sending health, financial or other sensitive information.

That last rule is where coaches get caught, because coaching often sits close to health and money. An event or parameter named after a person's condition or debt describes that person. Keep event names generic, such as Lead or Schedule, and keep the answers to intake questions out of your parameters. This is not legal advice; confirm the rules for your jurisdictions with a lawyer.

Customer lists: the audience you hand Meta yourself

A customer-file Custom Audience is one you build by uploading hashed identifiers, so it does not depend on what a browser does. Meta requires SHA-256 hashing for everything except external identifiers, accepts email, phone, name, date of birth and location among other fields, and says matching on several identifiers at once raises match rates. Normalise first: lowercase and trim emails, strip symbols from phone numbers and add country codes.

The lists that matter for a coach are leads who have not booked, booked-call no-shows, and buyers or members. A list is a snapshot, so choose a refresh schedule you will keep. Meta also makes you accept its Custom Audience Terms and says the advertiser is responsible for the data it collects and uploads.

Retargeting the people who opted in but never booked? Here is how the warm layer is built →

Our take: tracking is a hygiene job, members are a growth job

This announcement is not a reason to rebuild your ad account. It is a reason to confirm your tracking is sound, because everything Meta does with your signals starts there. If tracking is all you need, your platform's integration or a developer will cost less than we do, and we will say so on a call.

AdvLaunch is the better choice when your problem is members, growth and revenue rather than software: the tracking works, but too few strangers become paying members. It is the wrong choice in two cases. Under about $20K a year of community revenue, the Scale Program is probably premature. And if you need legal advice on consent or a standalone Conversions API build, that is not what we sell. Ad spend is separate and paid from your own Meta Business Manager, and the budget is set with you on the call.

How AdvLaunch Fills a Community on Clean Tracking: The Community Flywheel™

Clean events matter because every step of our system is a measurable event. We call the system The Community Flywheel™, and tracking is how each step gets checked rather than assumed:

1. Hook: a Meta ad sends cold traffic to a paid challenge, webinar or masterclass we control, on a page where the Pixel can fire and a Lead event is recorded, not to your community signup page.
2. Result delivered: over seven days or one live event, your method produces a real outcome before anyone pays, and registration and attendance are events you can see.
3. Community upsell: graduates are offered the paid community at a founder rate, and the purchase event ties the sale back to the ad that started it.
4. Retention compounds: members arrive already bought in, and we measure retention and lifetime value against the campaign cohort instead of a generic benchmark.