---
title: "Multilingual Campaigns for Marketing Agencies - PerfLocale"
description: "Get campaign pages translated inside WordPress: a scoped Translator role, machine translation, XLIFF hand-off, and a per-language completion dashboard."
canonical: "https://perflocale.com/use-cases/marketing-agencies/"
source: "https://perflocale.com/use-cases/marketing-agencies/"
format: "markdown"
---
# PerfLocale for Marketing Agencies

Get campaign pages into every market from inside WordPress, next to the page you’re translating — instead of round-tripping documents by email.

## What usually slows marketing teams down

Running a campaign in five languages isn't hard because of the writing - it's hard because of the handover. A translator gets sent a Word document, the campaign page goes live before their edits come back, and when the English source gets a late tweak nobody can tell which translations went stale.

PerfLocale doesn't try to be a translation management system - there are no assignments, deadlines, or approval queues in it. What it does is put translating, handing off, and tracking coverage where campaign teams actually work: inside WordPress, next to the page you're translating.

## What you get

### A translator role that only does translator things

Give freelancers, in-country specialists, or review clients access to translate - without handing over admin rights to the site. They see what they need to see, and nothing else. No more "don't click anything else" phone calls.

### You can tell which translations went stale

PerfLocale hashes the source content it translated from. When someone edits the English page after the fact, the affected translations are flagged as needing an update instead of quietly drifting out of date behind a green checkmark.

### First drafts from the engine you already pay for

DeepL, Google Cloud Translation, Microsoft Azure Translator, or LibreTranslate — plus a custom endpoint if your agency has its own translation service. Bring your own API key; PerfLocale resells nothing and adds no markup. A monthly character limit and a cost estimate before each run keep the bill predictable.

### Bulk work runs in the background, not in your browser tab

Translating a whole campaign section, scanning a theme for strings, or importing from another plugin all run as background jobs you can watch, cancel, and retry from the Jobs screen. Closing the tab doesn't kill the run, and a stalled provider doesn't take the admin down with it.

### XLIFF export and import for external translators and CAT tools

Export content as industry-standard XLIFF, send it to your LSP or your in-house CAT tool, import the translated file when it comes back. Works both ways, no copy-paste into textareas.

### A dashboard you can screenshot for the weekly client call

Live completion percentages by language and by post type. When a client asks how the German launch is tracking, you open one page, not a folder of status docs.

### The campaign site stays as fast as the one you pitched

Landing pages get judged on load time, and adding five languages shouldn't undo that. PerfLocale’s own code stays a small fraction of total page time, with three layers of caching in front of it — so the language count is not what slows the page down.

## Running multiple clients on one setup

Each site keeps its own languages, translations, and string catalogue — nothing is shared between clients, whether they sit on separate installs or on subsites of one multisite network. There is no cross-site translation reuse to configure or to accidentally leak, and PerfLocale's free GPL license means there's no per-site cost either way.

## Pricing

PerfLocale is free under GPL-2.0+. No agency tier, no seats, no paid addons. Install it on every campaign site you manage without worrying about license fees eating the project margin. Support runs through the free WordPress.org forums.

[Install from WordPress.org](https://wordpress.org/plugins/perflocale/) [See the machine-translation features](https://perflocale.com/features/machine-translation/)