Assets Overview
Assets are the public and reusable pieces that campaigns depend on. They include landing pages, QR codes, templates, custom domains, uploaded files, online media, and edited images.
Assets - Main Features Overview
Reusable marketing assets: landing pages, QR codes, templates, custom domains, and files. This page explains how customers should use the Assets module in day-to-day LocalBoost AI operations, from setup to review and troubleshooting.
Main Features
- Landing pages.
- QR codes.
- Marketing templates.
- Custom domains.
- Files and image editor.
Recommended Workflow
- Create or select a template.
- Build the landing page or QR campaign.
- Attach media from Files.
- Assign custom domain when needed.
- Preview and publish.
- Track scans, visits, and submissions.
Views, Filters, and Review Options
- Filter assets by business.
- Filter by type and status.
- Search by asset name.
- Use folders for files.
- Review QR analytics by date.
Available Actions
- Create asset.
- Edit asset.
- Preview public asset.
- Download QR images.
- Upload or import files.
- Edit images.
- Assign domains.
Benefits
- Keeps campaign material reusable.
- Improves brand consistency.
- Supports print and digital campaigns.
- Makes public assets easier to manage.
Before Publishing or Activating
- Landing pages are mobile-friendly.
- QR codes scan successfully.
- Templates are customized.
- Custom domain DNS is verified.
- Files are optimized and accessible.
Troubleshooting
- If page does not open, check publish status and slug.
- If QR does not scan, regenerate at higher contrast.
- If file preview fails, check storage permissions.
- If domain fails, check DNS and SSL.
- If automation or AI does not run, check credits, provider settings, logs, and feature access.
Operational Notes
Use consistent naming for businesses, campaigns, templates, QR codes, automations, and CRM segments. Consistent naming makes reports easier to read and helps support teams diagnose issues quickly. When a feature depends on an addon, confirm the addon is installed, active, available in the current plan, and visible to the current workspace.