> For the complete documentation index, see [llms.txt](https://docs.anedot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.anedot.com/action-pages/advanced-features/tandem-pages.md). # Tandem Pages A Tandem Page is an Action Page that allows two or more organizations to fundraise together through a single page. A **Tandem Page** is an Action Page that allows two or more organizations to **fundraise together** through a single page. With Anedot, all funds are **direct contributions** *(not conduited)* to each participating organization's account. ## Benefits Of Tandem Pages * **Teamwork** – Perfect for nonprofits, political campaigns, and other organizations working toward a shared cause. Any Anedot customer can collaborate using Tandem Pages to raise funds jointly. * **No extra reporting burden** – Funds are contributed directly to each participating account, just like a standard donation. No conduit PACs or other entities are used. This means Tandem Pages can be used across organization types, provided applicable state or local laws allow it. *(State and local political candidates should confirm with their regulatory body before use.)* * **Higher fundraising totals** – Beta testing showed an average **50% increase** in total funds raised compared to separate pages. For example, if Organizations A and B typically raise $1,000 each, a Tandem Page could raise $1,500 combined. ## Tandem Page FAQ * **Tracking** – Each contribution is processed as a direct donation to the applicable Anedot account. Each account only has access to donor data for the transactions it has received. These transactions can be viewed in the **Transactions** tab of your fundraising account (see [Transactions](/finance/management-and-reporting/transactions.md)) and relayed to connected **integrations**. * **Authority Lines** – Each account must include its own "paid for by" line or legal disclaimer. This is added in **Settings → Finance → Funds** for each Fund. See [Funds](/settings/finance/funds.md). * **Cross-account fundraising** – Tandem Pages can be used across different account types (federal, state, local, etc.), but each account is responsible for compliance with its own laws. We recommend following the most restrictive rules among participating accounts. * Example: If a federal candidate partners with a state candidate, the page should not request or accept corporate contributions to avoid compliance issues. *The Federal Election Commission (FEC) has found that use of a "split-it" style contribution page (similar to Anedot's Tandem Pages) does not necessarily require forming a Joint Fundraising Committee when funds are never pooled and are allocated from the start according to a stated formula (FEC Advisory Opinion 2022-19, Maggie for NH).* *While the FEC has not specifically ruled on Anedot Tandem Pages, Anedot's position is that joint-fundraising rules are not triggered in this setup. This is not legal advice. Please consult legal counsel for guidance.* ## Setting Up a Tandem Page Before you start, ask each partner organization to share its **Account UID** with you. The UID starts with "a" and can be found in the account URL when logged in to that account. If a partner can't find its UID, the Anedot team can provide it. You can connect a partner in either of two ways. Both create the same connection, and the partner appears under **Active Connected Accounts** in **Settings → Access → Connected Accounts** either way. The connection happens right away. No one has to approve it, and neither account gets an email or notification. ### Option 1: Connect From Settings 1. Go to **Settings → Access → Connected Accounts**. 2. Click **+ Connect an Account**. 3. Enter the partner's **Account UID**. 4. Click **Send Request**. Despite the button name, this connects the account right away. See [Connected Accounts](/settings/access/connected-accounts.md) for more on sharing additional Funds. ### Option 2: Connect From the Action Page Builder 1. In the **Action Page Builder**, create a **Donation** or **Event Page**. 2. Go to **Finance → Funds**. 3. Click **+ Add fund**. 4. Select **Connect external fund**. 5. Enter the partner's **External Account ID (UID)**. ### Add the Partner's Fund to Your Page 1. In the **Action Page Builder**, go to **Finance → Funds** on your Donation or Event Page. 2. Click **+ Add fund**. 3. Select the **External Fund** from the dropdown list. *Once a partner is connected, its Fund can be reused for other Action Pages.* ## Related * [Funds](/settings/finance/funds.md) * [Transactions](/finance/management-and-reporting/transactions.md) * [Connected Accounts](/settings/access/connected-accounts.md) * [Page Builder Overview](/action-pages/page-builder.md) * [Advanced Features](/action-pages/advanced-features.md) --- # 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.anedot.com/action-pages/advanced-features/tandem-pages.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.