> For the complete documentation index, see [llms.txt](https://docs.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.distro.so/integrations/amplemarket-sequences.md). # Amplemarket sequences Use Amplemarket Start Sequence after qualification and identity checks. ## Configure the sequence Connect [Amplemarket](/integrations/amplemarket.md), choose the sequence and map the prospect email. Optionally map a person's LinkedIn profile and the sequence's dynamic fields. Choose a **Mailbox** if this enrollment should use a specific sending inbox. Leave it empty to use the sequence's configured senders. ## Review exclusion overrides The step offers separate overrides for exclusion lists, recently contacted people and duplicates in other active or draft sequences. Decide each override deliberately. Enabling one can bypass the corresponding provider restriction. Keep the normal restrictions when you do not have a specific reason to change them. ## Verify Check the mapped dynamic fields with a sample before publishing. Make a controlled live enrollment and confirm the sender and sequence in Amplemarket. Inspect the returned status and skip reason. A provider exclusion is different from an authentication or network failure; retrying it blindly does not resolve the underlying decision. A valid LinkedIn URL for this step identifies a person profile, not a company page. See [Unbooked follow-up](/guides/unbooked-follow-up.md) for placing enrollment after a scheduling decision. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.distro.so/integrations/amplemarket-sequences.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 `build a script that syncs our docs to a CMS` 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.