Get to know our frameworks

Select an app template built on your preferred framework.

Build apps on our native app editor. Use drag and drop elements, Velo code and Wix APIs to develop custom features.

Streamline your app development process with the Wix CLI. Get a familiar developer experience with minimal setup and configuration.

Take full control over your app's tech stack, deployment, and hosting.

App templates

Wix Blocks templates

Wix CLI templates

Self-hosted templates

Kickstart your app development with templates built on your preferred Wix developer tool. Browse templates for practical foundation and get to know the Wix ecosystem.

Wix App Templates for Developers

This example apps can be used as a starting point for building your own app, for concrete examples of how to use Wix framework, or for inspiration.

Choose a template.<0 />Build an app.

Browse by:

How to build it step by step:

This template is built with:

Read how this template was built, step by step.

How we built this template

Deployment instructions:

Choose a package manager and run the command in your terminal.

Copy command

Before you get started, make sure you have the following:

Prerequisite steps

Get started with Wix CLI

Begin by setting up your Next.js project with your preferred hosting platform.

Select your hosting service

Start the deployment flow and set up your template repo on Netlify. After you finish set up, come back here and add your Netlify custom domain.

Copy the code from our Git repo to deploy your app on any platform that supports Next.js.

Start the deployment flow and set up your template repo on Vercel. After you finish set up, come back here and add your Vercel generated URL.

Add the base URL and give your app a name.

App details

Go to the app dashboard and test your app to ensure a smooth integration within the Wix ecosystem. <0>Learn more about app checks and testing</0>

Define your environment

Terminal

Related templates

Note

Warning

Your app name will be used as the namespace suffix.

Name your app to generate a namespace. This lets you refer to your app in code later on.

Go Headless

Build Apps

Client

API Preview

Ricos

Develop Websites

REST

Velo

GraphQL (Alpha)

# About the Analytics Sessions API

The Analytics Sessions API enables developers to access session IDs collected from Wix sites.

<blockquote class='important'>
 Beta Feature: 
 This functionality is currently available to select beta users only.
</blockquote>

A session is a visit of a visitor to a site. A session starts when a visitor reaches the site, and ends after 30 minutes of inactivity. Within each session, a visitor can take multiple actions and view multiple pages. Each session is identified using a [browser session ID](fallback::https://hazelcast.com/glossary/web-session).

Wix offers select beta users an entry point to access selected analytics apps that record visitor sessions. When a site user (admin or contributor) accesses the entry point, Wix passes all relevant filters appended to the iframe URL, and your app can use the filter data to request a list of relevant visitor sessions from Wix. With this API, your app can extend Wix analytics data to help site owners identify pain points and find areas for improvement.

## Use cases
- [Record a visitor session and notify Wix that a recording has been made.](fallback::https://www.sbdautomotive.com/ja/wg-cgi/dev.wix.com/docs/rest/business-management/analytics/sessions/sample-flows#record-a-visitor-session-and-notify-wix-that-a-recording-has-been-made)
- [Display session recordings to users based on Wix's filter data.](fallback::https://www.sbdautomotive.com/ja/wg-cgi/dev.wix.com/docs/rest/business-management/analytics/sessions/sample-flows#display-session-recordings-to-users-based-on-Wixs-filter-data)
 
## Before you begin
- This functionality is currently available to select beta users only. If you are interested in providing such an app, reach out to [Wix Support](fallback::https://www.wix.com/support-chatbot?nodeId=25a57397-ccf7-4376-8b74-48d51edf7159&referral=devRels).
- Some calls in this API are asynchronous and return a job ID.
- All sessions are identified by their browser session IDs.
- An iframe dashboard page extension is required.
 
## Terminology

- **Session**: A visit of a visitor to a site. Within each session, a visitor can take multiple actions and view multiple pages.
- **Browser session ID**: An ID stored in the visitor's browser to identify the session.

# Sample flows

This article shares some possible use cases your app could support, as well as an example flow that could support each use case. You're certainly not limited to these use cases, but they can be a helpful jumping off point as you plan your app's implementation.

<blockquote class='important'>
 Beta Feature: 
 This functionality is currently available to select beta users only.
</blockquote>

## Record a visitor session and notify Wix that a recording has been made
When your app recognizes that a visitor session has begun, your app should:
1. Collect the browser session ID.
2. Record the visitor's session on the site, and map it to the browser session ID.
3. Notify Wix that a recording has been made by calling the [Mark Session as Recorded](fallback::https://www.sbdautomotive.com/ja/wg-cgi/dev.wix.com/docs/rest/business-management/analytics/sessions/mark-session-as-recorded) endpoint and passing the browser session ID.


## Display session recordings to users based on Wix's filter data
When a site user (admin or contributor) accesses the dedicated entry point for your app:
1. Wix calls your extension's iframe URL with filter data as query parameters.
2. Collect the filter data from the query parameters.
3. Call [List Sessions Async](fallback::https://www.sbdautomotive.com/ja/wg-cgi/dev.wix.com/docs/rest/business-management/analytics/sessions/list-sessions-async) with the filters from step 2.
4. Collect the job ID and call [Get List Sessions Job Result](fallback::https://www.sbdautomotive.com/ja/wg-cgi/dev.wix.com/docs/rest/business-management/analytics/sessions/get-list-sessions-job-result).
5. If the job is complete, collect the returned session IDs.
6. Display the browser sessions with the IDs returned in step 5.

value

Int32Value

StringValue

Conversion funnel details, meaning the steps in the journey the visitor has taken on the site.

exclude

include

ConversionFunnelSessionsParams

Request for getting store conversion sessions.

User timezone. If not provided it will be taken from site properties.

timezone

CountFunnelSessionsRequest

Custom time period with start & end dates.

predefinedTimePeriod

period

Response for getting store conversion sessions.

CountFunnelSessionsResponse

cartViewSessions

checkoutSessions

convertedSessions

productViewSessions

siteSessions

Recordings

Request for getting the total number of sessions.

CountSessionsRequest

Response for getting the total number of sessions.

sessions

CountSessionsResponse

Custom period end date in provided timezone. Returned data will include all dates until the requested end date.
For example, { startDate: '2024-01-01', endDate: '2024-01-03' } will return data for '2024-01-01' and '2024-01-02'

endDate

Custom period start date in provided timezone.

startDate

CustomTimePeriod

DeviceType

FunnelStep

jobId

limit

Number of items to skip in the current sort order.

offset

GetListSessionsJobResultRequest

GetListSessionsJobResultResponse

jobStatus

sessionIds

total

JobResult

JobStatus

User's timezone. Defaults to timezone as set in the [Site Properties API](https://www.sbdautomotive.com/ja/wg-cgi/dev.wix.com/docs/rest/business-management/site-properties/properties/properties-object).

ListSessionsAsyncRequest

Conversion funnel details. The steps in the journey the visitor has taken on the site.

params

ListSessionsAsyncResponse

sessionId

MarkSessionAsRecordedRequest

MarkSessionAsRecordedResponse

Page interactions, including where the user dropped off. For example:
- ["/{Homepage}", "__DROP__"]: Sessions where a user visited the site's homepage and then dropped off.
- ["", "__DROP__"]: Sessions where a user visited (any page) and then dropped off.
- ["", "", "__DROP__"]: Session where a user visited any page, then navigated to any page, and then dropped off.

pageInteractions

NavigationFlowSessionsParams

Predefined time period.
`THIS_WEEK`begins with Monday.

PredefinedTimePeriod

Session

type

SessionsByDeviceParams

Start an async job to retrieve a list of session IDs, given the provided filters. The following filters **must** be passed:
- Time period, either predefined or custom.
- Session filter, either navigation flow (page interactions), conversion funnel steps, or device type.