> For the complete documentation index, see [llms.txt](https://help.craftsmanplus.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.craftsmanplus.com/play/properties/dynamic-content/fallback.md).

# Fallback

A **Fallback** layer is a safety net. It displays when no other dynamic layer matches the viewer for that condition category, so your creative never renders with missing content.

***

### Setting a Fallback

**Fallback** appears as an option at the bottom of every condition category in the Dynamic Content popup. It can be used two ways:

* **Fallback only** - check Fallback with no other options. The layer exists purely as the backup and only displays when nothing else matches.
* **Fallback alongside conditions** - check Fallback in addition to specific options. The layer displays normally when its conditions match, and also acts as the backup when nothing matches. For example, a layer set to Android + Fallback displays for Android viewers, and displays for everyone else too if no other Device layer matches them.

***

### How Layers Resolve at Runtime

When a playable loads, each condition category (Time, Device, Language, Location, Weather) is resolved on its own. Within a category, every layer that uses it is sorted into one of three lists:

| List           | What lands here                                                          |
| -------------- | ------------------------------------------------------------------------ |
| **Approved**   | Layers that match the viewer in this category                            |
| **Fallback**   | Layers that don't match in this category, but have **Fallback** checked  |
| **Unapproved** | Layers that don't match in this category and don't have Fallback checked |

Then, for that category:

1. If **any** Approved layer actually displays, the category's Fallback layers stay hidden. An Approved layer that is hidden by another category doesn't count.
2. If **no** Approved layer displays, the category's Fallback layers display instead.
3. If neither list has layers, no layers using this category display.

A layer displays only when it passes every category it uses, either as Approved or as a Fallback that was allowed to display.

{% hint style="info" %}
*A match in one category never hides another category's fallback. A layer Approved for Device doesn't hide a Weather fallback.*
{% endhint %}

{% hint style="info" %}
*If two layers would each hide the other's fallback, both display, so the viewer is never left with nothing. Every other layer still follows the rules above.*
{% endhint %}

{% hint style="info" %}
*Unlike* *Catalogue, where fallback is automatic, Dynamic Content fallback must be* ***manually configured**. Without one, outcome 3 is possible and a non-matching viewer sees nothing.*
{% endhint %}

***

### Examples

For a viewer on an **Android Desktop** device:

| Layer setup                 | Result                                              |
| --------------------------- | --------------------------------------------------- |
| Layer 1 = Android + Desktop | **Approved** - displays                             |
| Layer 2 = Android + TV      | Unapproved - hidden                                 |
| Layer 3 = Android + Mobile  | Unapproved - hidden                                 |
| Layer 4 = Fallback          | Fallback - hidden, because an Approved layer exists |

Same viewer, but no layer targets Desktop:

| Layer setup                | Result                                                |
| -------------------------- | ----------------------------------------------------- |
| Layer 1 = Android + Tablet | Unapproved - hidden                                   |
| Layer 2 = Android + TV     | Unapproved - hidden                                   |
| Layer 3 = Android + Mobile | Unapproved - hidden                                   |
| Layer 4 = Fallback         | **Fallback** - displays, because nothing was Approved |

Same setup without Layer 4, and no dynamic layers display at all. A viewer on a Tuesday should still see something even if you only built Monday content, so always include a Fallback.

When layers combine two categories, a layer that matches one category but fails the other doesn't hide the fallback. For a viewer in **New York** on a **sunny** day:

| Layer setup                                    | Result                                                                                          |
| ---------------------------------------------- | ----------------------------------------------------------------------------------------------- |
| Layer 1 = New York + Rain                      | Unapproved - hidden, because it isn't raining                                                   |
| Layer 2 = Location Fallback + Weather Fallback | **Fallback** - displays. Layer 1 matches the location but fails on weather, so it doesn't count |

On a rainy day in New York, Layer 1 is Approved in both categories and displays, and Layer 2 stays hidden.


---

# 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://help.craftsmanplus.com/play/properties/dynamic-content/fallback.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.
