All Collections
Event Builder
Pages & Menu
External services
WebView Content Button: use case and settings
WebView Content Button: use case and settings
Updated over a week ago

Content Buttons are the gates to your Community and Event! With them, you can manage how to display your content. As there are several types of Content Buttons in Swapcard, here you will learn about the WebView Content Button.

If you need to, you can learn more about the basics of Content Buttons with this article: Setting up Content Buttons.

Content

Link to an external website or a file. For instance, it can be used to link to a PDF file of the floor plan, or any link to third-party services. The content can either be opened in a new tab, or in an embedded iFrame:

With the embedded iFrame option, the content is directly displayed within your Event or Community.

When users click the WebView Content Buttons on the homepage or top navigation bar, they stay on the same tab, as shown below:

Screen_Shot_2022-10-19_at_14.43.54.png

To embed an image or a PDF, you first need to host it on your server, and paste the resulting URL in the Website field. If you do not have the technical capabilities, or if you prefer to host it on Swapcard servers, please reach out to our Support Team, or your Success Manager.

Use case

Provide a way for Attendees and Exhibitors to access content that can't/shouldn't be hosted directly within your Swapcard Event or Community.

Design

You can set up a Button background image (or a button color instead) and a Page background image.

Visibility

You can decide which Group(s) of Participants can see the Content Button, and whether you want to make it visible to unregistered Guests (publicly). Depending on the complexity of your Event, you could show different WebView Content Buttons to different Groups of Participants. For example, this is commonly used to hide Participants who belong to a "VIP Attendee"-like Group from those in the "Standard Attendee" Group.

Data

In the Data tab, you can edit the content URL, and how it can be accessed (via another tab, or an embedded iFrame)

Did this answer your question?