> 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/export/3rd-party-calls.md). # 3rd Party Calls A third-party call is any request your playable makes to the open internet while it runs — loading external content, fetching live data, or pinging a tracking URL. Because playables ship as self-contained files, most features never touch the network. A handful do, and not every ad network allows it. ### What Counts as a Third-Party Call PLAY flags your project as requiring third-party calls when it uses any of the following: * **Fire Tracker actions** — firing a custom [tracker URL](/play/general/actions/fire-tracker.md) at runtime. * **iFrame components** — an [iFrame](/play/layers/components/iframe.md) with its format set to URL, which loads an external page. * **Location and Weather conditions** — [dynamic content](/play/properties/dynamic-content.md) that resolves the viewer's location or local weather requires a live lookup. * **Linked Catalogues** — [Catalogue](/play/catalogue/what-is-catalogue.md) dynamic content fetches product data at runtime. ### Why Some Partners Restrict Them Many ad networks run playables in a sandbox that blocks outbound network requests, for privacy, security, and reliability reasons. On those networks, a playable that depends on unrestricted internet access can break silently — or the ad can be rejected outright during review. ### How PLAY Flags Them You'll see warnings at two points: * **In the editor** — when you configure any of the features above, a **Third-Party Calls Required** notice appears in the relevant properties popup, reminding you that the feature relies on unrestricted internet access which not all partners support. * **At export** — in the [Export dialog](/play/export/export-partners.md), partners that support third-party calls display a dedicated icon on their row (hover it to confirm). If your project requires third-party calls and you select a partner that doesn't allow them, that partner's name highlights in yellow and a warning appears above the Export button explaining the project could be rejected. The warning doesn't block exporting — you decide whether to proceed, swap the feature out, or target a partner that supports third-party calls. --- # 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/export/3rd-party-calls.md?ask=&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.