> For the complete documentation index, see [llms.txt](https://docs.adpage.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adpage.io/app-tracking/platform-error-reference.md).

# Platform error reference

What the platforms answer when an app event is wrong, and what each response means.

The responses below come from the `raw_response` of the container's outgoing requests. Add a row whenever you resolve a new one, with the literal response text, because that is what a colleague searches on.

## Meta

| Response                                                              | Meaning                                                                                 | Fix                                                                                                     |
| --------------------------------------------------------------------- | --------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------- |
| 400, code 100, subcode 2804043, "wrong extinfo version or OS version" | Action source is `app` while `app_data.extinfo` is empty, or position 0 or 4 is missing | Update the tag template and switch on automap for app data, or map `extinfo` by hand. See the Meta page |

## TikTok

**Open:** fill in from practice.

## GA4

GA4 answers a valid request with a 204 and no body, so a 204 here says the request was accepted, not that the event is correct. Verify content in Realtime or DebugView.

## Symptoms without an error

Not every problem produces a response. These are the silent ones.

| Symptom                                                   | Cause                                                             | Fix                                                         |
| --------------------------------------------------------- | ----------------------------------------------------------------- | ----------------------------------------------------------- |
| Nothing at all in the outgoing requests                   | The sGTM URL is off in GA4, or on only one of the two app streams | Enable it on both streams                                   |
| App events missing while web traffic runs fine            | No GA4 App client in the container                                | Add the App client                                          |
| The event is in the outgoing requests but not in GA4      | The GA4 tag is triggered on the web client only                   | Add a trigger on the App client                             |
| A platform receives app events as web events              | An event-name trigger without a `Client Name` condition           | Add the condition and give the app its own tag              |
| A platform accepts everything but reports no attribution  | The event carries only an IP address                              | Send an identifier, see the identifiers page                |
| The client sees nothing in preview while events do arrive | Preview is running on the web container                           | Check the container id, and verify in the outgoing requests |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.adpage.io/app-tracking/platform-error-reference.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.