Quickstart: Launch Your First Campaign

The targeting section restricts who and what the discount applies to. Combine filters for precise reach:

Product targeting:

• Specific SKUs or product IDs
• Entire categories or collections
• Tag-based (new-arrival, clearance, summer-2026)
• Exclusion lists ("everything except gift cards")

Customer targeting:

• CRM segments (First-Time Buyers, VIP, At-Risk, Lapsed)
• Loyalty tier (Bronze and above, Gold only, etc.)
• Geographic (specific countries, states, or postal codes)
• Order-history filters ("3+ previous orders", "spent > $500 lifetime")
• Account age ("new accounts under 30 days")

Channel targeting:

• Web only, POS only, mobile-app only
• Specific store locations (multi-store retailers)
• API / third-party order sources

typescript // Example: VIP-only promotion for a specific category const promo = await aeion.api.post("/v1/discounts/promotions", { name: "VIP Spring Apparel", type: "percentage", value: 25, targeting: { customerSegments: ["vip", "platinum-loyalty"], productCategories: ["apparel", "footwear"], channels: ["web", "mobile"], }, startsAt: "2026-03-01T00:00:00Z", endsAt: "2026-03-31T23:59:59Z", });

Set start and end dates with minute precision. The engine auto-activates and auto-deactivates without manual intervention — no cron job for you to write.

Recurring schedules (e.g., "Happy Hour every Tuesday 2–5pm"):

typescript const happyHour = await aeion.api.post("/v1/discounts/promotions", { name: "Tuesday Happy Hour", type: "percentage", value: 15, schedule: { recurring: true, daysOfWeek: ["tuesday"], startTime: "14:00", endTime: "17:00", timezone: "America/Los_Angeles", }, });

Geo-aware activation — the timezone field above is per-customer, not per-tenant. A customer in Tokyo sees the happy-hour discount during their Tuesday 14:00–17:00 local; a customer in NYC sees it during theirs. No manual timezone math.

Automatic promotions — leave the code field empty. The engine evaluates eligibility on every checkout in real-time. Customer sees the discount applied at cart-line and checkout without entering anything.

Single-code promotions — set one human-friendly code. Good for marketing campaigns where the same code is broadcast to many customers.

typescript const broadcastCode = await aeion.api.post("/v1/discounts/promotions", { name: "Newsletter Launch", code: "WELCOME20", type: "percentage", value: 20, });

Bulk code generation — for influencer / affiliate / partner campaigns where you want unique tracking codes. Generate up to 10,000 codes in one call:

```typescript const partnerCampaign = await aeion.api.post("/v1/discounts/promotions", { name: "Influencer Q3 Campaign", type: "percentage", value: 15, codePrefix: "SUMMER-", generateCodes: 10000, usageLimitPerCustomer: 1, });

// Returns: { promotionId, codes: [{code, status, generatedAt, ...}], ... } // Each code is unique, single-use, and tracking-attributable ```

Codes are exported as CSV for partner distribution. Each redemption is logged with the redeeming customer, order, timestamp, and code — full attribution chain.

The Discounts Analytics dashboard (Admin → Commerce → Promotions → Analytics) surfaces:

• Redemption rate — code usage vs codes distributed
• Revenue impact — gross sales attributable to the promotion
• Margin impact — net effect on margin after discount
• Cohort behavior — do discount-users come back at full price?
• Per-code performance — for bulk campaigns, which influencer codes drove the most revenue
• Time-of-day patterns — when redemptions cluster (informs future scheduling)

Set up alerts to fire when:

• Redemption rate exceeds projection (you may have set the discount too aggressively)
• Margin impact crosses a threshold (cap your downside before damage is done)
• A specific code is being abused (e.g., 100+ redemptions on a code meant for one influencer's audience)

Cross-reference with CRM (Admin → CRM → Customer Segments) to see if the discount is attracting your target segment or being absorbed by existing high-value customers.