VELORYZ STUDIO / KNOWLEDGE

Promotion system overview

Campaigns, placements and display hierarchy.

Promotion system overview

VELORYZ Studio · Promotions, announcements and advertising placements Audience: Studio owners, campaign authors and QA reviewers Guide type: Practical Studio operations guide

Purpose

Promotion system overview should be treated as an end-to-end responsibility, not an isolated button. Start by defining what will change, who can approve it and how success will be checked. Campaigns, placements and display hierarchy.

Campaign management is available to authorised Studio owners inside the CMS. It is not an advertising network integration.

Availability and responsibility

The protected admin CMS supports announcement, promotional and advertisement campaigns with placements, scheduling and motion options. These are Studio-controlled placements, not an external advertising network or a guarantee of third-party impressions.

Before committing time or budget, confirm who operates this workflow: the visitor, the client portal user, a Studio owner, or the delivery team. A feature described in design documentation is not automatically a public account entitlement.

Before you begin

  • Approved copy, artwork, optional destination link and campaign owner
  • Start and end dates, display priority and audience relevance
  • Dismissal, frequency and accessibility requirements
  • A short list of measurable success criteria specifically for promotion system overview.
  • A recovery plan if the proposed change creates a regression.

Recommended procedure

  • Locate the relevant area or public route. For new projects, establish the brief at /create/; for owner-only content changes, use authenticated Studio Control at /admin. Do not assume a missing feature exists.
  • Define the specific work item for Promotion system overview: capture the initial state, user intent, relevant data, permissions, expected output and what must not change.
  • Follow the design and operating decisions listed below. Work in a draft, staging or reviewed project handoff where available; avoid editing live customer data experimentally.
  • Review the effect with real content and realistic viewport sizes. Record any exception and obtain the appropriate approval before a public change.
  • After the change, verify the public outcome rather than relying on a success message alone; preserve a reference to the reviewed version.

Topic-specific operating procedure

These steps apply to Promotion system overview. The implementation must be verified against the current Studio permissions, deployed provider connections and approved project scope.

  • Authorised admins should choose Broadcasts & ads, not the public project creator, for campaign management.
  • Define message purpose, campaign type, visual treatment and links before enabling any placement.
  • Save a draft and review multiple concurrent campaigns, frequency and mobile obstruction.
  • Publish only approved, time-bounded messages and verify them on the actual public site.

Evidence to retain

  • The original input or situation, and a clear before/after comparison.
  • The reviewed version, responsible owner and acceptance record.
  • Any limitation, follow-up decision, or safely reversible workaround.

Configuration and decision points

  • Open the protected /admin campaign area with authorised owner access.
  • Choose placement and campaign type, verify the text and optional primary/secondary destinations.
  • Keep the campaign disabled while reviewing preview, priority, scheduling and mobile layout.
  • Publish the approved draft and verify the campaign appears only within its configured window.

When more than one implementation is possible, prefer the simplest approach that remains accessible, maintainable and compatible with the current source. Note any cost, licensing, privacy, ownership and performance implications before approval.

Verification checklist

  • Calls to action link to the correct destination and clearly state what happens next.
  • Multiple active campaigns do not obscure critical navigation or form controls.
  • Sticky/pinned ads do not cover focus targets on mobile.
  • Animation respects motion preferences and dismissal works as intended.

Also confirm that the result addresses the original objective: Campaigns, placements and display hierarchy.. Review the customer-visible language, error states, navigation paths and the relevant device widths. A green build or a successful save does not by itself establish a correct production outcome.

Troubleshooting and recovery

  • Pause the affected campaign if placement or targeting looks wrong.
  • Restore the last known-good CMS publication from owner history.
  • If scheduling differs from expectations, confirm timezone interpretation and effective timestamps.

When asking for assistance, include the exact public URL or project reference, a concise reproduction path, the expected behaviour, actual behaviour, relevant timestamps and a redacted screenshot if useful. Never include passwords, access tokens or private customer records.

Related reading

  • [Announcement bars](/docs/studio/promotions/announcement-bars/)
  • [Promotional strips and banners](/docs/studio/promotions/banners/)
  • [Sliders and rotating campaigns](/docs/studio/promotions/sliders/)
  • [All VELORYZ documentation](/docs/)
  • [Studio documentation](/docs/studio/)
  • [Help Centre](/help/studio/)
  • [/design/](/design/)
  • [/motion/](/motion/)

Operational note

This article describes the Studio workflow and its acceptance criteria. Where a self-service control is not available, the action is coordinated with the Studio team rather than silently represented as automated.

Let’s talk
Make your project