> For the complete documentation index, see [llms.txt](https://help.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.impact.com/partner/what-would-you-like-to-learn-about/platform-features/marketing-content/card-linked-offers-clo-explained-for-partners.md). # Card-Linked Offers (CLO) Explained for Partners Card-Linked Offers (CLO) are a type of promotion in which a brand offers some incentive for a consumer to buy their product or service using a linked credit or debit card. ## How are you involved with CLO as a partner? * When you implement CLO with a brand, the brand will pay you for any card-linked sales you drove. You then pay the consumer the cash reward or rewards points promised in the original offer. * Implementing Card-linked Offers (CLO) as a partner allows you to import transaction data for one or more brands. You can utilize the same setup for any number of brands you currently partner with. {% hint style="success" %} **Note:** Check out the [Implementation Guide](https://integrations.impact.com/integration-guides/for-partners/card-linked-offers-beta/integration) for specific instructions on how to get started with CLO as a partner. {% endhint %} ## Benefits of implementing CLO with impact.com * Brands are more likely to be open to experimenting with CLO when they partner with you through our platform impact.com. * Data and reporting transfer are easy with CLO. * Save time by not having to manually send performance reports and invoices to brands. impact.com handles all the reporting, invoicing, and payment processing for them. --- # 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.impact.com/partner/what-would-you-like-to-learn-about/platform-features/marketing-content/card-linked-offers-clo-explained-for-partners.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.