Overview
This guide explains how to configure banner images for the Visual Preview signature experience within the Opensense Outlook Add-in. Banners are commonly used for internal campaigns, branding promotions, or external marketing messages. When implemented correctly, banners support basic view and click tracking, allowing teams to measure impressions and engagement without requiring a routed solution.
Note: This configuration applies only to the Visual Preview experience. For routed deployments (e.g., plaintext block or stamping), Opensense supports no-code banner configuration using the [[abm]] token.
Sample HTML Snippet
Below is a standard example of a banner using the required HTML format. This snippet includes both a clickable link (link.html
) and the associated banner image (logo.png
):
<a href="https://smart.customer.com/sig/{{sgsusername}}//pilot/pilot/link.html" target="_blank">
<img border="0" src="https://smart.customer.com/sig/{{sgsusername}}/pilot/pilot/pilot/logo.png">
</a>
The
href
defines the click-through destination (used for click tracking).The
src
references the image to be displayed (used for view tracking).
Both files (link.html
and logo.png
) should be hosted in the appropriate asset structure under the smart.domain.com
namespace.
URL Structure and Tagging Breakdown
Each component of the URL has a specific role in determining which banner content is displayed. Below is the breakdown of the path:
Example Link:https://smart.customer.com/sig/{{username}}/pilot/us_mb/default/link.html
Segment | Label | Description |
---|---|---|
| Folder | Base directory for signature assets |
| User-specific placeholder (typically injected dynamically) | |
| Assigned Tag | Optional campaign tag assigned via signature assignment |
| Fallback Tag | Regional or audience-specific fallback tag if none is assigned |
| Fallback Ad Name | Default banner name to show when no override exists |
| Filename | Banner components: link for tracking, image for visual rendering |
Tip: Leaving the "Assigned Tag" blank allows the fallback logic to determine which banner is served. This makes it easy to support account-wide or division-wide default banners.
Implementation Steps
To configure a banner for use in the Visual Preview experience, please reach out to help@opensense.com.
Troubleshooting
Issue | Suggested Action |
---|---|
Banner does not display | Confirm the |
Click tracking not working | Check that |
Incorrect user data populating | Ensure the |
Signature not updating | Refresh Outlook and clear the add-in cache (Add-in → Settings → Clear Cache) |
Note: Opensense cannot control behavior inside all email clients. If images fall back to hosted links, this is due to client-level rendering limitations.
Alternative for Routed Deployments
For routing/stamping customers, banner logic can be injected using the simplified no-code [[abm]]
token. This method supports multiple banners, advanced targeting, and guaranteed rendering across all platforms.
Opensense Support
For further assistance, contact Opensense Support:
Email: help@opensense.com
Knowledge Base: help.opensense.com