Overview
Experiences and banners often need static images: a hero shot for a promotion, an icon for a banner, a product photo for a recommendation tile. The Assets explorer is the place to manage those images for the current property. It uploads to TagPipes' CDN and gives you a stable public URL you can paste into any experience.
The library is scoped per property. Switching properties in the top bar changes which assets are visible. There is no cross-property sharing yet, which keeps client work cleanly separated.
Navigate to Assets
Open Activate > Assets from the left sidebar. The grid shows every image uploaded for the current property with a thumbnail, the filename, dimensions, and the public URL. Hover any card to expose the copy and delete icons.
Upload an image
Click the Upload button. Drag a file into the modal or click to pick one from disk. Allowed formats are PNG, JPG, GIF, and WebP, up to 5 MB per file. SVG is not supported. The upload progresses in place; when it finishes, the new asset appears in the grid with its CDN URL ready to copy.
Copy the URL
Click the copy icon on any asset card to copy the public URL to your clipboard. Paste it into an experience's HTML, into a banner image field, or anywhere else you need a stable image link. The URL is hosted on TagPipes' CDN, so it loads fast from anywhere.
Delete an asset
Click the delete icon on the card. A confirmation modal appears. Confirm to remove the file from the CDN permanently. Be careful: URLs already in published experiences will break the moment you delete the underlying file, so make sure nothing is referencing it first.
Experiences don't have a built-in asset picker today. Copy the URL from the Assets page and paste it into the experience manually. A picker is on the roadmap but not the default flow today.
Performance tips
Activate is a real-time personalization layer, which means assets often render on the user's first paint. Heavy images delay that first paint and degrade the perceived speed of your site. Compress images before uploading, use WebP where possible, and aim for under 100 KB per asset. The CDN handles delivery efficiently, but it can't shrink files for you.
Troubleshooting
Upload fails with "file too large"
There is a per-file size cap to keep delivery fast. Compress the image (TinyPNG, ImageOptim, Squoosh) and re-upload. If you genuinely need a larger asset, talk to support about raising the property's cap.
The image doesn't appear after upload
Refresh the page. The grid loads on initial render and doesn't always pick up new uploads from concurrent sessions. If a refresh doesn't surface the asset, the upload failed silently somewhere mid-way; re-uploading is the fastest fix.