{"id":16942,"date":"2021-04-08T08:50:03","date_gmt":"2021-04-08T12:50:03","guid":{"rendered":"https:\/\/www.gravityforms.com\/?p=16942"},"modified":"2026-03-24T16:38:02","modified_gmt":"2026-03-24T20:38:02","slug":"embed-forms-using-code","status":"publish","type":"post","link":"https:\/\/www.gravityforms.com\/blog\/embed-forms-using-code\/","title":{"rendered":"How to Embed WordPress Forms Using Code"},"content":{"rendered":"\n

\"Embed
\nEmbedding forms into your content is pretty easy using Gravity Forms’ built-in support for WordPress Classic Editor<\/a> or Gutenberg.<\/a> You can even use the Form Widget, added to the WordPress Appearance Widgets menu, to embed a form into any of the WordPress widget areas.<\/p>\n\n\n\n\n\n\n\n

But… what if you want to embed the same form underneath the content on all of your blog posts? You can of course use the above to embed the form manually for each post, although that doesn’t sound like a smart way of achieving our goal, right?<\/p>\n\n\n\n

There must be a better way to make technology work for us, don’t you think?<\/p>\n\n\n\n

Well there is! We call it the function call embedding method<\/a>.<\/p>\n\n\n\n

What?<\/h2>\n\n\n\n

It basically consists of two functions provided by Gravity Forms core that you can use to embed your form using code:<\/p>\n\n\n\n

gravity_form()<\/a> – This is the main function, that takes care of displaying the form.<\/p>\n\n\n\n

gravity_form_enqueue_scripts()<\/a> – This function is a required <\/strong>companion, that will ask WordPress to enqueue the required CSS and JS files for the form.<\/p>\n\n\n\n

I will assume that you already know how to create and configure a Newsletter form<\/a>. Therefore I will focus this tutorial on using the above functions along with the WordPress filter the_content<\/a> and get_header<\/a> hook.<\/p>\n\n\n\n

Preparing gravity_form() to call our form.<\/h2>\n\n\n\n

First, we need to know the id of our form. My Newsletter form has id 5<\/strong>. This will be the first parameter for the gravity_form() function call, and the only one that is required<\/strong>. So you could just use the following:<\/p>\n\n\n

\ngravity_form( 5 );\n<\/pre>\n\n\n\n
But in this case I want also to enable ajax submission to avoid the page reloading when a visitor clicks the form button.<\/p>\n\n\n\n
The parameter to enable ajax submissions is the sixth parameter and another important parameter for this use case is the echo parameter <\/strong>– this last one we need to set to false to tell Gravity Forms to return the form instead of printing it directly to the screen.<\/p>\n\n\n\n
Therefore I will use default values for all the parameters except for the form id, ajax submission and echo<\/strong>, for which I will use 5, true and false respectively. My function call will look like this:<\/p>\n\n\n
\ngravity_form( 5, true, true, false, false, true, false, false );\n<\/pre>\n\n\n\n
You can find more details about each parameter by checking the documentation for the gravity_form() function call<\/a>.<\/p>\n\n\n\n
At this point we know already which function and parameters we will use to get the form.<\/p>\n\n\n\n
Preparing gravity_form_enqueue_scripts() to enqueue the required scripts.<\/h2>\n\n\n\n
Now we need to prepare the function that will ask WordPress to enqueue the required files for our form to be displayed and work as expected.<\/p>\n\n\n\n
gravity_form_enqueue_scripts() has only two parameters, the first one to specify the id of our form, and the second to make ajax submission enabled or not (disabled by default).<\/p>\n\n\n\n
We want to use ajax submission for our form, so we will use the two parameters, like this:<\/p>\n\n\n
\ngravity_form_enqueue_scripts( 5, true );\n<\/pre>\n\n\n\n
 <\/p>\n\n\n\n
Using WordPress core get_header and the_content to trigger our functions.<\/h2>\n\n\n\n
At this point we have the Gravity Forms functions ready, the only thing left is to call them when needed to make the magic happen.<\/p>\n\n\n\n
We will use the WordPress core get_header hook to run the function to enqueue the files, this hook runs just before wp_head so it will ensure the files are already enqueued before Gravity Forms needs them.<\/p>\n\n\n
\nfunction gf_enqueue_required_files() {\nGFCommon::log_debug( __METHOD__ . '(): running.' );\nif ( is_single() && 'post' === get_post_type() ) { \/\/ Do it only for Posts.\ngravity_form_enqueue_scripts( 5, true );\n}\n}\nadd_action( 'get_header', 'gf_enqueue_required_files' );\n<\/pre>\n\n\n\n
The snippet has an if statement that will ensure it runs only for WordPress default posts.<\/p>\n\n\n\n
And finally we’re going to add our form at the end of our posts’ content by using the following:<\/p>\n\n\n
\nfunction gf_add_newsletter_form_after_post( $content ) {\nGFCommon::log_debug( __METHOD__ . '(): running.' );\n\/\/ Form added after the post content.\n$content .= gravity_form( 5, true, true, false, false, true, false, false );\nreturn $content;\n}\nadd_filter( 'the_content', 'gf_add_newsletter_form_after_post' );\n<\/pre>\n\n\n\n
That’s it! Once you have the above snippets added to your site, your form will be added dynamically<\/strong> after the content on each WordPress post you publish.<\/p>\n\n\n\n
And you know what? If you change your mind later, you don’t need to edit all your posts. As you’re embedding the form on the fly with the snippets, you can simply remove the snippets to stop the form from being added after your posts. Isn’t it great when machines do the work for you? ?<\/p>\n\n\n\n
Not a Gravity Forms customer yet? Get started with a free personalized demo<\/a> and test out all the features that Gravity Forms has to offer!<\/em><\/p>\n\n\n\n
 <\/p>\n\n\n\n
\n
\"Gravity<\/figure>
<\/p>\n
If you want to keep up-to-date with what’s happening on the blog sign up for the Gravity Forms newsletter!<\/strong><\/p>\n<\/div>\n\n\n