Managing Projects

A ZapWorks project consists of a single augmented reality (AR) experience that can be launched via user-defined triggers and possesses individual analytics.

Projects can be created and modified from the ZapWorks dashboard.

To create a project, navigate to ZapWorks and select Create New Project. Upon project creation a ZapWorks tool (i.e. Studio, Designer, Universal AR or Widgets) must be selected. A minimum of one trigger must also be selected, at which point you'll be redirected to the Project Overview page.

After creation, additional triggers can be assigned from within the project overview page. Existing triggers can not be removed from a project.


Three project-level options are available under the Actions dropdown.

  • Duplicate: Duplicates the current experience's content to another project. Triggers, analytics and labels from the current project will not be carried over.
  • Get Deep Link ID: Learn more here.
  • Unpublish: Disables the project. This prevents the experience from being launched via any of its triggers.
  • Delete: Archives the project and deletes its content. This also prevents the experience from being launched via any of its triggers.


Labels allow you to organize projects under a common theme on your account, for example multiple experiences for a single campaign.

Projects grouped together under a label will also display aggregated analytics data.

Labels can be assigned to a project from its overview page. You can filter projects by their label through your workspace dashboard.


Project triggers determine the methods that an experience can be launched, e.g. via zapcode, QR code, deep link, etc.

The trigger(s) selected during the creation of the project will appear in the Triggers pane.

For more information on the different triggers available and their usage, check out our Triggers article.


Publishing a project makes your AR experience live so that it can be launched via the project's trigger(s).

Each time a project is published, a log is produced. These logs are accessible from the Overview and Experience tabs in a project.

Studio projects, once published, upload a ZPP file which can be downloaded from the Publish log.

Experiences must be published from within the tool they were created with, therefore, Studio experiences must be published from within Studio. For more information on publishing Studio projects please refer to this article.


Near real-time analytics data is provided for published projects, and can be accessed via the Analytics tab. Analytics information is available per project, per grouped projects (via labels), or across all projects on a workspace.

This data includes the number of views, as well as the views' country of origin and time of day.

For more information on the analytics data provided by ZapWorks, please refer to this article.

In-app title and icon

Scanned experiences will appear under the Recents tab on a user's device, within Zappar's native app or WebAR platform. By default, the experience will be titled Unknown Experience and no icon will be displayed.

The In-app options allow you to specify a title and icon to be displayed, instead of the default values.

A Lite Branded WebAR Distribution's name and icon will be used if there is one linked to the experience

zapcode branded_zapcode i