Embed for Tally - Forms Block, Popup & Elementor Widget

No. Embed for Tally is an independent plugin by Hendra Setiawan and is not affiliated with or endorsed by Tally. "Tally" is a trademark of its owner.

Yes. Forms are built at tally.so; a free Tally account is enough.

No. The block and the widget work as soon as you paste a form link. The Get started page under the Tally Forms menu is a shortcut: save your form there once and every new block and widget starts with it, and a shortcode without an id uses it. Each block, widget or shortcode can still use a different form.

Add the Tally Form block, paste your form link, and choose Button that opens a popup in the block sidebar. Your page shows a button that opens the form in a centred popup. You can change the button text and style, open the popup automatically, and close it after the form is submitted. With the shortcode, use [tally_form id="mRoDv3" mode="popup" button_text="Contact us"].

Yes. Under Open the form, choose after a delay, when the visitor is about to leave (exit intent, desktop only) or after scrolling part of the page. You can show it only once per visitor, stop showing it after the form is submitted, and hide the button so the popup only opens automatically. With the shortcode: [tally_form id="mRoDv3" mode="popup" open_trigger="exit" show_once="1" hide_button="1"].

Yes. Choose Slide-in in the corner in the block sidebar, or use mode="slidein" in the shortcode. The form opens in a small panel in the bottom corner of the page.

In your form's share link (https://tally.so/r/mRoDv3), embed URL (https://tally.so/embed/mRoDv3) or editor URL (https://tally.so/forms/mRoDv3/edit). You can paste any of those, or just the ID.

In Elementor, add the Tally Form widget. It has the same options as the block and a Style tab for the popup button. In Divi, Bricks and other builders, put [tally_form id="..."] in the builder's shortcode, text or HTML element. Tally Forms → Shortcode builds the shortcode for you. The same shortcode works in the classic editor and in widgets.

Yes. Add static values in the block's Hidden fields panel (one key=value per line) or with hidden="source=website,campaign=spring" in the shortcode. The keys must match hidden fields in your Tally form. Tally also receives the page's address and query parameters automatically.

Yes. Turn on Fill in name and email for logged-in visitors under Tally Forms → Advanced, and add hidden fields called name and email to your Tally form (or map them to questions with Tally's prefill). Logged-in visitors then get their WordPress display name and email passed to the form; nothing is passed for other visitors.

You don't need to learn them: Tally Forms → Shortcode writes the shortcode from the options you choose. For reference: id (required), mode (inline, popup, slidein), hide_title, transparent, auto_height, height (px), align (left or center), button_text, button_style (inherit or basic), open_trigger (click, delay, exit, scroll), open_delay (seconds), open_scroll (percent of the page), show_once, hide_after_submit, hide_button (automatic opening only), width (popup width in px), overlay (slide-in only), emoji, emoji_animation, auto_close (seconds), hidden (key=value,key2=value2), title (accessible name of the form).

The plugin leaves the shortcode to that plugin and tells you so on the Shortcode page, so nothing on your site changes. The block and the Elementor widget keep working as usual.

In your Tally account. The plugin displays your forms; everything visitors send is stored by Tally. Open the form in Tally and go to its Submissions tab.

Not yet. If you would use that, click Request this feature under Tally Forms → Submissions, or say so in the support forum. Those requests decide what gets built next.

Yes. Turn on Track form submissions under Tally Forms → Advanced. Form views and submissions are then reported to the tags already on your site. In Google Tag Manager, use a Custom Event trigger for Tally.FormSubmitted. Sites that use Google Analytics without Tag Manager receive a tally_form_submitted event. Meta Pixel receives Tally.FormSubmitted as a custom event. The plugin adds no tags of its own, so your site needs one of these installed.

Yes. Enter the page's address under Thank-you page on Tally Forms → Advanced. After a submission the visitor is sent there. This works for forms on the page, popups and slide-ins.

Turn on Remember UTM parameters under Tally Forms → Advanced. The plugin keeps utm_source and the other UTM parameters for the visit and passes them to forms on later pages. Add hidden fields with the same names to your Tally form to store them. The values are kept in the visitor's browser until the tab closes, so check whether your cookie notice should mention it.

Yes. Turn on Ask before loading forms under Tally Forms → Advanced. Inline forms then show a short message and a "Load form" button, and nothing is requested from Tally until the visitor clicks. Popups load when their button is clicked, and popups that open by themselves wait until a form has been loaded. You can change the message and the button label.

Yes, once you turn it on. It is off by default: go to Tally Forms → Advanced and turn on Let AI assistants use Embed for Tally. On WordPress 6.9 or newer, the plugin then registers three WordPress Abilities that assistants connected to your site (for example through WordPress's MCP adapter) can use: get the embed code for a form, insert a form into a post or page, and list the posts that contain a form. They follow WordPress permissions: only users who can edit a post can add a form to it. Inserting a form never changes existing content, and it is saved as a normal revision. If Elementor is active: recent Elementor versions switch the site's MCP server off until you turn MCP on under Elementor → Elementor MCP. Turn it on there if your assistant can't find the abilities.

No. Tally's embed script is only loaded on pages where a form is actually rendered, and the form iframe is lazy-loaded. If you turn on Remember UTM parameters, a few lines of inline JavaScript are added to every page so the parameters are kept from the page the visitor lands on; no extra file is loaded.

The block editor script in build/ is compiled from the files in src/, which are included in the plugin. To rebuild it, run npm install and then npm run build in the plugin folder. The build uses @wordpress/scripts, as listed in package.json.