> For the complete documentation index, see [llms.txt](https://docs.chord.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chord.co/activate/audiences/chord-retargeting/building-abandonment-audiences-with-ai-chat.md). # Building abandonment audiences with Ask Chord You can ask Ask Chord for a browse, cart, or checkout abandonment audience in plain language, and get sessions, people, and reachability back without building a Chord Analytics explore by hand. It works from Chord's purpose-built abandonment data, which covers closed browsing sessions from the trailing 72 hours, so the numbers reflect a rolling window rather than a fixed report. Ask again a few hours later and expect the counts to move. ## What you can ask Ask in whatever words come naturally. A few examples: * "Who abandoned their cart in the last 72 hours?" * "Build me a checkout abandonment audience." * "What do we have on abandonment audiences right now?" * "What's the Chord Reveal uplift on our cart abandoners?" ## What Ask Chord returns Ask Chord reports three stages side by side, and a session lands in exactly one of them: * **Product abandonment.** Someone browsed and left without adding anything to their cart. * **Cart abandonment.** Someone added an item to their cart but never started checkout. * **Checkout abandonment.** Someone started checkout but never completed it. For each stage, it reports: * Sessions and distinct people. * How many of those people are identified versus anonymous. * How many are reachable by email, counting an email on the customer record even when the session itself carried none. * How many identified people have no email on file at all. * The Chord Reveal uplift: of the people reachable by email, how many are reachable only because Reveal supplied the address, versus how many were reachable without it. This is broken out per stage, not just as one account-wide number. On an account without Reveal, Ask Chord says so and reports the uplift as zero. * How many people bought after abandoning. Ask Chord leaves them out of the audience by default and tells you how many it left out, so a win-back never reaches someone who has already converted. {% hint style="info" %} Example, not a benchmark: one account's 72-hour window turned up 1,430 cart and checkout abandoners, 253 reachable by email, Reveal supplied the address for 82 of those, and 38 people who bought after abandoning were left out. Your numbers will look different. {% endhint %} ## Narrowing and saving the audience Ask Chord can narrow the list on request. You can ask for: * A cart value floor. * A specific product sitting in the cart. * Only people with no purchase at all in the last 90 days. * The people who bought after abandoning added back in, if you want them. * One row per person instead of one row per session. * The list ranked by another customer attribute. Ask Chord returns the member list either way. Where the Audiences feature is turned on for your account, tell it to save the list and give it a name. From there it is a custom audience like any other, and syncing it to your marketing tools works the same way. See [Custom Audiences](/activate/audiences/custom-audiences.md). ## Limits to know * The 72-hour window is fixed and can't be widened. Ask about a longer stretch and Ask Chord answers from your event history instead, where identity only exists for shoppers who were logged in at the time. * Email reachability is usually a small slice of any abandonment audience. Most abandoners are anonymous, so plan for channels beyond email if you want to reach the rest. * Ask Chord reports the numbers and the definitions behind them. It doesn't recommend a campaign, a discount, or a send cadence, that part is still up to you. {% hint style="info" %} Questions about how this applies to your account? Reach out to your Chord team and we'll walk through the details together. {% endhint %} --- # 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.chord.co/activate/audiences/chord-retargeting/building-abandonment-audiences-with-ai-chat.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.