> 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/action-page-basics/submissions.md). # Submissions Review every supporter response on an Action Page, including failed payments. Use Transactions for detailed financial data. A **Submission** is recorded each time a supporter responds to an Action Page, including both completed entries and failed payment attempts. If a payment fails, ask the donor to contact their bank. * **All Submissions:** Go to **Action Pages -> Submissions** to review every submission in your fundraising account. * **Page-Specific Submissions:** Go to **Action Pages -> Pages**, hover over the desired page, open the **⋮** menu on the page row, then select **View submissions**. *For a more detailed breakdown of financial data, use the **Finance ->*** ***Transactions*** *tab instead of Submissions.* ## Filter Submissions To filter Submissions, use the **Search Bar** to look up donor records. The following data points can be used for filtering in the Search Bar: * *Name* * *Email* * *Submission ID* * *Page Slug (end of the page URL)* * *Page Name* * *Page Type (Donation, Event, Lead)* To filter by the **Page ID**, click the Filter icon in the upper right corner. Next, enter the **Page ID** and click **Apply Filters**. ## Export Submissions To view all Submission data in an Excel or Numbers spreadsheet, click the **Export CSV** button. Next, click the **Downloads** icon located in the upper right corner of the account menu to open the CSV file. The following data is available within the **Submissions Export**: | Column Headers | Definition | | -------------------------------- | ------------------------------------------------------------------------------------------------------------------ | | Action Page ID | Action Page ID | | Action Page Name | Action Page Name | | ID | Submission ID | | First Name | First Name | | Middle Name | Middle Name | | Last Name | Last Name | | Title | Title (aka: prefix, salutation) | | Suffix | Suffix | | Email | Email | | Phone | Phone number | | Address Line 1 | Address Line 1 | | Address Line 2 | Address Line 2 | | City | City | | State | Region/State | | Zip | Postal code/Zip code | | Country | Country | | Source Code\* | Source code | | IP Address | IP address for the submission | | Referrer | Action Page URL for the submission | | Referrer To Form | The page that referred the Action Page | | Communications Consent Email | Communication consent given for email (True = Yes, False = No) | | Communications Consent Phone | Communication consent given for phone (True = Yes, False = No) | | Currently Employed | Currently employed (True = Yes, False = No) | | Employer Name | Employer name | | Occupation | Occupation (job title) | | Organization | Organization name (for donations submitted as a business or PAC) | | Created At | Submission created at timestamp | | Donation ID | Corresponding donation's UID | | Anedot Fees | Corresponding donation's Anedot processing fees | | Vendor Markup | Corresponding donation's Vendor fees (sum of all vendor markup fees) | | Net Amount | Corresponding donation's net amount | | Gross Amount | Corresponding donation's gross amount | | Product Code | Corresponding GOAA product's internal SKU | | Product ID | Corresponding GOAA product's ID | | Product Name | Corresponding GOAA product's name | | Product Value | Corresponding GOAA product's value | | Fund Internal ID | Corresponding donation's Fund Internal ID (configured in Settings -> Finance -> Funds) | | Fund Name | Corresponding donation's Fund Name (configured in Settings -> Finance -> Funds) | | custom\_field\_response\_headers | Custom field responses (header is the field's internal name; cell value is the field response for that submission) | | Utm Campaign | UTM campaign | | Utm Content | UTM content | | Utm Medium | UTM medium | | Utm Source | UTM source | | Utm Term | UTM term | | Pledge? | Is the submission a future pledge? (True = Yes, False = No) | | Pledge Capture Date | Future pledge capture date (shown in account time zone) | | Donor Covered Fees | Did the donor cover fees? (True = Yes, False = No) | | Donor Covered Fees Amount | Fee covered by donor | ## Related * Donor Covers Fees * New Jersey Public Financing Page Setup * Share an Action Page * Manage Events * Goals --- # 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/action-page-basics/submissions.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.