For advanced users utilizing 3rd party platforms embedded into Cadence, we offer a few advanced methods for authentication with external platforms.

In simple terms: 3rd party platforms may require a separate login or basic user information. The methods outlined in this article show you how you can make embedded platforms more seamless to avoid attendees needing to enter in basic information or create a separate account.

Which option is right for you is dependent on support within the 3rd party platform you're embedding.

METHODS

URL Attributes

Example Use Case: The external platformed embedded requires users to enter their first name and last name. Instead of forcing users to retype their info, you can automatically pass variables within your embed URL.

Supported Attributes

[[firstname]] = First name of attendee, i.e "Jane"

[[lastname]] = Last name of attendee, i.e. "Smith"

[[fullname]] = Full name of attendee, i.e. "Jane Smith"

[[email]] = Email of attendee, i.e. "janesmith@eventcadence.com"

[[title]] = Title of attendee, i.e. "Senior Director"

[[company]] =  Company of attendee, i.e. "Acme. Inc"

Example Embed Code

Below is a standard embed code, this will work on its own, however, the platform asks attendees for Email and their First Name. Using attributes we can automatically pass this info to the external platform.

Unmodified Embed

 <iframe id="iframe_landing_page"
width="300"
height="200"
src="https://live.remo.co/e/my-event">
</iframe>

Modified Embed with First Name and Email

 <iframe id="iframe_landing_page"
width="300"
height="200"
src="https://live.remo.co/e/my-event?name="[[firstname]]"&email="[[email]]">
</iframe>

You can see in the above example, adding ?name="[[firstname]]"&email="[[email]]" to the embed code will pass this information.

TIPS

  • The name of the attribute is dependent on the 3rd party platform being used. Some may require First Name to be expressed as not as firstname=, but something entirely different such as first_name, name1, displayname or something different than name used in the example. in the example of first_name, you would express this in the embed code as ?first_name="[[firstname]]

Base64 Support for URL Attributes

If your embedding platform utilizes base64 encoding for URL attributes, you can just add .base64 to any attribute. For example:

[[firstname.base64]] = First name of attendee encoded as base64

URL-Encoding Support for Attributes

Not all text is friendly within URLs, and sometimes the text needs to be in URL-encoded format to play nicely with some systems. For example "Event Cadence" with URL-encoded format is represented as "Event%20Cadence%0A". If you need attributes to be in URL-encoded format, just add .urlencoded to your attribute.

[[firstname.urlencoded]] = First name of attendee with URL encoding

You can also combine Base64 and URL-encoding together, for example:

[[firstname.base64.urlencoded]] = First name of attendee with base64 and URL encoding

Signed URLs

Signed URLs allow an authentication token to be passed to the 3rd Party platform via the embedded iframe via adding an HTTP.

SETUP

  1. Access your Integrations Tab within Event Setup > Integrations via the Cadence Admin site.

  2. Download the Public Certificate

  3. Import the Public Certificate into your 3rd Party Platform

  4. Modify your embed code - Example

❗❗❗[[DRAFT NEED REFERENCES TO PLATFORM]] ❗❗❗

Unmodified Embed

 <iframe id="iframe_landing_page"
width="300"
height="200"
src="https://live.remo.co/e/my-event">
</iframe>

Modified Embed with Signed URL

 <iframe id="iframe_landing_page"
width="300"
height="200"
src="{{signedurl:https://live.remo.co/e/my-event}}">
</iframe>

You can see in the above example, adding {{signedurl: before the URL and }}at the end of the URL will add authentication to the URL of each person who accesses the URL.

SSO

Related Articles

Did this answer your question?