Consistent naming
Standard campaign and UTM values reduce fragmented reporting.
Campaign templates
Start from a repeatable campaign structure.
Templates shorten repetitive setup while keeping each new asset independently owned and validated. Consistent names and designs make each campaign easier to recognize and maintain.
Create a campaignSafe defaults
Every generated asset still passes current validation and entitlement rules.
Versioned change
Updating a template does not rewrite historical campaigns.
Reuse the decisions that should be consistent
A template can capture parameter vocabulary, QR appearance, Bio theme, and campaign conventions. The owner still reviews the destination, public alias, and audience context before publishing.
This avoids cloning stale destinations or credentials from an old campaign.
Protect historical meaning
Published campaigns retain the template revision they used. A later naming or design change applies to new work unless an owner explicitly migrates an asset.
Versioned defaults keep analytics comparisons understandable across time.
Match templates to the current plan
Template access comes from the customer’s current plan instead of a label written into the page. If billing status is temporarily unavailable, Gods.ly safely falls back to free-plan capabilities.
Downgrading preserves customer data even when a premium template becomes read-only.
Common questions
What teams ask before they start.
Will editing a template change existing assets?
No. Existing assets retain their stored definition; revised templates apply to future creation unless a user chooses a controlled migration.
Can templates contain custom scripts?
No. Templates store validated structured values, not executable plugin code.
Start with a real workflow