Performance, stability and long-term support - rolling out to every campaign type

What's Happening

We're in the middle of upgrading the engine behind all 50+ campaign types. Think of it as giving your campaigns fresh suspension and new tires: smoother rides for fans, easier handling for you:

This rollout (August - October 2025) is all about

• More stable, maintainable code
• Faster load speeds
• Compatibility with what's next (Offline campaigns + New campaign editor)

Check out the live rollout status below 👇

Big Updates #1
Entry forms at the beginning of MOST Campaigns

As our single-page campaign updates roll out, you’ll notice that most transitioned engagement campaigns now begin with the entry form. Many of you have shared that you prefer the form after the activity - especially when you’re shaping a fan flow or brand moment - and that feedback is completely valid.

Here's the reason for that change

• Starting with the entry form gives us a consistent structure that is more stable, less buggy, and supports the direction of new features we're building post single-page refactoring
• Cleaner data: Fewer half-finished entries that never tie back to a profile
• Consistency: Fans know exactly what to expect, whether they're playing trivia or building dream teams

To understand how this impacts campaign performance, we’ve been comparing campaign entry rates before and after the shift for live campaigns. In our Dream Team rollout, entry rates increased between 13% and 43.5% after rollout, meaning more fans who opened the campaign actually gave their first-party data and completed it with the entry form at the beginning.

This isn’t a permanent design decision - it’s a foundational step as we modernize our campaigns. We’ll keep monitoring the impact as more campaign types move over. 

In the meantime, we’re here to help you create engagement campaign flows that feel smooth, intentional and on-brand. Here are some quick workarounds:

1. Use Tradable Bits Auth on your campaign instead. One login = 6 months of session persistence, so fans don't have to re-enter details every time.
   
   
2. Keep the form as short as possible, being strategic about what you're asking for. 
   
   
3. Toggle off "PII collection" and add a link to an entry form on the last page of the campaign (we recommend discussing this option with your CSM before implementing).

Big Updates #2
Lineup Campaign has a fresh look

The classic carousel has retired. Say hello to deck-style cards.

Fans now swipe through a stack to lock in their picks. On mobile, it's faster, bolder and more aligned with today's swipe habits.

Why the switch?

• Mobile-first: smoother gestures

We know change takes adjusting - some of you loved the carousel. This is step one in evolving layouts, and your feedback will shape where we go next.

👉 Next Step:  Preview your Lineup Campaign and let us know how it feels on mobile! Like it? Hate it? Tell us at support@tradablebits.com 

Big Updates #3
Dream Team has a new, mobile-first roster UI

Dream Team now uses the same "deck-style swipe UI as Lineup - replacing the classic full-roster grid of player photos. 

Why the switch?
Because the majority of Dream Team entries happen on mobile, and the old grid made fans pinch, zoom, scroll and hunt. The new stack-style swiping is:

• Faster - one tap to swipe through players
• Cleaner - no long-load grids or layout shifts
• More modern - mirrors the swipe patterns fans use everywhere else (TikTok, IG, Tinder-style carosels).

Once fans lock in their picks, the same positional sorting and team breakdowns still appear just like before.

👉 Next Step:  Preview your Dream Team on mobile and let us know how it feels.  Love it? Hate it? Drop us a note at support@tradablebits.com 

📅 Rollout Status

What's Changing?

 Each campaign type is getting upgraded under the hood, including:

• Entry forms come first
• Routing updates (e.g. tb_app replacing thank_you)
• Class name structure improvements
• More reliable state transitions between campaign views
• Small adjustments to UI

⚠️ If you've added custom JS, CSS or scripts to the thank you page of your campaign, please check the following for campaign-specific updates:

• You rely on page routes (like /thank_you/) for your custom JS/CSS
• You've added custom code for pixel fires on the thank you page
• You've written logic that assumes a full redirect

An example of impact: 

Before: your sweepstakes showed a separate "thank you" page (at /thank_you/) to fire a conversion pixel.

Now: the same "thank you" state appears within the same route (/tb_app), so any script tied to /thank_you/ won't fire unless updated.

What TBits is doing on every deploy

Behind the scenes, we're

1. Running QA for each campaign type
2. Reviewing the live campaigns with custom JS on deploy
3. Flagging edge-case issues to our Solutions Engineering team for fast handling

What you should do:

Most partners don't have to take any action. However, if you've deployed custom tracking, custom layouts, or specialized CSS/JS on your campaigns, here's your QA checklist:

✅ Load campaign and walk through it as a user
✅ Confirm expected styles and transitions
✅ Check if any custom scripts are firing correctly

👉 Need help? support@tradablebits.com 

What if I experience a bug?

Reach out via your shared slack channel and/or contact support@tradablebits.com with the following:

• A short description of what's happening vs expected behaviour
• The campaign ID and impacted functionality

How will I know when a deploy is live?

You'll be notified:

• With an in-app notification on the platform 
• You'll receive a deploy update in your shared Slack channel
• On this page (updated status: "✅ Done!")