What is Dynamic creative?

Dynamic creative inverts how an ad is made. Instead of building a finished unit, an advertiser supplies a set of parts — several images or videos, several headlines, several descriptions, a call to action — and the platform assembles a combination for each impression.

What it decides is which parts go together and which viewer sees which combination. What it does not do is write anything, design anything, or improve a component. The ceiling on what it can produce is set entirely by what was supplied.

That is the whole of the arrangement, and most of the confusion about it comes from expecting the assembly to add something. It multiplies; it does not create.

The single most consequential input decision is what "several" means.

An advertiser who supplies five headlines that say the same thing in different words has given the model five ways to say one thing. The combinations differ and the message does not, so the assembly optimises something that does not matter and the account concludes dynamic creative does nothing.

An advertiser who supplies five headlines naming five different problems has given the model a real decision, and it will find which problem resonates with which kind of viewer — which is a thing no hand-built ad set can do at that granularity.

The same applies to images. Five crops of one photograph are one image. A product shot, a person using it, a result, a comparison and a detail are five.

The rule that falls out: supply different arguments, not different wordings.

The finished unit. The advertiser cannot guarantee that a particular headline appears with a particular image, which matters when the pairing carries the meaning. A headline that refers to what is in the picture is a hazard under dynamic assembly.

Clean testing. Combination-level reporting is usually limited or absent. An account cannot easily answer which combination won, only which components appeared often and how the whole performed. A conventional creative test — two versions, everything else held constant — is hard to run inside the format.

Some brand control. Where a brand specifies exactly how type, logo and imagery are arranged, an assembly that varies the arrangement will produce units that do not comply.

Each of these is a real cost and each is worth accepting in exchange for coverage, in the situations where coverage is what the account needs.

Large accounts with many audiences. The number of sensible combinations exceeds what any team will build by hand, and per-viewer adaptation is worth more than per-unit control.

Accounts with proven arguments. Once an account knows which propositions work, dynamic assembly is a good way to extract more from them.

Ongoing campaigns. The format rewards a steady supply of components and punishes a set that never changes.

While learning. If the open question is which argument works, separate ads answer it and dynamic assembly obscures it. Test first, assemble afterwards.

When the pairing matters. A headline that depends on a specific image, a comparison whose two halves have to appear together, a sequence — none of these survive recombination.

On a small account. Few conversions means little for the model to learn from, and the assembly is close to random.

Make components independent. Every headline should work with every image, because it will have to. Anything that refers to "the photo above" or "this offer" is a component that will eventually appear somewhere it makes no sense.

Cover the shapes. Vertical, square and landscape assets composed for each placement, not one asset cropped three ways.

Keep the set small enough to learn on. A very large component set spreads delivery so thinly that most components never accumulate enough impressions to be judged, and the model's early choices become self-reinforcing.

Read component-level reporting where it exists. Most platforms report how individual assets performed even when they will not report combinations. That is where the remaining signal about what works lives, and it feeds the next round of production.

Refresh on a cadence. Fatigue applies to components as it does to finished ads, and an assembly drawing from a stale library produces stale ads in novel arrangements.

Dynamic creative, responsive search ads and asset groups are the same idea on different surfaces: the advertiser supplies parts and the platform assembles.

The pattern is the direction every major platform has moved in, and the reason is consistent. Per-auction assembly using signals the advertiser cannot see outperforms a fixed unit, at the cost of the advertiser knowing what any individual person saw.

The skill that remains is upstream of the assembly: deciding what arguments to make, producing components that are genuinely different, and reading the component-level signal to decide what to produce next. That is a creative job rather than a media one, which is the same conclusion the rest of the discipline has been arriving at.

Because combination reporting is thin, the productive place to run a test is above the assembly rather than within it.

Two campaigns or two ad sets, each with its own component library built around a different proposition, compared on outcomes. The assembly optimises inside each, the comparison happens between them, and the result is attributable.

What does not work is supplying two propositions to one assembly and hoping the reporting separates them. It will not: the components get mixed, the delivery is chosen rather than randomised, and whatever the report shows is a consequence of the platform's preference as much as of the audience's.

This is the same discipline that applies to any automated allocation. Put things in the same container when you want the platform to choose between them, and in different containers when you want to know which is better.

Enough components to give the assembly choices, each making a different argument.

Every component independent, so any combination reads sensibly.

Every placement's shape supplied, composed rather than cropped.

Nothing that depends on a pairing — no headline that refers to the image, no description that completes a sentence started elsewhere.

A refresh schedule, because the library fatigues even though the arrangements are new.

Component-level reporting read on a cadence, since it is the only signal the format returns about what is working.