Data Manager API can return GOOGLE_ANALYTICS_SUBPROPERTY_OR_ROLLUP_PROPERTY_NOT_ALLOWED when an event targets a Google Analytics subproperty or roll-up property that the operation does not support. WordPress pipelines often store a property ID as an untyped string, so an administrator may choose a familiar reporting property without knowing that ingestion must target the eligible source property. Permissions and property type are separate checks.
Use this for WordPress sites sending events to Google Analytics through Data Manager API, especially organizations with Analytics 360 structures, multiple brands, agency-managed properties, development properties, subproperties, and roll-up reporting.
Quick answer
Preserve the failed event and resolve the configured property ID in Google Analytics Admin or the supported management API. Record whether it is a standard source property, subproperty, or roll-up and which source property owns event collection. Update the destination map to the eligible collection property, verify access separately, test one synthetic event, and replay only the rejected eligible events.
What to check first
- Capture request ID, event ID, destination reference, configured property ID, account ID, stream context, error reason, mapping source, environment, and consent state.
- Resolve the property in its native Google Analytics hierarchy and record type, parent or source relationship, account owner, environment, and expected collection role.
- Inspect WordPress settings, environment variables, deployment templates, CRM mappings, and fallback logic for copied reporting IDs or labels without resource type.
- Test standard source, subproperty, roll-up, nonexistent, wrong-account, and inaccessible property fixtures before changing production mapping.
- Send one synthetic event to the corrected destination and verify API acceptance, DebugView or Realtime evidence where appropriate, event parameters, and absence of duplicate client collection.
Diagnostic table
Use this table to keep the work practical. It connects the symptom to evidence and a verification step.
| Action | Evidence to collect | How to verify |
|---|
| Quarantine rejected events | Capture request ID, event ID, destination reference, configured property ID, account ID, stream context, error reason, mapping source, environment, and consent state. | Every configured Analytics destination stores a resolved resource type. |
| Resolve property type and hierarchy | Resolve the property in its native Google Analytics hierarchy and record type, parent or source relationship, account owner, environment, and expected collection role. | Unsupported property fixtures fail during local validation. |
| Correct the typed destination map | Inspect WordPress settings, environment variables, deployment templates, CRM mappings, and fallback logic for copied reporting IDs or labels without resource type. | The corrected synthetic event appears once in the intended source property. |
| Verify permissions and one synthetic event | Test standard source, subproperty, roll-up, nonexistent, wrong-account, and inaccessible property fixtures before changing production mapping. | Replay preserves event identity, timestamp, parameters, consent, and environment. |
Why this usually happens
- Reporting teams recognize a roll-up property name and select it as if it were a collection endpoint.
- Configuration stores only the numeric property ID without resource type or parent relationship.
- A copied production map can point a development environment at an enterprise reporting property.
- An administrator can have access to view a property while the upload operation still does not support that property type.
- Client-side collection and server upload can both send the corrected event if deduplication is not planned.
Useful command or data shape
Adapt paths, IDs, and privacy handling to the site before running commands or storing data on production.
event_id: purchase-10428
before_destination:
property_id: 912345678
property_type: ROLLUP
error_reason: GOOGLE_ANALYTICS_SUBPROPERTY_OR_ROLLUP_PROPERTY_NOT_ALLOWED
after_destination:
property_id: 845672301
property_type: STANDARD_SOURCE
mapping_version: ga-destination-v5
synthetic_status: accepted
duplicate_check: pass
Safe fix order
Do the work in a sequence that makes each result easy to prove. Stop if a step produces new evidence that changes the incident scope.
- Quarantine rejected events
- Resolve property type and hierarchy
- Correct the typed destination map
- Verify permissions and one synthetic event
- Replay the bounded failed subset
Decision rule
Route collection to the supported source property defined by the Analytics architecture and API contract. Do not repoint to an arbitrary accessible property just to clear the error. Reporting can still use subproperty or roll-up views through their intended configuration.
What to tell the client or owner
Give the site owner the affected version, exact workflow, observed result, business impact, evidence location, temporary control, named owner, and next review time. Remove credentials and personal data from shared screenshots and logs.
Production verification checklist
- Every configured Analytics destination stores a resolved resource type.
- Unsupported property fixtures fail during local validation.
- The corrected synthetic event appears once in the intended source property.
- Replay preserves event identity, timestamp, parameters, consent, and environment.
Mistakes to avoid
- Do not guess property type from its display name.
- Do not confuse viewer permission with destination eligibility.
- Do not send a production purchase as the first test.
- Do not leave client and server collection both active without duplicate analysis.
Questions teams ask during testing
Why can I see the roll-up property but not send to it?
Visibility and upload support are different. A reporting property can be accessible in Analytics while the Data Manager operation requires the eligible source property.
Should dashboards switch to the source property?
Not necessarily. Correct the collection destination first. Reporting architecture can continue to use approved subproperty and roll-up views as designed.
When HandL WP should help
Bring in HandL WP when this affects a production site, paid lead flow, checkout, email delivery, or a managed fleet. We can preserve evidence, isolate the failing layer, make the smallest corrective change, and verify the result across WordPress, the external service, logs, and the user journey.
If this is active on a production site, fix a Google Analytics destination.
Related HandL WP guides
Use these related guides when the same issue touches tracking, security, checkout, or crawler visibility.
Helpful references