> For the complete documentation index, see [llms.txt](https://ledsak.gitbook.io/docs-for-ledsak/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ledsak.gitbook.io/docs-for-ledsak/integrations/meta-ads.md).

# Meta Ads

### Step 1: Generate Meta User Access Token

To begin the integration, you need to provide a **Meta (Facebook) User Access Token** with the appropriate permissions.

#### ✅ Required Token Permissions

Ensure your token includes the following permissions:

* `ads_read`
* `ads_management`
* `business_management`
* `read_insights`

> ℹ️ You can generate the token from the Meta Graph API Explorer or your own Meta App.

***

### Step 2: Connect Meta Ads to Ledsak

#### Fields to Fill in Ledsak:

| Field            | Description                                                                 |
| ---------------- | --------------------------------------------------------------------------- |
| **Access Token** | Paste your Meta User Access Token here. Ensure it’s active and not expired. |

#### Instructions:

1. Log in to your Ledsak dashboard.
2. Navigate to: **Integrations → Meta Ads Reports → Click Connect.**
3. Enter your Meta **Access Token** in the provided field.
4. Click **"Connect"** or **"Save"** to finalize the integration.

***

### Data Synced

Once connected, Ledsak will automatically fetch and display:

* Campaign-level performance metrics
* Ad set & ad-level analytics
* Impressions, Clicks, CTR, CPC, Spend, and more
* Custom date ranges and filters

***

### Token Expiry & Renewal

Meta access tokens often expire after a limited time.

* Ledsak will notify you before expiry.
* You can renew your token manually under the **Meta Ads Integration** section.

***

### Troubleshooting

| Issue           | Solution                                                                |
| --------------- | ----------------------------------------------------------------------- |
| Invalid Token   | Ensure the token is copied correctly and includes required permissions. |
| No Data Appears | Check if the token has access to the right Ad Accounts.                 |
| Expired Token   | Regenerate from Meta Graph API Explorer and update in Ledsak.           |

***

<figure><img src="/files/kslDIW5EsCiBxh27kpoI" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/V1ZjrtSOFmcL9J4M7TDM" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/MERqSQzQ4p5wvYWyQrup" alt=""><figcaption></figcaption></figure>

Need Help?

If you run into issues or need support with Meta Ads integration:

📧 Email: <support@ledsak.ai>\
🌐 Website: <https://ledsak.ai>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://ledsak.gitbook.io/docs-for-ledsak/integrations/meta-ads.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.