> For the complete documentation index, see [llms.txt](https://help.smartico.ai/welcome/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.smartico.ai/welcome/products/crm-automation/activities-of-flows/activity-meta-ads-audience.md).

# Activity: Meta Ads audience

The **Meta Ads audience** activity adds players to your Meta (Facebook and Instagram) custom audiences, or removes them, as they go through a campaign flow. Use it to retarget players in your Meta ads: for example, add every player who made a first deposit to an audience you advertise to, or remove the players who came back.

{% hint style="info" %}
**Note:** The activity appears in the flow builder only when Smartico has turned it on for your label. Contact your Customer Success Manager to turn it on.
{% endhint %}

## Before you start: set up Meta

You need these in Meta Business Manager:

* **An ad account.** Smartico works with the custom audiences of one ad account per label.
* **The Custom Audience Terms accepted** for that ad account. Meta refuses customer lists until they are accepted.
* **One or more customer list audiences** in that ad account (in Ads Manager: **Audiences** → **Create audience** → **Custom audience** → **Customer list**). The activity lists only customer list audiences.
* **An access token** of a system user that has access to the ad account, with the `ads_management` permission. Choose a token that does not expire: when the token expires or is revoked, players go to the **Not sent (Meta error)** branch.

## Set up the activity on your label

Open **Label settings** → **Marketing automation** → **Custom activities**. The **Meta Ads audience** row shows the current values and the status: **Configured**, or **Not configured** with the settings that are still missing. Click **Configure** and fill in:

* **Meta ad account ID** — the ID of your ad account.
* **Meta access token** — the token of the system user. After you save, the token is shown as **hidden**.

<div data-with-frame="true"><figure><img src="https://77049817-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfS5hl0PiysHtKAKMsQTe%2Fuploads%2FrLEMubwqXOs3xn1i9quR%2Fmeta-ads-audience-label-settings-04995c6a-a8af8c.png?alt=media" alt="Custom activities in Label settings" width="640"><figcaption><p>The Meta Ads audience activity in Label settings: its status and the label's values. Configure opens them for editing.</p></figcaption></figure></div>

Until both are set, a Meta Ads audience step in a flow shows the warning **Not set on this label** and every player who reaches it goes to the **Failed** branch. If you can edit label settings, the **Set up** button under the warning opens the same settings.

## Add the activity to a flow

Drag **Meta Ads audience** from the **Actions** group of the palette onto the canvas, then choose:

* **Audiences** — one or more of your customer list audiences, at most 20. The list is loaded from your ad account.
* **Action** — **Add users** or **Remove users**.
* **Player value** — optional: the player property Meta gets as the customer value (see [Player value](#player-value-for-value-based-audiences)).

<div data-with-frame="true"><figure><img src="https://77049817-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfS5hl0PiysHtKAKMsQTe%2Fuploads%2FhWREQMp4JovHgkP5HZGc%2Fmeta-ads-audience-node-form-41d9ba16-da50dc.png?alt=media" alt="The Meta Ads audience step" width="640"><figcaption><p>The settings of a Meta Ads audience step: the audiences and the action</p></figcaption></figure></div>

The activity works in campaign flows only. It is not available in automation rules or missions.

## What Smartico sends to Meta

For each player, Smartico sends:

* the email address and the phone number, normalized and hashed with SHA-256 before they leave Smartico. Meta never gets them in plain text;
* the player's Smartico user ID, as the external ID;
* with **Add users** and a **Player value**, the value of that property, to value-based audiences only.

Meta matches the hashes with its own users. A phone number is matched only when it is stored with the country code. A player with neither an email address nor a phone number goes to the **Failed** branch.

## Player value for value-based audiences

A value-based audience is a customer list created in Meta with a customer value column. Meta builds a value-based lookalike from it: people similar to your most valuable players, not to all of them. In the **Audiences** list of the step these audiences are marked **(value-based)**.

To fill one, choose a **Player value**: **Accounting: Total NGR**, **Accounting: Last 180 days NGR**, **Accounting: Total Deposit Amount** or **Accounting: Total GGR**. Smartico sends the player's value of that property as it is. A negative or empty value is sent as 0.

* A value-based audience needs a **Player value**. Without it, Meta refuses the players and they go to **Not sent (Meta error)**.
* An ordinary audience gets the players without the value, so one step can fill both kinds.
* **Remove users** never sends a value: Meta removes players from both kinds of audience without it.

{% hint style="info" %}
**Note:** Meta restricts audiences that suggest the financial status of people. Give a value-based audience a neutral name and audience label (for example **General customers**, not **High value**).
{% endhint %}

## Timing

Smartico sends players to Meta in batches, one batch per audience. A batch closes 15 minutes after its first player (or at 10,000 players) and goes out within the next 15 minutes, so a player reaches Meta within 30 minutes after the step. Meta then updates the audience on its side, which can take up to 24 hours. Meta shows the size of an audience only approximately, so a few added players may not change the number you see in Ads Manager.

If Meta does not answer or limits the requests, Smartico tries the batch again every hour, up to 13 attempts in all. If Meta refuses the batch (an expired token, the terms not accepted, a deleted audience, a value-based audience without a **Player value**), Smartico does not try again.

## Outgoing connections

<div data-with-frame="true"><figure><img src="https://77049817-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfS5hl0PiysHtKAKMsQTe%2Fuploads%2F3a5CEPkMiGPnTvOsp9Wd%2Fmeta-ads-audience-branches-eb78bf3b-6ab399.png?alt=media" alt="Outgoing connections" width="560"><figcaption><p>A Meta Ads audience step with its Failed, Sent to Meta and Not sent (Meta error) branches</p></figcaption></figure></div>

| # | Connection                | When the player goes this way                                                                                                                                                                                                 |
| - | ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| 1 | **Then**                  | Right away, when Smartico starts the step. It does not wait for Meta.                                                                                                                                                         |
| 2 | **Failed**                | The step could not run for the player: the player has neither an email address nor a phone number, or the activity's settings on your label are missing or wrong.                                                             |
| 3 | **Sent to Meta**          | Meta accepted the batch with the player, within 30 minutes after the step.                                                                                                                                                    |
| 4 | **Not sent (Meta error)** | Meta refused the batch with the player, for example because the token has expired or a value-based audience got no **Player value**, or the batch could not be sent after all attempts (up to about 16 hours after the step). |

{% hint style="warning" %}
**Sent to Meta** and **Not sent (Meta error)** fire only while the player is still in the campaign. Set the campaign **Duration** long enough for them: at least 1 hour for **Sent to Meta**, and at least 1 day if you use **Not sent (Meta error)**. A player whose campaign has ended (its **Duration** has passed, or a **Stop campaign** step ended it) does not take these branches.
{% endhint %}

### Frequently Asked Questions

**Q: Does Sent to Meta mean that Meta found the player?**

A: No. It means Meta accepted the batch. Meta does not tell which players it matched; it updates the audience on its side.

**Q: The step has several audiences. How many times does the player take a branch?**

A: At most once per branch. If the batches of all the audiences are sent, the player takes **Sent to Meta** once. If one audience fails and another is sent, the player takes both **Sent to Meta** and **Not sent (Meta error)**, once each.

**Q: What happens if I add a player who is already in the audience, or remove one who is not in it?**

A: Nothing. Meta keeps the audience as it is, and the player takes **Sent to Meta** as usual.

**Q: Can I use lookalike or website audiences?**

A: No. The activity lists only customer list audiences. You can build a lookalike audience in Meta from a customer list audience that Smartico fills, and a value-based lookalike from a value-based one.


---

# 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.smartico.ai/welcome/products/crm-automation/activities-of-flows/activity-meta-ads-audience.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.
