Linking content to your app

Created by Glen Barnes, Modified on Wed, 3 Jul at 6:13 AM by Natalie Nguyen

Is your new tour ready and you want to add it to the app? Then keep reading to find out how to link content to your app. We say content because any collection list, tour, embedded webpage or individual screen can be linked to your app. 


You can either link this new content by adding a new tab button or add this new content to an available tour or list.

Okay, let's get linking.


How to link content to your app:


Option 1: Create a new tab button.


Go to your project in the STQRY Builder >> Click on Tabs.


Here, you can see what is already linked to the app and also link new tours or content. 


To start creating a new tab, click on New Tab (+). You can then either create a Menu or link existing screens or collections from the library if they have already been created.



Option 2: Add the new content to an available tour or list.


Click on Projects (1), then Tabs (2). Hover over the ellipsis and click on Edit app tab (3) to access the collection.




Now you are in the collection. A collection is essentially a group, in which you can add (1) a new screen or (2) an available screen/tour/list. Click on Content (if this is a list) or Stops (if this is a tour) to see what is already linked and link new screens/tours.



(1) Adding a new screen to a tour.

You have the option here to add a new screen or choose a screen from the library.







(2) Adding a new screen/tour/list to a collection list.


You have the option here to add a new screen or choose a screen/tour/list from the library.






You can update the content at any time. For the changes to show in the app, you should hit Save in the builder. In the app, you should go to the app settings and hit "Check for updated content".



Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article