Skip to main content

​
Campaigns, Links, and Rules

Campaigns define economics and structure. Links deliver traffic. Rules personalize routing.

​
End-to-end operating flow

  1. Create campaign with cost model and currency.
  2. Create links and assign them to campaign/folders/tags.
  3. Attach rules to links in explicit priority order.
  4. Configure deep links, tracking, and security controls.
  5. Validate behavior in link and campaign analytics.

​
Campaign setup

A campaign should define:
  • objective and naming convention
  • cost model and reporting currency
  • ownership and lifecycle status
Typical campaign statuses:
  • active
  • paused
  • archived
Campaign-level tracking choices affect downstream conversion and analytics visibility. Each link should define:
  • destination and fallback behavior
  • campaign assignment
  • tags/folders/UTM pattern
  • lifecycle controls (expiry, password, click limits)
Link settings commonly used by operators:
  • slug/short-code customization
  • title/label conventions for reporting
  • access controls (password-protected links)
  • expiration and archival behavior
  • click-limit protection for capped promotions
Common link creation/editing surfaces include:
  • Basic: destination, slug, domain, metadata
  • Rules: attach and order routing rules
  • Advanced: security, tracking, attribution, UTM, deep-link options
  • QR: generate and manage QR assets
Domain choices commonly include system domains and verified custom domains.

​
Rule behavior

Rules are evaluated by priority and specificity. Good practice:
  • keep highest-confidence rules at top
  • use explicit fallback rule
  • avoid overlapping broad rules that mask precise targeting
When combining multiple rules:
  • start from narrow conditions and expand outward
  • keep one unambiguous default destination
  • validate priority order after each rule edit
Rule attachment behavior:
  • a link can have multiple rules attached
  • priority determines evaluation order
  • broad fallback rules should be last

​
Rule targeting dimensions

Supported targeting dimensions include:
  • geography
  • device and platform signals
  • browser and OS
  • referrer and source attributes
  • query and request attributes
  • time windows and quality/fraud signals
Rules can also combine nested condition groups for advanced targeting logic. For app journeys:
  • define platform-specific deep-link targets
  • ensure web fallback exists
  • test routing under unsupported device/app cases
Enable deep linking only when at least one platform/fallback target is valid. If in-app browser breakout is enabled, validate behavior in major social in-app browsers.

​
QR and offline acquisition

For QR use cases:
  • use campaign-specific QR tracking
  • validate destination behavior for scan contexts
  • monitor QR-specific analytics views
QR operations typically include:
  • generate code assets per link
  • select visual style and format
  • download for print/web usage
  • monitor scans and unique scans in analytics

​
Organization controls (Tags, Folders, UTM)

Use these together for clean operations:
  • Tags: campaign semantics and segmentation labels
  • Folders: ownership and access organization
  • UTM templates: consistent attribution parameters at scale
This combination improves filtering, exports, and cross-team governance. Frequently used controls:
  • password protection
  • expiration date/time
  • expired-target URL
  • click limits
  • archive/unarchive behavior
These controls directly affect redirect outcomes and should be reviewed before high-traffic launch.

​
Cost and tracking alignment

Campaign sets default economics; links may override in selective cases. Practical guidance:
  • avoid unnecessary per-link cost overrides
  • keep conversion tracking enabled where revenue attribution is required
  • align UTM and external IDs with CRM/BI conventions
  1. Confirm campaign cost model and currency.
  2. Confirm each link destination/fallback/domain.
  3. Validate rule order and fallback catch-all behavior.
  4. Validate deep-link and QR behavior (if enabled).
  5. Send test clicks/conversions before going live.
Related:
  • /user-guides/manual/monetization/currencies-cost-models-and-fx
  • /user-guides/manual/data/analytics-and-reporting
  • /user-guides/manual/growth/tags-folders-utm-reference