Meta Pixel Sharing: Permissions and step by step Safety Guide

Pixel sharing can let one business give another Business Manager access to an existing Meta Pixel. When Meta's sharing controls support the setup, the original business generally remains the owner while the partner receives only the permissions that are granted.

This arrangement can suit agencies, brands, developers, and companies that manage advertising in separate businesses. It does not automatically move the pixel or merge the two Business Managers.

What Is Pixel Sharing?

A Meta Pixel is generally used to receive events from a website. App measurement may require a separate Meta SDK or another supported Meta data source.

Website events can include page views, leads, purchases, and registrations. With pixel sharing, the owner business uses Meta Business Settings to grant another business access to the asset.

Depending on the current asset and permission settings, the receiving business may be able to assign the shared pixel to eligible ad accounts or users. Sharing access does not install the pixel, repair event errors, or change the events sent by the website.

• Owner: The business that owns the pixel.

• Partner: Another Business Manager that receives access.

• Users: People in either business who receive asset permissions.

• Ad accounts: Accounts that may be eligible to use the pixel for supported campaign or measurement functions.

Meta can change menu names and layouts. If your screen differs, start in Meta Business Suite or Business Settings, then look for Data Sources, Pixels, or Business Assets.

Pixel Sharing vs. Pixel Ownership

Sharing grants access; ownership controls the asset at the business level. When Meta's sharing feature is used rather than an ownership transfer, the original business generally remains the owner, but confirm the ownership and control details shown in the current account.

Use sharing when a brand wants to retain control while an agency or partner works from a separate Business Manager. Consider an ownership change only after checking business records, contracts, tracking dependencies, and Meta's current rules.

When Should You Share a Meta Pixel?

Pixel sharing can be appropriate when multiple teams need access to the same website event source. For example, a brand may own the pixel while an agency manages campaigns from another Business Manager.

It may also help when a developer needs to check events or when regional teams use separate ad accounts for one website. Each team should receive only the assets and permissions required for its work.

Good reasons to share

• An agency manages campaigns for a brand.

• A contractor needs to test events without owning the business asset.

• Approved ad accounts may need access to the same conversion source.

• A parent company manages tracking for related business units.

Do not share one pixel across unrelated brands merely to simplify reporting. Combining unrelated event data can make reporting and optimization harder to interpret.

What You Need Before Sharing a Pixel

Prepare both businesses before opening the access settings. Common causes of access problems can include selecting the wrong business, lacking the required role, or entering an incorrect Business ID.

• Access to the owner business and the asset-management permissions required by Meta's current setup.

• The correct pixel selected from the owner business.

• The receiving business's Business ID, not a personal profile ID.

• A named contact who can review and manage access in the partner business.

• An ad account in the receiving business if it is intended to run campaigns.

• If campaigns rely on domain-based web measurement, a review of the applicable domain and web-event requirements in Meta's current documentation.

• An agreement on who may view data, change settings, and remove access.

Domain verification is distinct from pixel access. Check Meta's current requirements for the specific web-measurement, event, and campaign configuration you plan to use.

Before sharing, record the pixel ID, current event status, connected domains, assigned ad accounts, and active campaigns. This creates a baseline for later checks.

For implementation details, see the Meta Pixel and Conversions API setup guide. Sharing permissions do not replace website or server-side tracking configuration.

How to Share a Meta Pixel With Another Business Manager

Use the owner Business Manager for this process. Do not send login details or ask a partner to work through your personal profile.

1. Open Business Settings. Select the business that owns the pixel.

2. Find the pixel. Open Data Sources, Pixels, or Business Assets, then identify the correct pixel by name and ID.

3. Open partner or assigned access. Look for Add Partner, Share with a Partner, or Assign Partner. Meta may place this option in the asset's access panel.

4. Enter the partner Business ID. Confirm every digit before continuing. An incorrect ID could send access to the wrong business.

5. Select permissions. Grant the lowest level that supports the agreed work. Use management access only when the partner must manage the data source.

6. Confirm the share. Review the business name, pixel name, and selected permissions before saving.

7. Document the change. Record the date, partner, permissions, owner, and review date in your access log.

Some accounts show asset access under a central Business Assets screen instead of a Pixel screen. If the partner option is missing, check that you selected the owner business and have the permissions required by the current account setup.

The owner generally retains control when the sharing feature is used, but business restrictions, asset status, account structure, and changes in Meta's interface can affect the available controls.

How the Receiving Business Accepts and Uses the Pixel

The partner may see the asset under Business Settings, Partner Assets, or Shared with a Partner. An admin should confirm that the request came from the expected owner business.

After access appears, the receiving business should assign the pixel to the intended users and ad accounts where the current asset model permits those assignments. A shared pixel may not be usable by every person or account automatically.

1. Open the receiving Business Manager.

2. Go to Business Settings and open Partner or Shared Assets.

3. Select the owner business and locate the shared pixel.

4. Assign the pixel to the approved ad account if the control is available.

5. Assign named staff who need to view or manage it.

6. Open Events Manager or Ads Manager and check whether the pixel is available for the intended task.

With compatible permissions and account configurations, the receiving business may be able to use the pixel for some campaign, reporting, and optimization functions. Availability can depend on the pixel, ad account, event configuration, campaign type, data restrictions, and Meta's current controls.

Access may not include the ability to edit every event rule, website integration, domain setting, or Conversions API configuration.

Pixel Permissions: People, Ad Accounts, and Partner Access

Permissions operate at separate levels. Partner access connects two businesses, while user and ad-account assignments affect use inside the receiving business.

Use view access for reporting and review when that level meets the need. Use management access only for trusted users who must change asset settings or manage assignments.

Do not give every agency worker full control. Assign accountable administrators, then use narrower roles for buyers, analysts, developers, and contractors.

If a control is unavailable or an asset is missing, review Meta's technical support and case guide before changing ownership or creating duplicate assets.

How to Confirm the Shared Pixel Is Working

Test access before launching a campaign. The pixel may appear in the partner business without being available to a particular ad account; check the current asset and ad-account assignments.

• Confirm that the pixel ID matches the website and the owner's records.

• Check whether the receiving ad account appears among the pixel's assigned assets.

• Open Events Manager and review recent browser or server events.

• Use a controlled test visit, form submission, or purchase event where appropriate.

• Check event quality, warnings, deduplication, and timestamps.

• Open campaign setup and check whether the pixel is selectable for the chosen event.

• Compare reporting with the owner business after enough new events arrive, while accounting for differences in permissions and attribution settings.

Sharing generally does not create a new data source, but historical-data visibility and reporting may vary by the connected accounts, permissions, attribution settings, and Meta's current reporting behavior. A new share does not recreate old events.

Do not judge tracking from one test alone. Browser limits, consent settings, ad blockers, delayed server events, and campaign attribution can affect what you see.

Common Pixel-Sharing Problems and Fixes

The pixel does not appear

Check the selected Business Manager, pixel ID, partner ID, and user role. Ask an owner administrator to confirm that the asset was shared with the correct business.

The partner cannot assign the pixel

The partner may have business access but lack the permission needed to assign assets. An administrator should review the pixel's assignments to the intended ad account and users.

The ad account cannot select the pixel

Confirm that the account belongs to the receiving business and has an assignment to the shared pixel. Also check whether the campaign objective or event type supports the selected setup.

Events are missing

Sharing does not repair website code, consent tools, browser events, or server events. Check the pixel ID, event names, domain configuration, consent behavior, and Conversions API connection.

The share option is missing

Meta may limit the control because of your role, asset status, business structure, or a product change. Ask the owner administrator to review access, then contact Meta technical support if the control remains unavailable.

How to Remove Shared Pixel Access Safely

Review access in the owner Business Manager when a contract ends, a vendor changes, or a business no longer needs the data.

1. List the partner business, users, ad accounts, and campaigns using the pixel.

2. Pause or move active work only after confirming the business impact.

3. Open the pixel's partner access settings in the owner business.

4. Remove the partner or reduce its permissions.

5. Check direct user access and ad-account assignments as separate steps.

6. Review Events Manager and campaign access after removal.

7. Update your access log and notify the partner in writing.

Revoking access is intended to prevent that partner from using the asset going forward, but confirm the resulting visibility and effects on campaigns, historical data, and records in the current Meta setup.

Pixel-Sharing Security and Privacy Best Practices

Pixel data can relate to customer actions, so treat access as a business and privacy responsibility. Share only with approved partners that have a defined service role.

• Use individual profiles instead of shared logins.

• Turn on two-factor authentication for administrators and agency users.

• Grant the least access needed for each task.

• Keep a record of partner IDs, user roles, and access dates.

• Review access when staff, vendors, or contracts change.

• Follow Meta's terms, privacy rules, consent duties, and applicable data laws.

• Do not export customer data or event information for an unrelated purpose.

• Keep website disclosures and consent controls aligned with your tracking practices.

For agency teams, a periodic access review can identify former contractors and unused ad accounts. You can also review two-factor authentication for agency Business Managers.

When to Create a New Pixel Instead

Create a new pixel when the businesses are unrelated, data must remain separate, or the existing asset's tracking history would make reporting difficult to interpret.

A new pixel may also suit a new website, a separate legal business, a clean measurement plan, or a different consent and data policy. Do not create duplicate assets only because sharing is inconvenient.

Before making that choice, map the website, domains, ad accounts, events, campaigns, audiences, and reporting needs. Also identify who should own each asset after an agency relationship ends.

Final Checklist for Safe Pixel Sharing

• Confirm the correct owner Business Manager and pixel ID.

• Verify that you have the permissions required to change access.

• Check the receiving Business ID carefully.

• Set partner, person, and ad-account permissions separately where supported.

• Confirm the intended ownership and control arrangement.

• Test events and campaign availability after sharing.

• Record the access decision and review date.

• Remove access when the business need ends.

• Review consent, privacy, and data-use duties.

Pixel sharing can give an approved partner the access needed for its role without requiring an ownership transfer, but the result depends on the current Meta asset model, permissions, account configuration, and tracking implementation. Review those settings before sharing and after any major account change.