The embed codes generated in your Entase account drop a ready-made event widget into a page. They are designed to be copied and pasted with no development work — see Embedding events on your website for how to get one.
This page documents the options you can add to that snippet, and how to configure the checkout it opens.
The widget loads the JavaScript client itself, so you do not add client.js alongside it. It also does not need a publishable key: the widget is served by Entase, so the checkout is authorized through the widget rather than through a key on your page.
Configuration
Each widget is configured with an options object:
<div id="entase_OBJ_CODE"></div>
<script>
window.entase = window.entase || { o: [] };
window.entase.o.push({
obj: 'OBJ_CODE',
theme: 'dark',
ext: true
});
</script>
<script src="https://js.entase.com/embed.js" async></script>obj ties the configuration to its container: the widget renders into the element whose id is entase_ followed by the same code. If that element is missing, the widget logs a warning and renders nothing.
Push one entry per widget to place several on a page.
| Name | Type | Default | Description |
|---|---|---|---|
obj | string | — | The object code from your embed snippet. Required. |
width | string | 'auto' | Container width as a CSS value. 'auto' means full width. |
height | string | 'auto' | Container height as a CSS value. 'auto' starts at 200px and the widget resizes itself to fit its content. |
theme | string | 'light' | 'light' or 'dark'. |
locale | string | 'auto' | Widget language. 'auto' reads the lang attribute of your <html> element. |
ext | boolean | false | Extended layout — adds the event name and poster above the dates. |
attribution | boolean | true | Shows the Entase attribution line. Set to false to hide it. |
client | object | {} | Options passed to the JavaScript client that opens the checkout. |
The container is given a minimum width of 200px regardless of width, below which the widget cannot lay out correctly.
Configuring the checkout
client accepts the same options as the client constructor, so the checkout opened from a widget can be styled and sized like one you open yourself:
window.entase.o.push({
obj: 'OBJ_CODE',
client: {
checkoutMode: 'pane',
pane: { width: '60vw' },
backdrop: true,
backdropColor: '#101014'
}
});See Constructor options for the full list.
Two caveats. tprm is set by the widget itself from the page URL (see below), so a value passed here is replaced. And when several widgets share a page, they share one client instance — the client options of the last widget initialized are the ones in effect, so keep them identical across widgets on the same page.
Automatic campaign forwarding
Unlike the standalone client, the widget reads your page's query string and forwards known campaign parameters to both the widget and the checkout:
sgm, utm_source, utm_medium, utm_campaign, utm_term, utm_content, utm_id, utm_source_platform, utm_creative_format, fbclid
A visitor arriving on yoursite.com/concert?utm_source=facebook&sgm=SOCIAL has that attribution recorded against any resulting order without further configuration. Parameters outside this list are ignored — to carry your own, open the checkout with the client directly and set tprm yourself. See Tracking and consent.