Experience URLs for an app

For your mobile developer. Every address starts from a link in Studio, then takes what your app knows about the participant.

The address to load

Here play.lindenhall.example stands for your experience domain. Every parameter is listed in Embed URLs and parameters.

Leave embedded=1 out. It's meant for a web page that holds the experience in a frame and scrolls to each panel. In a WebView, panels would then open off screen once the participant scrolls a long page. So a script your organisation limits to embedded experiences, with Script Context IFRAME_ONLY, doesn't run in the app. Ask your Studio admin to set it to ALL if it should.

What your app should add

• l, the language. Set it from your app's language setting. An app in French showing an experience in English is the most common complaint on this integration, and it's one parameter.
• fci, the participant. Use it when your app already knows who the participant is. With customer accounts connected, the experience asks them to sign in; with a recognition integration for the campaign, it opens as that person with no sign-in screen.

Build the address in the app

Compose it in the app rather than hardcoding a finished string, so language and participant follow the app's state:

https://play.lindenhall.example/<campaign-public-link>
  ?c=<touchpoint-id>
  &l=<the app's current language>
  &fci=<the signed-in member's identifier>

Percent-encode every value you add. Otherwise a loyalty identifier holding &, # or + arrives cut short or changed. Build the WebView has a working example.

Next steps

• WebView requirements
• Build the WebView
• Pass a known customer into an experience