> ## Documentation Index > Fetch the complete documentation index at: https://help.lobyco.com/llms.txt > Use this file to discover all available pages before exploring further. # Recipients > Who gets a push, email, banner, feed or prompt, and how connecting it on the canvas changes that. This page explains who gets a push, email, banner, feed or prompt. You either pick the customers in the communication's own **Segmentation** panel, or you connect the communication on the campaign's canvas and let the flow decide. The second way changes who gets it and when, so it's worth knowing which one you're using. | Term | What it is | | - | - | | **Segmentation** | The part of every communication's form that says who gets it. | | **All customers** | Everyone in your app. Email doesn't offer it. | | **Audience** | A saved group of customers that you pick from a list. See [Segments and Audiences](/business-documentation/audiences-and-data). | | **Triggered** | The communication's block is connected after another block on the canvas. The flow decides who gets it, each time it reaches the block. | | **Validity period** | How many days a triggered banner, feed or prompt stays visible to each customer. | ## Pick who gets it Open the communication in its campaign and find its **Segmentation** panel. Email has a **Segmentation** tab instead. The choices depend on the communication. | Communication | You can pick | Also in the panel | | - | - | - | | [Push](/business-documentation/communication/push) | **All customers** or **Audience** | A note that messages only go to the customer's subscribed devices | | [Email](/business-documentation/communication/email) | **Audience**. **All members** is shown, but you can't select it. | A reminder to use an audience that only holds customers who gave consent | | [Banner](/business-documentation/communication/banner) | **All customers** or **Audience** | **By stores**, to show it only for the stores you pick | | [Feed](/business-documentation/communication/feeds) | **All customers** or **Audience**, under **By customers** | **By stores**, to show it only for the stores you pick | | [Prompt](/business-documentation/communication/prompt) | **All** or **Audience** | Nothing else | With **Audience**, you can pick one or more audiences. A push or email sent this way goes out once. A push goes at its **Delivery date** and an email at its **Start date**. A banner, feed or prompt is shown from its start date to its end date. [Lifecycle](/business-documentation/communication/lifecycle) explains what happens at each step. Some older pushes, feeds and prompts show a customer file in their **Segmentation** panel. You can't change it, and you can't add a file to a new one. ## Trigger it from the canvas Connect a communication's block after another block on the [orchestration canvas](/business-documentation/campaigns/orchestration-canvas). The flow then decides who gets it. Each time the flow reaches the block, the customers it carries get the push, email, banner, feed or prompt. | What comes before the communication | Who gets it, and when | | - | - | | A **Member segment** or **Seed**, on its own or through blocks such as **Enrich** | The customers in the result, each time the flow runs on its schedule | | **Customer event** | One customer, each time a customer signs up | | **Activity event** | One customer, each time they complete a challenge, win or lose a game, or get a coupon | | **Inbound API** | One customer, each time an external system calls in about them | | **Delay** | The customers the Delay was holding, once their wait is over | Email can't follow a trigger block directly. [What can connect to what](/business-documentation/campaigns/orchestration-canvas/block-reference#what-can-connect-to-what) has the full rules for every block. You can only connect or disconnect a communication's block while the communication is a draft. See [Connect the blocks](/business-documentation/campaigns/orchestration-canvas#connect-the-blocks). ### What changes in the form Once the block is connected, its **Segmentation** switches to a fixed choice. You can't change it while the block stays connected. | Communication | Segmentation shows | | - | - | | Push | **Custom** | | Email | **Triggered** | | Banner and feed | **Custom segment** | | Prompt | **Customer** | A push keeps **Custom** even after you disconnect its block, so you can't change it back. To send it to a group instead, use **Duplicate as draft**. The copy starts with **All customers**. A banner, feed or prompt also gets an **Add triggered details** panel. Its one field is **Validity period of banner**, **Validity period of feed** or **Validity period of prompt**. It sets how many days each customer sees it, counted from when the flow reached them. If you leave it empty, customers see it until the end date. It can't be longer than the time between the start and end dates. ![The Create Feed dialog opened from a Feed block that's connected after a Member segment block on the canvas, scrolled to Segmentation. By stores is greyed out. Under By customers, All customers and Audience are greyed out, and Custom segment is selected and greyed out, so the choice can't be changed. Below it, the Add triggered details panel has a Validity period of feed field, with a hint that the activity stays valid until its end if you leave it empty. Schedule shows the start and end dates from the campaign.](https://mintcdn.com/lobyco-4c9fb3ad/rG971_5ZfS49bcjM/images/communication-01-triggered-feed-segmentation.png?fit=max\&auto=format\&n=rG971_5ZfS49bcjM\&q=85\&s=c5e10e3b7655b231b892e8d7a2ff9547) *A connected feed's segmentation, locked on Custom segment* ### When a triggered communication acts > [!WARNING] > > Publish a triggered communication before the flow reaches it. A triggered communication only acts while it's published and between its start and end dates. If the flow reaches it while it's a draft, still scheduled or already expired, the run skips it. Those customers don't get it, and nothing sends it to them later. | Communication | Each time the flow reaches it | | - | - | | Push | It's sent to each customer's subscribed devices. A customer who reaches it again gets it again. | | Email | It's sent to each customer. A customer who reaches it again gets it again. | | Banner and feed | Each customer sees it for the validity period. A customer who reaches it again doesn't get a second copy. Their validity period starts again instead. | | Prompt | Each customer sees it for the validity period. A customer who reaches it again sees it again, even if they already answered it. | ## Personalise a triggered communication A triggered push, email, feed or prompt can use details the flow passes on, such as a customer's name. Each communication's page shows where to add them. A banner is an image, so it has nothing to personalise. What you can use depends on what comes before the communication. * After a segment, add an **Enrich** block to attach customer attributes. * After a trigger, you can only use the details the event carries. **Enrich** can't follow a trigger. If you change what comes before the communication, a detail you used may no longer be there. The communication's block on the canvas then shows a warning. For example, a flow that runs every day can show each customer a feed with their own details. ```mermaid theme={"system"} flowchart LR A[Member segment] --> B["Enrich: adds customer details"] B --> C[Feed] ``` The feed shows each customer's details as they were when the flow reached them. ## Older Dynamic Feed blocks A canvas built earlier can have a **Dynamic Feed** block. It works differently from **Feed**. Each time the flow runs, it creates a new feed for the customers in that run. Its **Publish on execute** switch decides whether the new feed is published or saved as a draft. You can't add a **Dynamic Feed** from the **Block library** any more. To send a personalised feed today, connect a **Feed** block as described above. ## Related * [Lifecycle](/business-documentation/communication/lifecycle) — what each communication does as it moves from draft to expired, and what you can still change. * [Orchestration canvas](/business-documentation/campaigns/orchestration-canvas) — building a flow and connecting a communication's block to it. * [Block reference](/business-documentation/campaigns/orchestration-canvas/block-reference) — every block you can connect before a communication, and what each one passes on. * [Segments and Audiences](/business-documentation/audiences-and-data) — building the audiences you pick in a communication's **Segmentation**. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.