Record the pre-change identity
Save the submitted channel or message link, visible name and order reference. Note which part of the identity is expected to change. A new display name can be harmless for some workflows, but the buyer should not assume all target references behave identically.
Check the active service's rules
Ask how the selected service treats a changed address or access configuration. Keep the response with the campaign record. If processing depends on the original input, an administrator's update may require review rather than automatically following the new public identity.
Communicate the transition once
Provide old and new references, the time of change and the existing order ID in a concise support request if needed. Avoid creating several separate cases with incomplete details. Confirm the current request's status before purchasing another order to compensate for an unexplained delay.
Decision checklist
| Decision | What to check |
|---|---|
| Old reference | Original purchase target |
| New reference | Current community identity |
| Timeline | Time and nature of change |
Worked example
For illustration, a channel changes its public branding during a post-view campaign. The campaign manager should preserve the old message references and explain their relationship to the current channel. A screenshot of the new name alone may not resolve what the service originally received.
Example figures explain the decision; they are not current prices or promised results.