> For the complete documentation index, see [llms.txt](https://user.netmera.com/netmera-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://user.netmera.com/netmera-user-guide/netmera-user-guide-tr/omnichannel-engagement/mobile-push/elements-of-push-notifications.md).

# Push bildirimlerinin öğeleri

Android ve iOS'ta küçük ikon, başlık, mesaj ve medya dahil olmak üzere her push bildirimi öğesi için boyut, format ve teknik özellikleri kontrol edin.

<figure><img src="https://1655476697-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FndrcIiUT8gMUAbOWl72H%2Fimage.png?alt=media&amp;token=a0c06376-c138-4915-be68-f8d572005edf" alt=""><figcaption><p>Push Bildirimlerinin Unsurları</p></figcaption></figure>

<table><thead><tr><th width="117.002197265625" align="center">Gösterim</th><th width="155.01934814453125" align="center">Öğe</th><th align="center">Açıklama</th><th>Teknik Özellikler</th></tr></thead><tbody><tr><td align="center">a</td><td align="center"><strong>Küçük Simge</strong></td><td align="center">Bildirim çubuğunda görüntülenen küçük simge.</td><td><strong>Boyut</strong>: Tüm cihaz boyutlarına uyacak şekilde 24×24 – 96×96 px<br><strong>Format</strong>: PNG<br><strong>Renk</strong>: Şeffaf arka plan üzerinde beyaz</td></tr><tr><td align="center">b</td><td align="center"><strong>Başlık</strong></td><td align="center">Bildirimin ana başlığı.</td><td>50 karakterle sınırlıdır.</td></tr><tr><td align="center">c</td><td align="center"><strong>Gövde</strong> (Bildirim Mesajı)</td><td align="center">Başlığın altında gösterilen içerik metni.</td><td>150 karakterle sınırlıdır.</td></tr><tr><td align="center">d</td><td align="center"><strong>Büyük Görsel</strong> (Android/iOS Medya URL'si)</td><td align="center">Genişletilmiş bildirimlerde görünen büyük görsel.</td><td><strong>Boyut</strong>: 1440×720 px (2:1 en-boy oranı)<br><strong>Formatlar</strong>: PNG, JPG, GIF <em>(animasyonsuz)</em></td></tr><tr><td align="center">e</td><td align="center"><strong>Uygulama Adı</strong></td><td align="center">Bildirimde gösterilen uygulama adı.</td><td><strong>Sabit - değiştirilemez.</strong></td></tr><tr><td align="center">f</td><td align="center"><strong>Zaman Damgası</strong></td><td align="center">Mesajın alındığı zaman.</td><td>Otomatik olarak oluşturulur.</td></tr><tr><td align="center">g</td><td align="center"><strong>Simge</strong> (Android/iOS Küçük Resim)</td><td align="center">Mesajla birlikte gösterilen ana görsel veya logo.</td><td><strong>Boyut</strong>: 192×192 px veya daha büyük<br><strong>Formatlar</strong>: PNG, JPG, GIF <em>(animasyonsuz)</em></td></tr><tr><td align="center">h</td><td align="center"><strong>Eylem Butonları</strong> (Ayarlar> <a data-mention href="/netmera-user-guide/netmera-user-guide-tr/panel-settings/settings/app-configuration/button-sets.md">Buton seti ayarları</a>)</td><td align="center">Kullanıcı etkileşimi için etkileşimli butonlar.</td><td>Destekler <strong>en fazla 3 butonu</strong><br>Şurada yapılandırılabilir <strong>Ayarlar > Buton Setleri</strong></td></tr></tbody></table>


---

# 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://user.netmera.com/netmera-user-guide/netmera-user-guide-tr/omnichannel-engagement/mobile-push/elements-of-push-notifications.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.