In this article:
- Obtaining the Embed code
- Applying the right size
- Avoid embedding multiple publications on a single page
Obtaining the Embed code
For every publication, you can click on the Share option and select the Embed tab where you will find a unique embed code to add onto your website or landing page.
You can also automatically embed your most recent publication on your website or blog with only a one-time setup required. This is specially helpful if you have weekly or monthly catalogs.
You'll find this particular embed code in the Website integration tab of your group's settings.
Locating the Website integration code:
TIP: When using this feature, we recommend that you always keep at least one Publication online to ensure that there is something for this integration to show your visitors. Click here to read more.
Applying the right size
Hotspots are hidden if the publication becomes smaller:
If the publications becomes even smaller (400 x 400 pixels or less), the bottom bar with the Open button disappears as well. Because the content is hardly visible anymore at this scale we recommend to use an image or animation instead, and link it to a new landing page where the publication is embedded as large as possible.
Avoid embedding multiple publications on a single page
Even though it is possible to embed and load multiple publications on a single page, this can have a negative impact on the way your publications are tracked and any reporting you based on this.
Increased bounce rate
For example, if a user only interacts with one of the embedded publications, the other publications will register a bounce (a session that has seen no interactions). Therefor, the bounce rate of your publications can increase significantly.
Report filters sowing incorrect results
Embedding multiple publications on a single page can also contaminate reports that rely on publication-filters. As Google Analytics is not able to track the embedded publications individually pageviews and events get blended into a single session. If you are using custom dimensions to filter pageviews and events on publication-level, details from one publication can be reported as originating from another publication.