Meta Conversions API Sub-Code 1353000 ('You do not have permission to send events for this pixel') occurs when the Access Token used in your API call does not have asset permissions for the specified Pixel ID. To fix this, navigate to Meta Business Settings > Users > System Users, click 'Add Assets', select your Pixel or Dataset with 'Full Control' enabled, and generate a new token with ads_management scope.
1. The Business Manager Asset Disconnect
In Meta's enterprise security architecture, an Access Token is not globally authorized across all assets. It is cryptographically restricted strictly to the specific Business Manager assets assigned to the user who generated it.
When agencies or developers set up CAPI, they often generate a token under a personal profile or an unassigned System User. When the server attempts to transmit a conversion event, Meta rejects the call with Sub-Code 1353000: 'Permission Denied'.
- Unassigned Pixel Asset: The system user has an active token, but was never granted access to the specific Pixel ID.
- Dataset vs Pixel Migration: Confusion between legacy Pixel IDs and modern Meta Datasets.
- Cross-Business Mismatches: The pixel belongs to a different Business Manager than the app token.
2. Comparative Analysis: Standard Tracking vs CAPI Control
The table below outlines the architectural and financial differences between passive conversion tracking and active signal governance:
| Error Diagnosis | Root Cause | Action to Resolve |
|---|---|---|
| Sub-Code 1353000 | Pixel asset not assigned to System User | Assign Pixel asset with 'Full Control' in Business Settings |
| OAuthException: Invalid Token | Token expired or revoked | Generate a permanent System User Token set to 'Never' |
| Dataset Permission Error | Token generated on App without Dataset access | Assign System User to Dataset under Data Sources |
3. Step-by-Step Asset Re-linking Procedure
Follow this exact administrative workflow inside Meta Business Settings to grant permanent API permissions:
// Administrative Resolution Workflow:
1. Open https://business.facebook.com/settings/
2. Go to: Data Sources -> Datasets (or Pixels)
3. Select the Pixel receiving Error 1353000
4. Click "Connected Assets" -> Ensure your Ad Account is connected
5. Click "Assign People" (or Assign System User)
6. Select your System User -> Toggle "Manage Dataset (Full Control)" -> Save
7. Go back to: Users -> System Users -> Select User -> "Generate New Token"
8. Select Scopes: [x] ads_management [x] business_management
9. Update your CAPI Control gateway with the newly authorized token stringHow to Deploy CAPI Control to Fix This Today
- Step 1: Log into Meta Business Manager as an organization Administrator.
- Step 2: Verify that your System User has 'Full Control' over the Pixel dataset.
- Step 3: Generate a fresh permanent token and paste it into CAPI Control.
- Step 4: Fire a test event to confirm HTTP 200 OK resolution.
Frequently Asked Questions
Can I use an agency's Business Manager token for a client's pixel?
Only if the client has granted the agency's Business Manager 'Partnership' access with permission to manage the Pixel asset.
What is the difference between a Pixel ID and a Dataset ID in Meta?
In modern Meta architecture, Pixels have been consolidated into Datasets. For CAPI purposes, the Dataset ID is used identically in place of the Pixel ID.
How long does it take for permissions to take effect?
Permission updates propagate across Meta's authorization servers in under 60 seconds.
Ready to steer Meta & Google toward your most profitable traffic?
Drop in CAPI Control in under 2 minutes. Transmit 100% of conversion signals free forever, or activate autonomous signal AI agents to get 3x better ad traffic.