Complete product guide for growth, routing, analytics, and operations

Who uses it

Core business outcomes

Create and brand links

• Create a destination URL and assign a short code.
• Use custom slug support when the active plan allows it.
• Select the root domain, including approved custom domains.
• Choose no-expiry links or time-based activation windows.

Traffic control

• Set geo redirect rules by country.
• Run weighted A/B testing with variant destinations.
• Use affiliate-safe interstitial behavior when direct routing is risky.
• Control starts-at and ends-at scheduling for launches or limited campaigns.

Editing and governance

• Edit destination, domain, slug, timing, or routing behavior when the plan allows link editing.
• Clear start or end times explicitly when a schedule should be removed.
• Review last updated time and edit history directly in link detail.
• Track changes without losing the original short code identity.

Overview metrics

• Engagements and average daily traffic.
• Active links and active QR assets in the workspace.
• Distinct countries and referrer groups reached.
• Suspicious click counts and clean traffic rate.

Highlights and dashboards

• Top links, top referrers, top days, and top locations.
• Saved dashboard modules for time series, devices, referrers, and locations.
• Custom module ordering and module naming.
• Filter by date range and available scoped dimensions.

How the data is produced

• Public link clicks write device, browser, referrer, and location fields.
• QR scans can feed the same analytics pipeline when tied to a short link.
• Referrer groups are derived automatically from UTM source and HTTP referrer.
• Locations use country and city fields collected at click time.

Static QR operations

• Create QR assets for URLs or short links.
• Download and distribute the generated asset.
• Keep QR management under plan-based controls.

Dynamic QR operations

• Edit the QR target without regenerating the public-facing code.
• Use a short link as the QR destination to inherit link logic and analytics.
• Apply plan-level entitlement for dynamic target editing separately from basic QR access.

Campaign lifecycle

• Create campaigns as draft, active, paused, completed, or archived.
• Assign source, optional budget, objectives, notes, and start/end windows.
• Duplicate successful campaigns into new drafts.
• Use bulk actions to activate, pause, archive, or delete multiple campaigns.

Campaign analytics

• Review tracked clicks, valid clicks, suspicious rate, unique visitors, and attributed links.
• Inspect source, medium, browser, and country breakdowns.
• Use performance trend cards to analyze campaign behavior over time.
• Use budget only when you want commercial efficiency metrics such as cost per click.

How campaign attribution works

• A campaign is not tied to only one short link by default.
• Attribution is matched by utm_campaign in the click URL.
• The campaign slug is the matching key used by the reporting system.
• If multiple short links receive visits with the same utm_campaign value, all matching visits roll up into the same campaign.

Recommended flow

• Create the campaign first and confirm the final slug.
• Use that slug in every outbound URL as utm_campaign=<slug>.
• Keep utm_source and utm_medium consistent across channels so breakdowns stay clean.
• Check Reports / Logs first when validating new campaign traffic.

Metric definitions

• Tracked clicks: Total click events whose utm_campaign matches the campaign slug.
• Valid clicks: Tracked clicks minus suspicious clicks.
• Suspicious clicks: Events flagged by traffic quality logic.
• Unique visitors: Distinct visitors approximated from tracked client IPs in the current implementation.
• Attributed links: Distinct short links that generated visits for the same campaign slug.
• Top sources / medium mix / device mix / top browsers / top countries: Breakdowns generated from stored visit metadata.

Cost metric formulas

• CPC: budget / total clicks. This is shown only when budget is greater than zero and the campaign has clicks.
• Cost / attributed click: budget / valid clicks. This uses non-suspicious clicks only.
• If budget is blank or zero, cost metrics are intentionally left empty.
• If no clicks are tracked yet, cost metrics are intentionally left empty.

Operational use

• Publish landing pages tied to campaigns and branded links.
• Use consistent messaging, SEO metadata, and public slugs.
• Track page-linked traffic through the broader analytics system.

Members and roles

• Invite colleagues with role-based access.
• Track invite delivery, resend status, and invite links.
• Restrict invite emails to supported addresses according to current platform policy.

Operational control

• Switch workspaces from the workspace console.
• Review role assignments and ownership transfer paths.
• Use workspace-scoped plan enforcement across features and limits.

Customer billing

• Choose a plan from Billing and proceed to checkout.
• Stripe is used for hosted payment completion.
• Refund window and last payment data are shown in-app.
• Plan entitlements continue to apply even if the Billing menu is hidden.

Plan enforcement

• Feature access and numeric limits are enforced in both the UI and backend.
• Unsupported features are disabled before requests are sent where possible.
• Limit errors return specific plan, feature, and usage messages.

Plans and pricing

• Enable, disable, or delete plans with in-use protections.
• Bind Stripe price identifiers directly to plan definitions.
• Configure feature entitlements and numeric limits with unlimited support.

Workspace control

• Force a workspace onto another plan when needed.
• Audit plan overrides and workspace state.
• Review workspace owner email and effective limits.

Governance

• Approve domains.
• Review links, visits, audit logs, announcements, and configs.
• Control billing visibility without breaking active entitlement enforcement.