Glitnir Integration Use Cases

Use Cases

1. Event-Based Campaign Targeting

Purpose: Target buyers of upcoming games with reminders or offers.

• Trigger Field(s): EventID, EventStart, Email

• Action: Schedule automated reminder emails 3 and 1 day(s) before the game.

  • Create an audience as following

  

  • Create a campaign or a journey specific to the game and use the above segment

• Enhancement: Include dynamic content like weather forecast, opponent stats, or merch discounts.

2. Post-Game Follow-Up Automations

Purpose: Re-engage attendees after each game.

• Trigger Field(s): Attended = 1, EventID, Email

• Action: Send post-game survey or photo gallery.

• Value Add: Incentivize feedback with discount codes for future games.

3. Segmented Promotions Based on Ticket Type

Purpose: Personalize promotions to drive upsells.

• Trigger Field(s): PriceID, Seat, SectionID, OrderTotal

• Action: Send premium upgrade offers to General Admission buyers.

• Example: Send upgrade promotions to purchasers of “$12 G/A - Advanced” to “$16 Box Seat - Advanced” such as “Try a box seat next time for just $4 more.”

4. Identify and Nurture High-Value Fans

Purpose: Reward frequent or high-spending fans.

• Trigger Field(s): Email, OrderTotal, OrderID (grouped by UserID)

• Action: Add to VIP campaigns, early ticket access, or special rewards.

  • Create segment of buyers who bought multiple tickets for the same game

    
  • Create segment of buyers who bought tickets worth a premium value over multiple games

    
• Insight: Total spend over the season can feed into loyalty scoring.

5. Recover Missed Attendance

Purpose: Bring back no-shows or incomplete orders.

• Trigger Field(s): Attended = 0, Email

  
• Action: Send “We missed you” emails with future game coupons.

• Bonus: Can A/B test reminder emails vs SMS for future games.

6. Drive Referrals from Active Buyers

Purpose: Turn ticket buyers into promoters.

• Trigger Field(s): OrderDate, Email

• Action: After first-time purchase, offer “Bring a friend” incentive.

• Timing: Triggered within 48 hours of new OrderID.

7. Analyze and Optimize Campaign ROI

Purpose: Track impact of marketing campaigns on ticket sales.

• Trigger Field(s): OrderSource, OrderID, EventID

• Action: Map campaigns (email/SMS) to orders by source.

• Outcome: Focus budget on high-converting channels (e.g., Mobile Ticketing).