Dynamic Sources
Where each piece of dynamic content actually comes from — the post, your settings, a custom field, or a bundled asset.
Where the Data Behind a Tag Actually Lives
The Dynamic Tags Reference lists what each tag resolves to. This page covers where that data actually comes from — because it isn’t always the post itself.
🟦 The post itself
Title, excerpt, date, author name, and primary category all come straight from the post being rendered — native WordPress fields, always available, nothing to configure.
🟩 Site-wide settings, not auto-detected
{{site_logo}} and {{site_icon}} are set once, under Settings → Brand identity — deliberately not pulled automatically from your theme or the WordPress Customizer. Page builders like Bricks manage their own header and logo entirely outside the Customizer, so there’s no single reliable place to read a “site logo” from automatically across every setup. Picking it explicitly in Settings works the same way regardless of theme or builder.
🟧 Meta Box and ACF — two different targets
{{custom:field_key}} reads a Meta Box/ACF field from the post itself. {{author_photo}} is different: it reads a Meta Box/ACF field too, but from the author’s own user profile instead of the post — the field key is set once under Settings, not per-post.
🟥 Bundled, not uploaded
The 25 emoji available to Image layers are shipped with the plugin itself — local files, never fetched from an external CDN or uploaded by hand. Picking one from the grid doesn’t touch your media library at all.