Audience: CMS Users, Integration Partners
Yes. Add an HTTPS EventPilot app link to your external website. Do not use the plain urn: value as the website link. The EventPilot link must include both the action URN and a Base64-encoded copy of that same URN.
Before you begin
- Collect the session IDs from the Conference App Builder. IDs are case-sensitive.
- Use the app link for the correct project and webapp shell. The easiest way to get the correct starting link is to open Tab Layouts, find an item under App Tabs, and use Copy link to page.
- The attendee must be signed in for the schedule change to be saved to their account.
1. Create the action URN
To add one session, use:
urn:eventpilot:all:agenda:add_sched:SESSION_ID
To add several sessions at once, separate the session IDs with a pipe character (|):
urn:eventpilot:all:agenda:add_sched:SESSION_ID_1|SESSION_ID_2|SESSION_ID_3
For example:
urn:eventpilot:all:agenda:add_sched:201|201-mod
2. Base64-encode the complete URN
Base64-encode the exact action URN from the previous step. Encode only the URN, not the EventPilot website address.
For the example above:
URN: urn:eventpilot:all:agenda:add_sched:201|201-mod
Base64: dXJuOmV2ZW50cGlsb3Q6YWxsOmFnZW5kYTphZGRfc2NoZWQ6MjAxfDIwMS1tb2Q=
The decoded b64urn value must match the urn value exactly.
3. Build the EventPilot link
Use this format:
https://SERVER/webapp/APP_SHELL/index.php?page=urn&project=PROJECT_ID&urn=ACTION_URN&b64urn=BASE64_URN
Replace:
SERVERandAPP_SHELLwith the values from a copied app-tab link.PROJECT_IDwith the project ID from the Conference App Builder.ACTION_URNwith the URN from step 1.BASE64_URNwith the Base64 value from step 2.
Complete EPDEMO example:
Add the EPDEMO sessions to My Schedule
Do the colons need to be URL-encoded as %3A?
No. Colons in the urn query value can remain as plain colons. A URL-building tool may convert them to %3A; that encoded form is equivalent and also works.
Other characters should still be safely URL-encoded when the link is assembled. For example, the pipe character may appear as %7C, and the trailing equals sign in a Base64 value may appear as %3D. In HTML, write the separators between query parameters as &.
4. Add the link to your external website
Use the complete HTTPS EventPilot link as the anchor's href:
<a href="https://eppro01.ativ.me/webapp/epexpress/index.php?page=urn&project=EPDEMO&urn=urn:eventpilot:all:agenda:add_sched:201%7C201-mod&b64urn=dXJuOmV2ZW50cGlsb3Q6YWxsOmFnZW5kYTphZGRfc2NoZWQ6MjAxfDIwMS1tb2Q%3D"
rel="external">
Add these sessions to My Schedule
</a>
Do not use a plain href="urn:eventpilot:..." link on an external website.
5. Test the link
- Publish the sessions and app changes to proof.
- Sign in to the proof app or webapp with a test attendee account.
- Confirm that the test sessions are not already in My Schedule.
- Open the external web page and select the add-to-schedule link.
- Return to My Schedule and confirm that every session in the URN was added.
Link to the external web page from the app
If attendees will reach your external page from an app tab or button:
- Open the item in ActionBuilder.
- Select the Website action.
- Select Internal Browser.
- Paste the external page URL. It must begin with
https://. - Click Save.
- Publish to proof and test the complete flow.
FAQ
How do I remove sessions instead?
Change add_sched to rem_sched, then create a new Base64 value from the complete removal URN. Both query parameters must contain the removal action.
urn:eventpilot:all:agenda:rem_sched:201|201-mod
Can I reuse the Base64 value after changing a session ID?
No. Any change to the action or session IDs changes the URN, so you must Base64-encode the updated URN again.
Why should I copy an existing app-tab link first?
The webapp shell in the URL is not always the same as the project ID. Copying an existing app-tab link preserves the correct server and shell for the project.