On this page
A creative is edited in PB after export. Later, a report shows its new title beside clicks from an external ad. Did the new version earn those clicks?
The current title alone cannot answer that question. Keep a handoff record connecting the exported version to the external ad and the evidence of what actually ran. Creative identity, editable version and provider identity are different parts of that record.
Freeze the package you intend to hand off
Before export, identify the selected copy, image and destination. Preserve their exact contents or the approved files and version references. Include the review date and the relevant check results.
An internal creative name is useful for organization but may change. A version number helps only when everyone knows which fields and assets belong to that version. Keep the actual approved package available for comparison.
Do not attach a review of one image to a later crop or assume a prior destination check covers a newly edited URL.
Record internal and external identities separately
A PB creative reference identifies work inside PB. The advertising provider's ad ID identifies an external record. An ad-group name may be a display label rather than the internal identifier required by an upload.
| Record | What to preserve |
|---|---|
| Internal creative | Creative and version references |
| Approved content | Exact copy, image reference and destination |
| Handoff event | Export time and exported package |
| External record | Verified provider account and ad ID when established |
| Representation | Local or provider preview and its date |
| Delivery evidence | Relevant reporting window and external identity |
This table is a manual handoff method. It does not imply that every field is automatically captured or permanently linked by PB.
Distinguish export from an external ad
Export prepares a package for a later workflow. It does not establish that a campaign was created, reviewed, activated or served.
Record the actual provider result when the authorized account owner completes the next step. If an upload is rejected, keep the rejection tied to the attempted package rather than treating the creative as delivered.
Token-backed asset links in an export can provide access to the asset. Keep those links in the authorized handoff, and redact their tokens from public tickets. Re-exporting is not a reliable assumption of revocation; use the product's actual supported behavior when access needs to end.
Compare previews by identity and time
A local preview shows the product's representation of the selected creative. An official provider preview depends on the external ad and available provider access. A saved PB draft alone does not establish that relationship.
When a provider preview is available, compare its copy, asset and destination with the approved package. Note any difference. An edit made in PB does not prove that the external ad changed with it.
A preview is also different from delivery evidence. It can show a representation without proving that anyone received an impression.
Walk through a version change
Illustrative example only. A fictional team exports version 2 on Monday and records the external ad ID after the provider handoff. On Wednesday, it edits the PB title and creates version 3, but does not update the external ad.
The current PB title now describes version 3. Performance from the original external ad still needs to be interpreted against the content actually handed off and served. The new title is not evidence that version 3 ran.
The team should preserve version 2's package and add a separate event if version 3 is later submitted externally. If it cannot establish which version was served during a period, label version attribution unresolved.
Keep reporting linkage honest
In the reviewed PB reporting flow, results are grouped by linked creative and can display its current title. That is not immutable attribution to the exact version that was served.
Matching based on creative text and destination can also become ambiguous when multiple drafts share the same fields. Use the external identity and handoff evidence to investigate the link rather than guessing from a familiar title.
If a report cannot distinguish versions, report at the supported creative or external-ad level and preserve the limitation. Do not divide aggregate results between versions using invented assumptions.
Hand off the next version with a clear event
Before the next export, confirm which version is selected and whether the intended change affects copy, asset or destination. Recheck the affected elements, preserve the new package and record the authorized external action when it occurs.
The useful history is a sequence of specific events: approved, exported, accepted externally, previewed and observed in delivery. Keep each event tied to the appropriate identity and date. That gives reviewers a way to understand later results even when the working creative continues to evolve.