How-to guide

How to Create Immersal VPS AR

The Immersal VPS route in ARLOOPA Studio sits inside the geospatial create flow, but it has its own setup requirements. You begin with `Geospatial AR`, choose `Immersal VPS` as the provider, select the content type, and then work through the Immersal-specific selector. In Studio, that includes provider credentials and map selection, plus an optional map display toggle for projects that should also be shown on a broader location map. This guide explains that full branch and where it fits best.

Geospatial AR model illustration for VPS experiences

Best for

Teams that need the geospatial create flow but specifically want the Immersal VPS provider path and its mapped-space workflow.

Watch out for

This route includes provider-specific inputs and preparation, so it is not the right branch for buyers who have not decided on the mapping approach yet.

ARLOOPA fit

ARLOOPA Studio gives no-code teams a guided path through the Immersal VPS branch without forcing them to build the entire flow from scratch.

Tutorials

Video tutorial for this workflow

Watch the matching Studio walkthrough before you build so the setup, asset choices, and publishing steps are easier to follow.

Geospatial (VPS) AR

Bring your creations to life by placing them on real buildings and landmarks with Geospatial (VPS) AR.

Use case fit

When the Immersal VPS branch is the right geospatial path

Choose the Immersal VPS route when the project needs that provider-specific branch and the mapped-space workflow fits the use case better than the Google-based route. In Studio, that means treating provider setup as part of the creation process, not as a later technical add-on.

This path is a better fit when the team already knows the project belongs in a VPS-oriented workflow and is prepared to validate the mapped environment as part of launch readiness.

•Use this path when Immersal VPS is the intended provider, not just a fallback idea.
•Choose it when mapped-space preparation is part of the plan from the start.
•Avoid it if the project has not yet chosen its geospatial provider logic.

Studio steps

How to create Immersal VPS AR in ARLOOPA Studio

This route is the Immersal VPS branch inside the geospatial flow. It includes an extra selector step, so move slowly and finish the provider setup before you worry about fine details.

If you also want the experience to appear on a map, decide that during setup rather than after the build is finished.

Do not plan the phone check too early. You need to publish first, then test in the real mapped environment.

1Click `Create experience` in Studio.
2Choose `Geospatial AR`.
3Choose `Immersal VPS` as the provider.
4Pick the content type you want to attach to the mapped experience.
5Complete the Immersal setup, including the token, map selection, and any optional `Show on map` setting you need.
6Upload or generate the asset and review the Studio setup carefully.
7Click `Publish` to generate the live experience.
8Open the published experience in the real mapped environment and confirm that it works there.

Preparation

What to prepare before using the Immersal branch

This route is more operationally specific than the generic geospatial overview. Teams should have provider access, a clear understanding of the mapped environment, and a realistic testing plan before they commit to the branch. The more defined the location logic is, the smoother the build will be.

It also helps to know whether the optional map display matters to the final audience journey. Not every VPS experience needs that extra layer.

•Have the provider token and map selection plan ready before final testing.
•Decide early whether the experience should also appear on a broader map.
•Keep the first VPS pilot small enough to validate mapped behavior clearly.
•Test in the real environment and validate any prepared artifacts before release.

Launch guidance

Where the Immersal VPS route usually performs best

The Immersal branch fits projects that need a VPS-specific place workflow rather than a simpler location overlay. It can be useful for mapped spaces, cultural or event environments, and other projects where the provider choice itself shapes the operational plan.

Like all geospatial work, it is strongest when the location experience is central to the value rather than just decorative.

•Mapped-space cultural, tourism, and event experiences.
•Geospatial pilots where provider-specific VPS behavior is part of the brief.
•Projects that need optional map visibility in addition to the main place experience.
•Place-based rollouts where field validation is already planned as part of production.

FAQ

How to Create Immersal VPS AR FAQ

How do I access the Immersal VPS path in Studio?

Choose Geospatial AR first, then select Immersal VPS as the provider on the next step.

What extra setup does the Immersal route require?

It includes the Immersal selector workflow, provider token handling, map selection, and optional map visibility settings.

Is the Immersal path still part of the normal Studio create flow?

Yes. It is a branch inside the geospatial flow, not a separate tool outside Studio.

What should teams validate before publishing?

They should validate provider setup, map selection, prepared artifacts, and real-world behavior at the target location.

Next step

Need help turning a how-to guide into a launch plan?

Use pricing and a live demo to validate the workflow, publishing path, and rollout scope before you build at full scale.

Existing Studio pages