---
title: Embed a form on your site
description: Put a form on a page you own, rendered by Athena in a frame or as JSON your own interface draws.
sidebar:
  badge: Starter+
---

A published form can live on a site you own instead of behind a shared link. Each placement is its own **embed**: it has its own address, its own list of sites it may load on, and its own record in your responses, so you can tell where a response came from and shut one placement off without disturbing the others.

Embeds have their own page, reached by **Embeds** at the top of the form editor. It lists every placement with its type, the sites it may load on, how many responses it has collected, and whether it's enabled; clicking one opens it in full. Forms and embeds are included on Starter and above.

## Pick a type

Every embed is one of two types, chosen when you create it and fixed from then on; each type answers on its own address, so switching would break every snippet already pasted. To move a placement from one to the other, create a second embed and swap the snippet over.

| Type | What you get |
|---|---|
| **Visual embed** | An `<iframe>` snippet. Athena renders the form (questions, validation, captcha, and the thank-you state) and the frame sizes itself to its content. |
| **JSON embed** | One address that accepts a response. Your site draws the interface and does the submitting; Athena gives you a worked example carrying your form's question ids. |

Choose the visual embed if you want the form working on a page today, or if abuse is a concern; it's the one that carries a captcha. Choose the JSON embed if the form has to match a design system you control, and you have someone to build the interface, keep it in step with the form, and defend it from automated submissions.

## Create an embed

1. Open the form, click **Embeds**, then **New embed**.
2. Give it a **Placement name**: *Pricing page*, *Partner portal*. This is what the responses table shows as the source, so name the place, not the form.
3. Pick the **Type**.
4. List the **Sites it may load on**. Enter the scheme and host, like `https://example.com`, with a port if your site uses one. Don't include a path. The embed refuses to load or submit anywhere else.
5. Optionally add **Recorded values** and **Values the page may pass in**; see below.
6. Leave **Require captcha** on unless you have a reason not to. On a JSON embed it is off and unavailable; see below.
7. Click **Create embed**.

The new placement appears in the list. Click it and the panel that opens carries the snippet to copy. For a visual embed that's an `<iframe>` plus a small listener that keeps its height in step with the content; paste both into your page. For a JSON embed it's a worked `fetch` example carrying your form's actual question ids.

:::warning[A JSON embed has no captcha]
Athena's captcha runs on an Athena page, and a JSON embed doesn't have one; the switch is off and disabled for that type. Whatever stands between your page and automated submissions is yours to add.

If the form is publicly reachable and you don't have that covered, use the visual embed instead.
:::

:::note[Publish before you paste]
While the form is a draft, nothing is served: a visual embed reads *"This form is unavailable"* and a JSON embed answers **not found**. The Embeds page says so directly. Publishing doesn't change any embed address, so you can paste the snippet first and publish afterwards.
:::

## Attach values to responses

Two different things can be attached to each response, and the difference matters.

**Recorded values** are set by you on the embed and saved with every response from that placement, exactly as you set them. Respondents never see them and cannot change them. Use these for anything you intend to rely on: which campaign a placement belongs to, which partner a page serves.

**Values the page may pass in** are named here and supplied at page load by the site hosting the embed. For a visual embed, the page appends them to the frame address; for a JSON embed, it sends them with the response.

:::warning[Passed-in values come from the page, not from Athena]
Anything the page passes in is visible in that page and can be edited by anyone viewing it before they submit. Treat these as analytics and nothing more, never as proof of who someone is, what they're entitled to, or what they should be charged.

If you need a split you can trust, give each page its own embed. The placement name is recorded by Athena and can't be forged.
:::

The placement name appears as a **Source** column in the responses table, once a form has at least one embed. The values themselves appear when you open a single response, and as one column each in the CSV export.

## What a respondent sees

A visual embed renders the same questions, validation, and required-field rules as the shared link, without the surrounding page furniture. It grows and shrinks with its own content, so there's no scrollbar inside the frame.

To pin it to your page's palette, add `?theme=light` or `?theme=dark` to the frame address in the snippet. Without one, the frame follows the visitor's own Athena theme preference, which won't necessarily match the page around it, so set it explicitly if your page is committed to one look.

Respondents don't sign in, and nothing identifies them beyond what your questions ask. On success the frame shows the same **"Response recorded"** confirmation the shared link does.

A form that has closed (by status, deadline, or response limit) shows its title and the closed notice in the frame, the same as the link does.

## Turn one off

Open a placement and the panel has an **Enabled** switch. Turning it off stops that placement loading and collecting immediately, everywhere it's pasted, while keeping its responses and letting you turn it back on later. That's the reversible option, and it's usually the one you want; the list marks it **Disabled** so you can see at a glance which placements are dormant.

**Delete** removes the embed for good. Every copy of that snippet stops working the moment you confirm, the address can't be brought back, and the responses it already collected stay in the form; they simply stop naming a placement. Deleting the form itself removes all of its embeds with it.

## Limits

- **25 embeds per form**, and **20 sites** per embed.
- **20 recorded values** and **20 passed-in keys** per embed, each value up to 500 characters.
- Submissions are rate limited per visitor, per embed.
