Sidekick Spark lets you bring your Sidekick experience directly to your own website with a simple installation, enabling attendees to get answers and support without ever leaving your event page. Every event in Amego is automatically provisioned with its own Spark embed code, so there is nothing extra to request or set up before you get started. All you need to do is copy that code and add it to your site.
To find your embed code, open your event in Amego and go to Sidekick > Settings. Scroll down the Settings page until you reach the embed code section. Your code will look like this:
<script
type="module"
src="https://spark-widget.amego.com/sidekick.js"
data-event-id="XXXXX"
data-app-id="spark-widget"
defer
></script>
In the example above, XXXXX is a placeholder. Before you add the code to your website, make sure the data-event-id value is your event's actual ID rather than XXXXX. The embed code shown in your Sidekick Settings should already include the correct ID for your event, but it is worth double checking, especially if you are copying the code from another source or reusing it across events.
Once you have your embed code, paste the code into your website's HTML just before the closing </body> tag on any page where you want the widget to appear. You can add it to a single page, such as your event homepage, or to every page of your site if you want Sidekick available wherever attendees go. If your site is built on a platform or content management system, look for an option to add custom code to the page footer, which typically places the code in the right spot.
After the code is installed, you do not need to make any further changes to your website to update the experience. Everything is managed through your normal Sidekick settings in Amego, and any changes you make there will be reflected in the widget on your site. Your Sidekick uses one setup for both mobile and web, so the content and configuration you already have in place for your event will carry over automatically to your website.
Comments
0 comments
Article is closed for comments.