A video can have a different local identifier in the agency spreadsheet, the ad server and the publisher report. Each system may work correctly on its own while the campaign team spends hours deciding which rows describe the same creative. That manual join becomes harder when one campaign has many versions or runs across several platforms.
Persistent creative identifiers address a specific part of that problem: carrying a recognizable creative identity across organizational boundaries. The migration includes registration policy, transport and reporting. Adding a field without preserving it through the workflow can leave the original reconciliation task intact.
Agree on what the identifier identifies.
IAB Tech Lab's Ad Creative ID Framework describes registration and persistent identifiers for video creative. VAST's UniversalAdId provides a place to convey an identifier and its registry. The registry context matters because a value alone may not tell a receiving system which authority issued it.
Ask the creative owner and registry how revisions, versions and localizations should be represented. Do not invent a universal rule that every change always reuses the same ID or always creates a new one. The operational requirement is that the identifier agrees with the registered creative and the registry's policy.
Keep campaign IDs, placement IDs, local creative IDs and persistent creative identity as separate fields. They answer different questions. A campaign may contain several creatives, and the same registered creative may appear in more than one campaign. Overwriting those relationships with a single convenient ID creates a new reporting problem.
Find where identity is lost today.
Trace a small set of creatives from the approved asset through ad-server output, wrappers, insertion or playback and the final report. Save the actual values at each point. Include an unchanged creative used in two destinations and two distinct creatives that have similar names.
Compare this trace with the existing manual process. Record which joins require a filename, spreadsheet lookup or human judgment. Those steps give the migration a measurable target. A claim that identity is fragmented is less useful than a list of the handoffs where the identifier disappears or changes meaning.
Include the data warehouse or reporting team in this review. A perfectly populated VAST response does little for reconciliation if the receiving system drops the field before reporting. Decide which report will expose the persistent identity and how unknown or invalid values will appear.
Migrate registration and transport together.
Assign an owner for registration, a validation step for the issued value and a mapping from existing local IDs. Retain the original registry response or other authorized registration record. Avoid silently generating a plausible-looking identifier when registration information is missing.
Implement the VAST representation supported by the destination. Where a legacy route is involved, review the 2024 addendum and confirm that the receiver consumes that structure. A supported extension can meet a specific need without assuming a whole delivery chain has moved to a newer version.
Use VASTLint to check the supplied document. Keep registration validation as a separate check where required. Correct syntax and a plausible format do not prove that the registry issued that value for the intended asset.
Get VAST spec updates, platform guides, and release notes in your inbox.
Prove that the value survives the complete handoff.
Run a dated test and compare the original registration, VAST response and destination output. Confirm that the identifier and registry context remain associated with the same intended creative. Inspect the report the campaign team will actually use, not only a player debug panel.
Add a missing-value test and a deliberately mismatched mapping in a controlled environment. Verify that the workflow reports the condition and routes it to the right owner. A process that replaces every unknown value with the same placeholder can appear complete while destroying the identity needed for reconciliation.
Retain an accepted unchanged creative as a control. When the mapping code changes, rerun that control along with the failure cases. This catches regressions in ordinary accepted messages as well as the newly added identifier path.
Measure reconciliation before promising other outcomes.
Count records joined automatically, records sent for review and actual review time. State the campaign scope and the rules used for matching. Compare like periods and explain changes in creative volume or partner mix. A reduction in unmatched records is useful evidence even before a revenue effect is known.
Do not equate a creative identifier with cross-device audience identity or automatic frequency control. A platform must use the signal in an appropriate decisioning system, and it may need other information. Carrying the identifier makes some workflows possible; it does not establish that those workflows have been implemented.
The same limit applies to duplicate suppression, competitive separation and measurement. Identify the consumer of the field and inspect its behavior before claiming an outcome. A data transport improvement should be reported as such until the downstream result is documented.
Put ownership into the next creative brief.
Specify who supplies the registered ID, who verifies it against the intended asset and who confirms it in the destination report. Define a correction process for a mistaken mapping and a rule for retaining historical records. These decisions prevent a technically correct field from becoming another manually maintained mystery.
Repeat the document checks with VASTLint when tags change, and repeat the reporting test when an integration changes. A successful migration gives campaign teams a dependable way to recognize the same creative across handoffs and a measured account of the work that recognition removes.