> For the complete documentation index, see [llms.txt](https://docs.marketingtool.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.marketingtool.pro/ad-set-storyline.md).

# Ad Set Storyline

Track every change made to your Facebook ad sets and see exactly how each modification impacts performance. Monitor team actions, automation triggers, and KPI shifts with color-coded analytics.

**Category:** [Facebook & Meta Ads](/facebook-and-meta-ads.md) · **Badge:** Facebook/Meta

## Where to find it

* **Web app** — [app.marketingtool.pro/tools/ad-set-storyline](https://app.marketingtool.pro/tools/ad-set-storyline)
* **iOS / Android app** — open the **Tools** tab and search “Ad Set Storyline”

## Inputs

| Input                     | Type                                                           | Required |
| ------------------------- | -------------------------------------------------------------- | -------- |
| Ad Set ID or Campaign URL | textarea                                                       | ✅        |
| Account Type              | select — E-commerce, Lead Generation, App Installs             | optional |
| Analysis Timeframe        | select — Last 7 days, Last 14 days, Last 30 days, Last 60 days | optional |

## Tips for best results

* **Monitor team changes** — See which team members made changes, when they occurred, and how they affected performance.
* **Audit automations** — Review all actions triggered by automation rules to identify which ones need adjustment.
* **Use color coding** — Green highlights strong metrics, red flags underperforming figures for rapid issue identification.

## How to run it

1. Open **Ad Set Storyline** (links above).
2. Fill in the inputs and press **Generate**.
3. Review your full result page — it's saved to your History automatically. On desktop, use **Download All** to save every asset.


---

# 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://docs.marketingtool.pro/ad-set-storyline.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.