Skip to main content
Published: 2026-09-12 · Last reviewed: 2026-09-12 · Reading edit: 2026-09-12 Someone reads your migration guide and leaves. An ad showing how to check compatibility might help them continue; another generic “book a demo” message may add little. Retargeting gives eligible previous visitors or participants a next piece of information. Decide what that information should be before building the audience.

Decide whether the audience merits a campaign

Start with a meaningful interaction and a specific unresolved question. If the eligible audience is too small for stable delivery or the only creative repeats the original advertisement, improve the underlying experience first.

Set up the audience lifecycle

  1. Decide when someone joins the audience. Record the qualifying page or interaction, lookback period, geography, and applicable permission requirements. Review platform rules and your privacy implementation before tags or list uploads are activated.
  2. Separate situations. A pricing visitor may need purchasing clarity; a tutorial reader may need implementation help. Do not present browsing behavior as knowledge of a person’s private intentions.
  3. Decide when to stop showing the ads. Exclude people who completed the intended action where technically and lawfully possible. Consider customers, employees, support visitors, and people who withdrew permission. Explain matching delays and incomplete identification to campaign owners.
  4. Choose a next question. Use a comparison, demonstration, or buying guide that adds information. Keep recognizable brand cues without repeating the same urgency message indefinitely.
  5. Control exposure. Use available frequency and budget controls, inspect actual distribution, rotate fatigued creative, and set an end date. There is no universal frequency number that makes every campaign effective.
  6. Check what the ads added. Retargeted audiences are already selected for prior interaction. Compare appropriate holdouts where feasible; otherwise describe results as attributed outcomes and acknowledge selection bias.

Worked example

A hypothetical integration vendor retargets eligible visitors to its migration guide with a short demonstration of rollback and validation. Successful consultation requests leave the acquisition audience when the integration updates. Existing customers are directed to support content through their normal service channels instead. The dashboard shows eight attributed consultations. The team reports eight attributed consultations, not eight additional consultations caused by advertising. A future eligible-audience holdout can test the stronger claim if volume and platform capabilities permit.

Audience specification

Operational check

Test a qualifying visit and a completed action using your approved consent configuration. Verify that withdrawal reaches the relevant systems, not just the visible banner. Review audience membership logic after a site redesign: an old URL rule can quietly target the wrong group.

Try it with your own work

Choose one meaningful interaction and write the question a reader may still have afterward. Plan an answer, an audience expiry date, and the conditions that should stop the ads.

Sources and scope

The example is fictional; any numbers illustrate the method rather than a benchmark. Adapt the worksheet to your own situation. Paid social · Privacy and compliance operations Chapter guide · All playbooks
Copyright © 2026 Ivan Xu. All rights reserved. See the copyright and reuse terms. Canonical source: github.com/weilun88313/B2B-Playbook