Page Builder Integrations

Use WPVoicer audio output in real builder workflows.

WPVoicer is built to work with common WordPress builder stacks so teams can render dynamic post audio, including optional intro/outro text in the generated MP3, without custom pipeline work.

Integrations

Pick your page builder.

Instructions and setup notes for each supported builder — so you can place the audio player exactly where it fits your templates.

Elementor Integration

How to place the audio player inside Elementor single post templates using dynamic fields.

Bricks Integration

How to use WPVoicer dynamic tags inside Bricks templates so each post loads its own audio.

Breakdance Integration

How to connect WPVoicer audio to Breakdance fields without touching API configuration.

Implementation map

All integrations start from the same WPVoicer output: the generated MP3 attached to the current WordPress post. If intro/outro text is enabled in the plugin, it is already part of that audio file; the builder only needs to read the right dynamic value.

Elementor Pro Use WPVoicer Audio URL in dynamic URL fields, or WPVoicer Audio ID where an attachment ID is required.
Bricks Use {voicer_audio_audio_url} for the MP3 URL, or {voicer_audio_audio_id} for the Media Library attachment ID.
Breakdance Select Dynamic Data -> WPVoicer -> Audio URL in URL-capable fields.
Universal fallback Use [voicer_audio_audio] when a shortcode-based player is the cleaner option.
FAQ

Integration questions.

Common questions about how WPVoicer audio attaches to WordPress posts and shows up inside builder templates.

Do integrations call the WPVoicer API directly?

No. The builder reads the generated audio attached to the current WordPress post. WPVoicer handles generation, including optional intro/outro text, through the plugin workflow.

Which builders are currently documented?

The current implementation pages cover Elementor Pro, Bricks and Breakdance, with builder-specific fields and fallback shortcode usage.

Can the shortcode be used instead?

Yes. The universal fallback is [voicer_audio_audio] when a shortcode-based player is the cleaner implementation path.

Does each post get its own audio value?

Yes. The dynamic value resolves against the current WordPress post context, so a single template can render different audio files per article.