Elementor Custom Fields — Field Forge Dynamic Content Integration
Download Log in

Field Forge + Elementor — Dynamic Content

Field Forge integrates with Elementor via the Dynamic Tags system. Every Field Forge field value is available as a dynamic source in Elementor widgets — drop a custom field into any text, image, or button widget with a few clicks, no PHP required. Works with Elementor free and Elementor Pro.


What Elementor Dynamic Tags are

Elementor’s Dynamic Tags system lets widgets pull content from dynamic sources instead of hard-coded values. Instead of typing “Product Name” into a Heading widget, you can select “Dynamic → Custom Field → Product Name” and the widget pulls the value from your current post’s custom field.

This is how Elementor Theme Builder templates work. A single template can render any product page by pulling product name, price, description, image, and features from custom fields dynamically.

Field Forge registers itself as a Dynamic Tag source, making all field groups available to Elementor widgets automatically.


How it works

Step 1: Install both plugins

Install Field Forge and Elementor (or Elementor Pro). Activate both. Field Forge detects Elementor on activation and registers its Dynamic Tag source.

Step 2: Create a field group

Use Field Forge’s visual builder to create a field group and assign it to a post type via location rules. For example:

  • Field group: Product Details
  • Location rule: Post type is equal to “product”
  • Fields: Product Name (text), Price (number), Description (textarea), Featured Image (image), Features (repeater)

Step 3: Use fields in Elementor widgets

Edit a product template (or any Elementor page). In any widget’s content field:

  1. Click the Dynamic button (the small database icon) next to the content field
  2. Select Field Forge → Product Details → Product Name
  3. The widget now displays the product’s name dynamically

Repeat for other fields — drop the Featured Image into an Image widget, the Price into a Price widget, and so on.

Step 4: Publish the template

Publish the Elementor template. Every product on your site now renders through this template with dynamic field values pulled from Field Forge.


Supported field types in Dynamic Tags

Field Forge exposes these field types as Elementor Dynamic Tags:

Text-based fields

  • Text, Textarea, Email, URL, Password, Number, Range → rendered as text
  • WYSIWYG → rendered as HTML content

Media fields

  • Image → drop into Image widget (returns ID, URL, or array depending on widget)
  • File → link text or file URL in Button / Text widgets
  • Gallery → use in Image Carousel or Gallery widgets
  • oEmbed → auto-embed in Video or HTML widgets

Choice fields

  • Select, Radio, Button Group → selected value as text
  • Checkbox → comma-separated values or array
  • True/False → conditional rendering (use with display conditions)

Relational fields

  • Post Object → linked post title or entire post data
  • Relationship → array of posts for use in Loop Builder (Elementor Pro)
  • Page Link → URL for Button widgets
  • User → user display name or email
  • Taxonomy → term names or links

Date/time fields

  • Date Picker → formatted date string
  • Time Picker → formatted time string
  • Color Picker → color value for custom color widgets

Compound fields

  • Repeater → use in Loop Grid widget (Elementor Pro) to render rows
  • Group → individual sub-field access via dot notation
  • Flexible Content → use with Loop Builder

Display conditions

Use Field Forge values in Elementor’s display conditions:

  • Show section only if “Featured Image” is set
  • Show CTA button only if “URL” is filled in
  • Hide sidebar on posts where “Hide Sidebar” checkbox is true

Elementor’s Display Conditions (Elementor Pro) read Field Forge values just like any other custom field.


Elementor Pro Theme Builder

For Elementor Pro users, Field Forge is especially powerful with Theme Builder:

  • Single Post templates — use Field Forge fields to render custom post type pages
  • Archive templates — use in Loop Grids to render field values per post
  • Header/Footer templates — pull site-wide settings from Field Forge options pages
  • Search result templates — dynamic content based on custom fields

Build one template, render it across hundreds of posts with Field Forge data.


Repeater fields in Loop Grids

Elementor Pro’s Loop Grid widget can iterate over Field Forge repeater rows:

  1. Add a Field Forge Repeater field (e.g., “Team Members” with Name, Photo, Bio sub-fields)
  2. In Elementor, add a Loop Grid widget
  3. Set the source to Field Forge Repeater → Team Members
  4. Build a loop template with dynamic tags for Name, Photo, and Bio
  5. The Loop Grid renders one item per repeater row

This replaces what you’d otherwise build with custom PHP and WP_Query loops.


Options pages in Elementor

Field Forge options page values are available throughout Elementor via:

Elementor → Site Settings → Custom CSS can reference options page values via CSS variables.

Elementor widgets can pull options page values via Dynamic Tags: select “Field Forge Options → Site Settings → Company Name” instead of “Field Forge → [Post] → Company Name.”

This is useful for global values (site logo, company info, social URLs) that should be consistent across templates.


Performance

Field Forge’s custom table storage and object cache integration mean Elementor pages render faster than they would with other custom fields plugins. Each Dynamic Tag lookup is cached, so repeated access to the same field on a single page adds no additional database overhead.

For Elementor archives with Loop Grids pulling data from 20+ posts, Field Forge’s batch loading eliminates the N+1 query problem that typically slows down Elementor + ACF combinations.


Migrating from ACF + Elementor

If you’re currently using ACF + Elementor’s ACF integration, migration to Field Forge is straightforward:

  1. Migrate ACF field groups and values to Field Forge (via the ACF importer)
  2. Field Forge registers as a Dynamic Tag source on activation
  3. Elementor templates that referenced ACF Dynamic Tags automatically pick up Field Forge’s registration

Most Elementor templates work unchanged after migration. In some cases, you may need to reselect the Dynamic Tag source from “ACF Field” to “Field Forge Field” in individual widgets, but the underlying data is the same.


Ready to use Field Forge with Elementor?

Get Field Forge — from $35/year →

Elementor integration is included in every version of Field Forge, including the free one.

Forge AI Assistant Online

Hi! I'm the Field Forge AI assistant. Ask me anything about the plugin — setup, features, troubleshooting, or development.

Just now
Powered by Forge AI · Browse docs