Blocksify Pro lets Content Loop cards use supported fields from ACF or SCF, Meta Box, Pods, and Toolset.
Read Dynamic data in the Content Loop for the card-building workflow. The free Dynamic data overview explains the underlying data sources and shared controls.
Where to find field plugins
Select the Dynamic Field card item and open Field. Groups appear only for active plugins with supported fields assigned to the loop’s post type.
- Select the Content Loop, open General → Card, and find Card Elements.
- Add or expand a Dynamic Field card item.
- Open Field, find the required group, and select its field.
ACF and SCF
Blocksify Pro reads active ACF or SCF field groups assigned to the queried post type. The Listing Information group in this example contains Listing Highlight, Year Built, Open House, Listing Agent, and Brochure URL.

| Field type | What Blocksify Pro shows |
| Text, Text Area, Email, URL, Password | Plain text |
| Number, Range | Formatted number |
| WYSIWYG, oEmbed | Formatted content |
| Link, Page Link | Clickable URL |
| Image; File containing an image | Selected-size image |
| Gallery | Image grid |
| Date Picker, Date Time Picker, Time Picker | Formatted date or time |
| True/False | Customizable yes/no text |
| Select, Checkbox, Radio Button, Button Group | Choice label(s) |
| Color Picker | Color swatch |
| Post Object, Relationship | Linked published title(s) |
Taxonomy, User, Repeater, Flexible Content, Group, and Clone fields do not appear. Relationship fields can expose another field only when exactly one related post and one target post type are allowed. This only traverses one level and does not drill in when a field allows multiple related posts.
Meta Box
Supported fields registered for the queried post type appear under Meta Box. This example lists Price, Bedrooms, Bathrooms, Floor Area (sqm), Available From, Featured Listing, Photo Gallery, Listing Agent, and Virtual Tour.

| Field type | What Blocksify Pro shows |
| Text, Textarea, Email, Password, URL, Autocomplete | Plain text |
| Number, Range, Slider | Formatted number |
| WYSIWYG, oEmbed | Formatted content |
| Link | Clickable URL |
| Single Image | Selected-size image |
| Image, Image Advanced, Image Upload | Image grid |
| Date, Datetime, Time | Formatted date or time |
| Checkbox, Switch | Customizable yes/no text |
| Select, Select Advanced, Radio, Checkbox List, Button Group, Image Select | Choice label(s) |
| Color | Color swatch |
| Post | Linked published title(s) |
Cloneable fields, groups, taxonomy and user selectors, non-image files, and map-related fields do not appear. A Post field can expose a related field only when it accepts one post and one target post type.
Pods
Supported fields from the matching Pod appear under Pods. The picker sorts this example as Departure Date, Duration (days), Duration label, Guide, Highlights, Photo Gallery, and Price From.

| Field type | What Blocksify Pro shows |
| Plain Text, Phone, Email, Password, Slug | Plain text |
| Number, Currency | Formatted number |
| WYSIWYG, Paragraph, oEmbed | Formatted content |
| Website, Link | Clickable URL |
| Date, Date/Time, Time | Formatted date or time |
| Yes/No | Customizable yes/no text |
| Color Picker | Color swatch |
| Relationship (Related Type: Simple) | Choice label(s) |
| Relationship (Related Type: a post type) | Linked published title(s) |
| File / Image / Video or Avatar, single | Selected-size image |
| File / Image / Video or Avatar, multiple | Image grid |
Pods relationships work even when stored separately from ordinary custom fields. Relationships to taxonomies, users, media, or comments do not appear; Code, Heading, HTML, and repeating ordinary fields are also excluded. Only a single Relationship to one post type can expose a related field.
Toolset Types
Supported Toolset Types fields assigned to the queried post type appear under Toolset. Without Toolset installed, the adapter reports inactive and the Toolset group does not appear.
| Field type | What Blocksify Pro shows |
| Single Line, Multiple Lines, Email, Phone, Skype | Plain text |
| Numeric | Formatted number |
| WYSIWYG, Embedded Media | Formatted content |
| URL | Clickable URL |
| Image, single | Selected-size image |
| Image, repeating | Local-image grid |
| Date | Formatted date |
| Checkbox | Customizable yes/no text |
| Checkboxes, Radio, Select | Choice label(s) |
| Color Picker | Color swatch |
| Post Reference | Linked published title |
Disabled fields, repeating fields other than Image, and File, Audio, Video, Address, Map, Twitter, and Time fields do not appear. Only a single Post Reference can expose a field from its related post.
Custom fields without a plugin (raw meta key)
For an unmanaged custom field, open Field, find the Custom group, and choose Custom meta key…. The editor first shows a Meta key chooser and Field type; open the chooser to select an existing key or enter a custom one.

| Field type | What Blocksify Pro shows |
| Text | Plain text |
| Number | Formatted number |
| Rich text | Formatted content |
| URL | Clickable URL |
| Image | Selected-size attachment or image URL |
| Gallery | Attachment-ID image grid |
| Date | Formatted recognized date |
| Yes/No | Customizable yes/no text |
| Choice | Saved value(s) |
| Color | Color swatch |
Keys beginning with an underscore are protected and do not render publicly by default. Raw gallery values must contain attachment IDs, and related-post output is unavailable because an untyped key does not describe its target.
For any supported gallery, use the Media Slider card item when the card needs sliding media instead of the Dynamic Field image grid.