> 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-funnel-marker-and-convert-campaign.md). # Activity: Funnel marker and Convert campaign **Funnel marker** and **Convert campaign** measure how players move through a campaign. They do not send anything to the player. * **Funnel marker** marks a step of the flow, so you can count how many players reach it. * **Convert campaign** marks the player as converted: the player reached the goal of the campaign. Use them to see where players drop off, to measure the success rate of a campaign, and to set the goal of an A/B test. Both activities are in the **Flow control** group of the flow builder, in Journeys and in Scheduled Campaigns. ## Settings Both activities have the same settings in the flow builder: | Field | What it does | | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Note** | Optional text for your team. The activity shows it on the canvas. | | **Funnel ID** | The name of the funnel step, for example "Made deposit". When it is set, the step appears in the **Funnel markers** table of the [Campaigns Dashboard](/welcome/products/bi-and-reporting/campaigns-dashboard.md). | | **A/B target** | Off by default. Turn it on to make this step the goal of an A/B test: the A/B test counts the players who reach it. Read more in [A/B Testing](/welcome/products/crm-automation/a-b-testing.md). | **Funnel ID** is not only for these two activities. You can set it on any activity of the flow. **A/B target** is offered only on **Funnel marker** and **Convert campaign**.

Convert campaign: 1 — Funnel ID; 2 — A/B target

## Outgoing connections Funnel marker has one outgoing connection; Convert campaign has none. The picture shows a Funnel marker followed by Convert campaign:
Outgoing connections

Outgoing connections of Funnel marker and Convert campaign in a flow. The numbers match the table below.

| # | Connection | When the player goes this way | | - | ------------------------------ | ------------------------------------------------------------- | | 1 | **Then (after Funnel marker)** | Right away: the step only records that the player reached it. | | — | **Convert campaign** | No outgoing connection: nothing can be attached after it. | ## How it works ### Funnel marker The activity does nothing for the player. It only records that the player reached this point, so the step can be counted in reports. ### Convert campaign * When a player reaches **Convert campaign**, Smartico marks this campaign entry as converted. * A campaign entry is converted only once. If the player reaches a second **Convert campaign** in the same entry, it is not counted again. * **Convert campaign** does not stop the campaign. The player's other open steps keep running, for example a **Wait for event** on another branch. * Do not attach **Convert campaign** and **Stop campaign** to the same branch. Only one of the two may run, so the stop can be lost. To convert and stop the player on the same event, create a conversion rule and a stop rule with that event (see below). Read more about stopping in [Activity: Stop campaign, Stop campaigns and Another Campaign](https://help.smartico.ai/welcome/products/crm-automation/activities-of-flows/activity-stop-campaign-stop-campaigns-and-another-campaign). ### Conversion rules You can also convert players without a step in the flow. Open the campaign, go to the **Stop/Convert rules** tab and click **Create Conversion Rule**. A conversion rule has these settings: | Field | What it does | | --------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Event to wait** | The event that converts the player. Required. | | Conditions | Optional conditions on the event data. | | **Match paired event** | Shown only for paired events, for example a bet and its settlement, when the campaign starts on the first event of the pair. **Yes** converts the player only on the event that belongs to the same bet (or the same position, ticket, and so on). | | **Note**, **Funnel ID**, **A/B target** | The same as in the flow builder. | The rule works for the whole time the player is in the campaign. Rules are not shown on the canvas; you see them in the **Stop/Convert rules** tab. Good to know: * If the rule uses the same event as the campaign's entry event, the event that starts the campaign does not convert the player. Only a later event does. * A campaign entry is still converted only once, whether the conversion comes from a rule or from a **Convert campaign** step. * Players in the control group do not go through the flow, so they never reach a **Convert campaign** step. To compare the control group with the other players, use a conversion rule. * When a conversion rule and a stop rule happen on the same event, the player is converted first and then stopped.

Create Conversion Rule: 1 — Event to wait; 2 — A/B target

## Example A welcome journey sends an email and a push to new players. The goal is the first deposit. 1. Add **Funnel marker** steps with **Funnel ID** "Email sent" and "Push sent" after each message. 2. In the **Stop/Convert rules** tab, create a conversion rule with **Event to wait** = the deposit event. The **Funnel markers** table shows how many players reached each step, and the campaign reports show how many players converted. ## FAQ **Does Convert campaign end the campaign for the player?** No. It marks the entry as converted. Other open steps of the player keep running. If the player must also leave the campaign, create a conversion rule and a stop rule on the same event in the **Stop/Convert rules** tab: the player is converted first and then stopped. **Why is my conversion counted only once?** Each campaign entry is converted only once. A player who enters the campaign again (if the entry mode allows it) can convert again in the new entry. **What is "Tangible prize" in tournament prizes?** It is the same activity as **Funnel marker**. It gives nothing automatically, so you can list a physical prize and hand it out yourself. ## Related * [Activities of Flows](/welcome/products/crm-automation/activities-of-flows.md) * [A/B Testing](/welcome/products/crm-automation/a-b-testing.md) * [Activity: Stop campaign, Stop campaigns and Another Campaign](https://help.smartico.ai/welcome/products/crm-automation/activities-of-flows/activity-stop-campaign-stop-campaigns-and-another-campaign) * [Campaigns Dashboard](/welcome/products/bi-and-reporting/campaigns-dashboard.md) * [Campaigns](/welcome/products/crm-automation/create-journey-flow.md) --- # 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-funnel-marker-and-convert-campaign.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.