Source: https://docs.amadalis.ai/optimization/live-offers-and-arrangements/ # Live offers and page arrangement Checked against the product’s code on 7 November 2026. Open **Optimization** > **Personalization** > **Targeted content** in the site admin to prepare a live offer, such as a promo banner, or a different section order for an [audience](https://docs.amadalis.ai/reference/glossary/#audience). Start with a published page and an active audience. See [Audiences and targeted content](https://docs.amadalis.ai/optimization/audiences-and-targeted-content/) for creating and activating an audience. A new [targeted item](https://docs.amadalis.ai/reference/glossary/#targeted-content) needs its own name. Its audience starts as returning visitors, so choose the intended audience deliberately. **Holdback %** starts at 10 percent. For an arrangement, held-back visitors keep the default order; setting it to zero removes the comparison needed to measure lift. Live event delivery uses the campaign’s own holdback too. Use a whole number from 0 to 100 in **Holdback %**. Trust that field after editing it; the “10%” hint underneath does not update. ## Reorder sections for an audience Holdback is the group that keeps the default experience for comparison. Lift is the measured difference between that group and the visitors who received the change. 1. Open **Optimization**. 2. Open **Personalization**. 3. Open **Targeted content**. 4. Choose **New targeted content**. 5. Choose **Arrangement**. 6. Enter a name in the top name field, such as `returning-page-order`. 7. In **1 · Who**, choose an active **Audience**. 8. Set **Holdback %**. Read the field value, since the nearby hint does not follow an edited percentage. 9. In **2 · Where**, choose the **Page**. 10. Under **Section order this audience sees**, use the up and down arrows to move at least one section into the desired order. 11. Leave the pin controls off. Pinned arrangements cannot currently be saved from this form. [![Arrangement form: Page Docs Walk First Page, section order Hero, Recommendations, Layout, pins off.](https://docs.amadalis.ai/images/steps/S085-live-offers-arrangement-order-moved.png)](https://docs.amadalis.ai/images/steps/S085-live-offers-arrangement-order-moved.png "Open full-size image") Move the sections into the order the audience should see. 12. If you want to measure a result, choose a **[Goal](https://docs.amadalis.ai/reference/glossary/#goal)** under **Measured on**. 13. Choose **Preview change**. 14. Read the proposed order. 15. Choose **Approve & make it live** or **Keep as draft**. Moving a section is needed to enable the form’s save and preview actions. Pinning alone does not establish an order. The arrangement applies when an eligible visitor loads the page. The site header and footer stay in place. Visitors outside the audience and those held back keep the default page order. [![The page for a visitor in the audience: the cards come before the two-column section.](https://docs.amadalis.ai/images/steps/S085-live-offers-audience-sees-new-order-1440.png)](https://docs.amadalis.ai/images/steps/S085-live-offers-audience-sees-new-order-1440.png "Open full-size image") The audience's order. For the audience in this picture, the recommendation cards appear above the two column section. [![Page at phone width for the selected audience, with the page cards before the columns section.](https://docs.amadalis.ai/images/steps/S085-live-offers-audience-sees-new-order-390.png)](https://docs.amadalis.ai/images/steps/S085-live-offers-audience-sees-new-order-390.png "Open full-size image") On a phone. The audience’s phone view keeps the cards above the layout text and places one card on each row. [![The page for a visitor outside the audience: the two-column section comes first.](https://docs.amadalis.ai/images/steps/S085-live-offers-default-order-1440.png)](https://docs.amadalis.ai/images/steps/S085-live-offers-default-order-1440.png "Open full-size image") Everyone else keeps the default order. [![Page at phone width outside the audience, with the columns section first.](https://docs.amadalis.ai/images/steps/S085-live-offers-default-order-390.png)](https://docs.amadalis.ai/images/steps/S085-live-offers-default-order-390.png "Open full-size image") On a phone. The default phone view keeps the layout’s words and button above the recommendation cards. ## Show a live offer **Expires after (s)** is the intended time until the offer should end after its trigger. It takes a duration in seconds. Read the expiry warning beside that field before relying on it. A Live offer is a dormant overlay until an approved live update reveals it. Delivery needs the site’s live channel, allowed personalization and a visitor in the audience. A visitor outside the audience does not receive the offer. For an offer triggered by joining its audience, the page can get a ticket before the visitor joins. Without that trigger, the visitor must already be in the offer’s audience for its slot to qualify for a ticket. The audience is checked before the offer is sent. For a new page load, the live connection uses an encrypted ticket that page scripts cannot decode to read the visitor id. Consent and Global Privacy Control still decide whether a ticket is issued. A ticket must be used within two minutes to open the connection; that limit does not end a connection already open. 1. Open the intended page in the [Composer](https://docs.amadalis.ai/composer/composer/). 2. Add a **Live offer** section. 3. Give its button a real destination if it uses one. 4. Apply the section change to the draft. 5. Publish the page when that base section is ready. 6. In **Targeted content**, choose **New targeted content**. 7. Choose the **Time-boxed offer** option. 8. Enter its name. 9. Choose the active audience. 10. Check **Holdback %**. Live event updates honor this campaign’s **Holdback %**. A held-back visitor keeps the default instead of receiving this campaign’s live change. 11. Choose the **Page**. 12. Choose the **Section**. An offer needs a section that supports live updates; static sections are unavailable for this choice. 13. In **3 · What**, type a supported text field’s exact name. 14. Enter its approved value. 15. Use **\+ add a field** for another value if needed. Repeat the name and value steps for that field. For a Live offer, `headline` is the heading and `body` is its body text. The form takes typed names and values. Live delivery replaces visible words only. Set the button destination on the base section and publish it; a live text update does not change its address. See the [conversion section reference](https://docs.amadalis.ai/reference/sections/conversion/) for the available fields. 16. Choose the **Trigger** event. 17. Set **Expires after (s)** to at least five seconds. The server is intended to control expiry, and another matching trigger can start a new expiry period. In the supplied demo-store walk, the offer stayed visible after its configured 60 seconds. Confirm expiry on your site before relying on it. For an event trigger with a window, the event must arrive within that many seconds of the session’s start. If the session start cannot be read, that trigger does not send an offer. 18. Choose a measured **Goal** if needed. [![Time-boxed offer: headline and body fields with Docs Walk text; trigger Add to cart within 30 s; expires after 60 s.](https://docs.amadalis.ai/images/steps/S086-live-offers-text-fields-and-trigger.png)](https://docs.amadalis.ai/images/steps/S086-live-offers-text-fields-and-trigger.png "Open full-size image") Type the words, choose the trigger and how long it lasts. 19. Choose **Preview change**. 20. Review the audience, page, section, words and expiry together. 21. Choose **Approve & make it live** only if the change matches your intent and you have accounted for the expiry warning above. [![The exact change: makes Docs Walk Offer live for the audience in Home's live offer, may update in place, reverts after 60 s.](https://docs.amadalis.ai/images/steps/S086-live-offers-exact-change-card.png)](https://docs.amadalis.ai/images/steps/S086-live-offers-exact-change-card.png "Open full-size image") The card before it goes live. The card names the audience and page section that would show the offer; its stated expiry still needs the separate check described below. Check the published page after the configured duration to see whether the offer has ended. The recorded walk left it visible beyond 60 seconds. [![Store Home with the offer box at the bottom right: Docs Walk: a note for this visit, and Go to the bag.](https://docs.amadalis.ai/images/steps/S086-live-offers-offer-arrived-1440.png)](https://docs.amadalis.ai/images/steps/S086-live-offers-offer-arrived-1440.png "Open full-size image") The offer appears on the open page after the trigger. ## Pause or reverse the change The approval receipt offers **Undo**. You can also **Pause** live targeted content and **Resume** it later. Pause an active item before archiving it. [![Stop this targeting? on docs-walk-offer with Approve & apply.](https://docs.amadalis.ai/images/steps/S087-live-offers-stop-card.png)](https://docs.amadalis.ai/images/steps/S087-live-offers-stop-card.png "Open full-size image") Pausing asks first. [![Paused record with Stopped targeted content Docs Walk Offer, Undo and Resume.](https://docs.amadalis.ai/images/steps/S087-live-offers-stopped-receipt-undo.png)](https://docs.amadalis.ai/images/steps/S087-live-offers-stopped-receipt-undo.png "Open full-size image") Paused, with Undo. For an arrangement, read **Performance** for exposed and held-back results. For a live offer, check its trigger window, audience and campaign holdback. A saved draft serves nothing, and targeted content cannot serve on an unpublished page. Check the published page, audience, consent and holdback when an expected result does not appear.