> 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/exporting.md).

# Exporting

All Dynamic Content is embedded inside your export. When a viewer opens the playable, their environment is evaluated on their device and the matching layers display.

***

### How Conditions Resolve

**Time**, **Language**, and **Device** are read directly from the viewer's device. These conditions work everywhere, on any partner.

**Location** and **Weather** require a **third-party call**, an external request made when the playable loads. Not all ad partners allow third-party calls, so these two categories only resolve on partners that support them. The export menu indicates which providers support third-party calls.

{% hint style="warning" %}
*If your project uses* ***Location*** *or* ***Weather*** *conditions, confirm your target partner supports third-party calls before building around them, and always configure a* *Fallback* *so viewers see content when the conditions can't resolve.*
{% endhint %}

For a full breakdown of how layers are approved, hidden, or replaced by fallback content when the export loads, see [How Layers Resolve at Runtime](https://help.craftsmanplus.com/play/properties/dynamic-content/fallback.md#how-layers-resolve-at-runtime).

***

### Updating Dynamic Content

Because conditions and assets live inside the creative, changing your dynamic setup requires a **re-export**. If your campaign needs frequent content updates or a large number of variants, consider [Catalogue](https://help.craftsmanplus.com/play/catalogue/quickstart.md) instead, which updates live without re-exporting.


---

# 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/exporting.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.
