> 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/company-settings/partner-integrations/applovin.md).

# AppLovin

Connect your AppLovin Axon account to PLAY and upload playables directly.

Connect your AppLovin Axon account to PLAY to upload playable ads directly to Axon from the Export modal, no manual download and re-upload required.

Setup is a one-time process handled on the Partner Integrations page in **Company Settings**. Once your credentials are validated, a **Direct Upload** option becomes available whenever you export for AppLovin.

***

### Finding Your Axon Credentials

CRAFTSMAN+ needs two pieces of information from your AppLovin Axon account: your **Account ID** and your **Campaign Management API Key**. Log in to the [Axon Dashboard](https://ads.axon.ai) to find them.

* **Account ID** - Open the account menu and go to **Settings**. Your Account ID is listed there.
* **Campaign Management API Key** - Open the account menu and go to **Keys**. Copy the Campaign Management API Key.

{% hint style="info" %}
*If you do not see a **Campaign Management API Key** on the Keys page, your account may not have API access enabled. Contact your AppLovin representative to have it provisioned.*
{% endhint %}

***

### Connecting Your AppLovin Account

{% stepper %}
{% step %}

### **In Partner Integrations, find the AppLovin section.**

{% endstep %}

{% step %}

### **Enter your Account ID and API Key from your AppLovin Axon account.**

{% endstep %}

{% step %}

### **Click Validate.**

{% endstep %}
{% endstepper %}

If validation <mark style="color:$success;">**succeeds**</mark>, a green checkmark appears next to each field and a confirmation appears at the bottom of the screen. Your integration is now ready to use!

If validation <mark style="color:$danger;">**fails**</mark>, a red X appears next to each field along with the error message returned by Axon. Update your credentials and click **Validate** to try again.

***

### Direct Upload from the Export Modal

When exporting a project, select **AppLovin** from the partner list in the Export modal. Two options appear beneath it:

* **Download** - Exports the playable as a file to your device. This is selected by default.
* **Direct Upload** - Uploads the playable straight to your AppLovin Axon account. They exported project will show up directly in your Interactives Media Library within Axon.

You can select either option or both.

If your AppLovin credentials have not been set up yet, a **Set Up** button appears next to **Direct Upload**. Clicking it takes you to the **Partner Integrations** page in **Company Settings**, where you can connect your account.


---

# 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/company-settings/partner-integrations/applovin.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.