Goal

Want a button that opens a web page the instant someone taps it? A Web URL button does exactly that. You give it a web address (the URL) as its content source, and the page opens inside the app’s own built-in browser (a webview) — so the user never has to leave your app. It’s the easiest way to put pages that already live on the web in front of your users — a terms-of-service page, a privacy policy, an external booking page, a help center, or any marketing page — without rebuilding a single one of them as a native screen.

Better still, there’s no code involved and no App Store / Play Store rebuild to wait on. A Web URL button lives as app content, and it reaches your app the moment you publish.

Before you start

• Admin access to Mobile App Manager → App Setup.
• The web address you want to open, copied and ready to paste. Use a full address including https:// (for example https://example.com/privacy).
• A decision about placement. A Web URL button can live on your app’s main navigation (the home grid / tab bar) or in the Left Menu (the slide-out drawer). You choose the placement by which tab you’re working on in App Setup — Main Navigation or Left Menu.

Already comfortable adding a button in general? Then this article is just the Web-URL-specific pass through Add a new screen (button) to your app — jump straight to step 3.

Steps

1. Open App Setup and choose a placement

1. In the WordPress admin, go to Mobile App Manager → App Setup.
2. Choose where the button should appear:
   • For the home screen, stay on the Main Navigation tab.
   • For the slide-out drawer, switch to the Left Menu tab.

If your app uses managed user roles, start there: pick the role you’re editing in the Content for Role dropdown first, since buttons are stored per role.

2. Add a button

1. Scroll to the add-new section at the bottom of the button list (the red + with the prompt to add a button).
2. Click the +. A new button is created at the bottom of the list.

Here’s a shortcut worth knowing: new buttons start out with Web URL as their default content type. So the button you just added may already be a Web URL button, and all that’s likely left to do is fill in the address.

3. Set the content type to Web URL

1. Expand the new button if it isn’t already open.
2. In the Content Type dropdown, choose Web URL (if it isn’t already selected).

4. Enter the web address as the content source

Once Web URL is set as the content type, a single-line content source field shows up with the placeholder http:// — that’s where your address goes.

1. Click into the content-source field.
2. Paste or type the full web address you want the button to open — for example https://example.com/terms.
3. Make sure the address is complete. This field is a plain URL box, so it needs the scheme included (https://) — and https:// is the better choice over http:// for a page that loads cleanly inside the app.

That’s the whole configuration, really — one field. Whatever URL you type here is exactly what gets handed to the app to open, nothing more.

5. Name the button and set its icon

1. In the button’s header row, type the button name users will see (for example “Privacy Policy” or “Book Now”).
2. Click the icon area to choose an image — from the bundled icon sets or your media library.
3. Use the Text / Image checkboxes to control whether the label, the icon, or both are shown.

6. Reorder, preview, and publish

1. Drag the button by its move handle to position it among your other buttons.
2. Turn to the Previewer and scan the QR code to open the page on an actual device before it goes live — it’s the best way to see how the page really renders on a phone screen.
3. When it looks right, publish to push the button out to your app.

How it behaves

• It opens in-app. Tap the button, and the address opens right inside the app’s built-in browser — the user reads the page, backs out, and keeps going, never handed off to Safari or Chrome.
• Whatever you type is what opens. The content source you enter goes straight through to the app, as-is. There’s no separate “page title” or behavior field on this button type — the URL is the entire configuration.
• Mobile-friendly pages work best. The page renders at phone width inside the app, so aim Web URL buttons at pages that already look good on mobile — a long desktop-only page can feel cramped in that space.

Notes and gotchas

• Use a full, working URL. If the page won’t open, check the address first — the usual culprits are a missing https://, a typo, or a page that blocks being embedded. Test that same URL in a desktop browser to make sure it loads there.
• In-app browser vs. handing off to the system browser. This button is built to keep the user inside the app’s browser. Want to also let people pop the page out into their device’s full browser — say, for a page that needs the user’s own logged-in session? Turn on the app-wide setting Show external browser button on web view, which adds an “open in browser” control to the in-app webview. It’s a global app setting, not a separate button type.
• Logged-in / personalized pages. A plain Web URL opens the page anonymously, so the page has no way of automatically knowing who the app user is. The button itself offers only the one URL field — there’s no admin option here to inject the signed-in user or account code. Passing that context into the URL, or sharing the app’s login session with the page, is more advanced territory; if you need it, ask the MAM team.
• Buttons are per-role and per-placement. A Web URL button added on the Main Navigation tab for one role has nothing to do with the same button in the Left Menu, or in another role. If a button seems to “disappear,” check that you’re viewing the role and placement you created it under.
• Deleting. Each button carries a Delete Button link in its expanded options — deleting it removes the button from that placement and role only, nothing else.

Related

• Add a new screen (button) to your app — the general flow for adding any button and choosing its content type.
• Content classes overview — the full catalog of screen / button types and what each one renders.
• Show external browser button on web view — the app setting that lets users pop a Web URL out to their device’s system browser.
• Set up the bottom tab bar for your app — make a Web URL one of your main tabs.

What’s next

Once you’ve seen the Web URL button working in the Previewer, think about where it belongs for the long run: a legal page usually settles into the Left Menu, while a high-traffic destination — a store, a booking page — earns its spot on the Main Navigation tab (the home grid or tab bar). From there, just repeat these steps for every external page you want to bring into the app.