How to Send Push Notifications via TRIFFT and Bloomreach

Push notifications can be delivered either as topic pushes (same message to many) or one-to-one pushes (personalized per user). Each has its strengths — but also limitations and risks if not implemented correctly.

🔔 Two Types of Push Notifications

1. Topic Push Notifications

• Delivered via Google or Apple topic system.
• Same message to all recipients (e.g., "New deal on pasta!").
• Cannot include personalization (e.g., no {first_name}).
• Can be sent to TRIFFT segments (like "Pizza lovers", "Pasta lovers").
• Best sent through:
  • TRIFFT Content Cockpit (via segment)
  • Or directly from Bloomreach using webhook calls to segments (not device topics)

2. One-to-One Push Notifications

• Personalized per user (e.g., “Hi John, you’ve earned a new reward!”).
• Typically used for:
  • Transactional messages
  • Personalized marketing campaigns
• Sent from Bloomreach one-by-one via API (/v1/member/{uuid}/message/notification)
• Must be rate-limited and spread over time to avoid issues.

✅ Recommended Approaches

Option A: Use TRIFFT Segments with Topic Pushes

• Create segments in TRIFFT (can be filled via Bloomreach via webhook).
• Send one uniform message to the whole segment.
• Use when:
  • Message doesn’t need personalization.
  • You want to reach many people efficiently.
• Safe and stable: no risk of duplication, minimal rate limiting issues.

Option B: Use Bloomreach for Personalized Pushes (One-to-One)

• Send individually personalized messages from Bloomreach to TRIFFT via API.
• Use wait nodes or AB test cascades to spread the load gradually.
• Needed when:
  • Personalization (e.g., name, rewards) is required.
  • Timing of messages should vary.
• ⚠️ Must be handled carefully to avoid:
  • Google/Apple rate limiting
  • Message duplication
  • TRIFFT API overload

What Happens If You Blast Without Rate Limiting?

• TRIFFT API limits can be overwhelmed (especially with 100k+ recipients).
• Google or Apple may throttle delivery, resulting in:
  • Delayed or dropped pushes
  • Some users receiving multiple notifications
• Bloomreach may retry on its own, sending the same push multiple times.

✅ Best Practices Summary

🛡️ Preventative Controls

To keep pushes safe, reliable, and compliant:

• Use TRIFFT segments to group users logically.
• In Bloomreach:
  • Add wait times between push batches.
  • Use A/B test splits or cascaded branches to reduce load spikes.
• Use per-client API keys to track and isolate traffic.
• Avoid sending more than a few hundred personalized pushes per minute without coordination.

For technical setup assistance or troubleshooting, please contact the TRIFFT support team.