Dynamic tags always read the page they are on. A Heading set to Post Title shows the title of the page being viewed, an Image set to Featured Image shows that page’s image, and so on. The Dynamic Data Provider changes what “the page” means for one Container: you point the Container at a piece of content, and every dynamic tag inside it reads that content instead.
It is available on any Elementor Container in Rey 3.4.0 and above, and it is on by default. If you cannot find it, check that the Dynamic Data Provider for Containers module is enabled in Rey Dashboard > Modules.
Where to find it
Select a Container, open the Advanced tab, and expand the Dynamic Data Provider section. Everything is in one place: you pick a source, and optionally what to do when the source is missing.
The setting applies to everything inside the Container: headings, text, images, buttons, backgrounds, links, and nested containers. It also applies to the Container’s own settings, so a Container whose Link is a dynamic tag will link to the source you picked.
The data sources
The Data Source dropdown is the only required choice. Everything below it changes depending on what you pick.
Post, Page or Custom Post Type
Pick a Post Type first, then the exact item in Select Content. Use it when you want a specific, hand picked piece of content somewhere it does not normally appear, such as a “read this first” post promoted on the homepage.
Product
The same thing, limited to WooCommerce products, so you do not have to select the post type first. Inside the Container you can use any product related dynamic tag, and WooCommerce shortcodes and widgets that read the current product will follow it as well.
Taxonomy Term
Any term from any taxonomy: a blog category, a tag, a product category, a brand, an attribute term. Inside the Container, dynamic tags behave as if you were on that term’s archive page, so the term name, description and image are all available.
ACF Relation Field
Instead of naming the content yourself, you let a field on the current page name it. This is the option to use when the answer changes from page to page.
Only fields that point at other content are accepted: Post Object, Relationship and Taxonomy. Choose it in Select Field, or type a field key by hand in Or add custom field key if it does not appear in the list. When the field holds several items, Item Number decides which one to use, counting from 1.
A typical use: every product has a “Recommended accessory” Post Object field, and one Container on the product template shows that accessory, whichever it is.
Inherited (from where this is used)
The options above name one fixed piece of content. This one does not: it takes the data from whatever is displaying the Container at that moment. It is the option to use inside anything reusable, above all Global Sections.
A Container can be inside several things at once. A mega menu panel, for example, is a Global Section, opened by a menu item, on a page. All three are candidates, so Inherit From lets you say which one you mean:
- Menu item, its own fields: the menu item itself. Use it when you add an ACF field group whose location rule is Menu Item, for instance a promo image and a subtitle set per menu item. The Container then shows the fields of the item whose panel is open.
- Menu item link, the page or category it points to: follows the link instead. If the menu item points at a product category, the Container shows that category’s name, description and image, with nothing to fill in per item. Menu items that are custom links have nothing to point at, so nothing is shown.
- The Global Section this container is in: the Global Section post itself, useful for fields you attach to the section rather than to the page.
- The parent data provider, card or loop item: the nearest source already opened around it, for example the product of the card the Container sits in, or another Dynamic Data Provider Container wrapping this one.
- The page being viewed: the real page, post, product or archive term the visitor is on. Useful inside a Global Section that has to describe the current page, and to get back to the page from inside a Container that changed the source.
- The current item in loop: the item being rendered right now, which is what you want inside third party loops and repeaters.
- Other variable: for developers. See the last section.
Hide if source is missing
Sources can come up empty: an ACF field left blank, a menu item that is a plain link, a Global Section used somewhere it was not designed for. By default the Container still renders, and everything inside it falls back to the current page. Turn this switch on and the Container is not output at all instead, which is usually what you want for a promo block that would otherwise repeat the page you are already on.
Three things worth knowing
Nothing is guessed. If you pick a source but leave its selection empty, Rey does not go looking for a substitute. The Container simply keeps showing the current page, and the editor tells you so with a warning under the empty field. On a product page that can look like it found a product on its own: it did not, it is showing the product you are on.
The editor preview is not always right. The editor shows the current page’s data until the preview reloads, and for the Inherited source it cannot be right at all, because nothing is displaying the Container inside the editor. Check that one on the front end.
It shows one item, not a list. This is not a loop or a query. To repeat content, use the Grid, the Carousel, or the Cards, and combine them with a provider Container if you need one fixed item next to a list.
Example: a mega menu that describes each item
The goal: one mega menu panel, reused by six menu items, where each item shows its own category image and description. Without the provider you would build six panels.
- Build one Global Section of type Mega Menu, with the layout you want.
- In it, add a Container and set Data Source to Inherited (from where this is used), then Inherit From to Menu item link, the page or category it points to.
- Inside that Container, use ordinary dynamic tags: an Image on the term image, a Heading on the term title, a Text on the term description.
- Assign the same Global Section to all six menu items, in Appearance > Menus.
Each item now opens the same panel filled with its own category. If you would rather write the text per menu item than pull it from the category, add an ACF field group located on Menu Item and switch Inherit From to Menu item, its own fields.
For developers
The Other variable option reads a PHP global by name, which is how the built in options work internally. Type the name in Variable Name, without the dollar sign. The value can be a post ID, a term ID, a WP_Post, a WP_Term, a WooCommerce product object, or an array, in which case the last entry is used.
You do not actually need a global to exist. Each name has a filter, so the value can come from your own code:
// Container set to "Other variable", with "featured_id" typed in.
add_filter( 'reycore/container_data_provider/variable/featured_id', function( $value ){
return get_option( 'my_featured_product_id' );
} );There is also a catch all filter, which receives the name as its second argument:
add_filter( 'reycore/container_data_provider/variable', function( $value, $name, $settings ){
return $value;
}, 10, 3 );To decide the source entirely in code, whatever the Container is set to, use the filter that runs last, right before the data is swapped in. Returning false means “no source”, and the Hide if source is missing switch then applies:
add_filter( 'reycore/container_data_provider/context_args', function( $args, $source, $settings ){
if( 'product' !== $source ){
return $args;
}
// A post: array('type' => 'post', 'id' => 123). A term: array('type' => 'term', 'term' => 45).
return array( 'type' => 'post', 'id' => 123 );
}, 10, 3 );Snippets go in your child theme’s functions.php, or in a plugin like Code Snippets. Do not edit the parent theme, your changes would be lost on the next update.




