Frequently Asked Questions

Comprehensive FAQ covering product, technical, and business questions about Appizer - get answers to 50+ common questions.

Everything You Need to Know About Appizer

Product Questions

What is Appizer?

Q: What exactly does Appizer do?

Appizer is a smart layer on top of push notification and email platforms (WonderPush, Brevo) that automatically detects users who are about to leave your app and sends them personalized re-engagement messages.

Think of it as your AI marketing team that works 24/7 while you build your next version.

Why do I need Appizer?

Q: I can send push notifications manually. Why pay for another tool?

You could, but:

  • Time: Manual campaigns take hours; Appizer = minutes
  • Data: You need to understand who to send to; Appizer handles segmentation
  • Copy: Manually writing messages is slow; Appizer generates them with AI
  • Frequency: Figuring out when to send requires testing; Appizer automates it
  • Results: Most manually-sent campaigns get <5% open rates; Appizer's get 15-25%

Real example: A solo developer spending 1 hour/week on re-engagement could use Appizer instead and save 50 hours/year.

Is Appizer a competitor to WonderPush/Brevo?

Q: Do I have to replace my current push/email platform?

No. Appizer complements WonderPush and Brevo, not replaces them. You still need WonderPush (or similar) to actually send the notifications. Appizer just makes them smarter.

Think of it like this:

  • WonderPush = The truck that delivers your packages
  • Appizer = The GPS that decides where to send packages based on customer behavior

What platforms does Appizer work with?

Q: Does Appizer work with my app built in [platform]?

Appizer works with any platform that:

  1. Can track events (user actions)
  2. Can use REST APIs
  3. Can integrate with WonderPush/Brevo

Specifically optimized for:

  • No-code builders: v0, Bolt, Windsurf, Lovable, Replit, Cursor
  • Frameworks: React, Vue, Next.js, Flutter, React Native
  • Backends: Node.js, Python, Go, any language with HTTP support

If you can send an HTTP request and track a user ID, Appizer works.

How much does Appizer cost?

Q: Is Appizer free?

Appizer pricing is designed to be affordable for vibe coders:

  • WonderPush: ~$1/month per 1,000 subscribers (their pricing)
  • Appizer: Pricing optimized for bootstrapped makers

Our goal is to keep Appizer affordable for solo makers (unlike expensive enterprise platforms at $500+/month).

Total estimated cost: ~$10-50/month for early-stage apps

Do I need to be technical to use Appizer?

Q: I'm not a developer. Can I use Appizer?

It depends on your app setup:

  • If developer built your app: Yes, they can integrate Appizer in 30 minutes
  • If you used a no-code builder (v0, Bolt, etc.): Yes, agentic integration (copy-paste prompts) handles it
  • If you need WonderPush integrated: You'll need someone technical OR use agentic IDE to automate it

Once set up, the Appizer dashboard is designed for non-technical people—no SQL or code required.

Technical Questions

Integration

Q: How long does integration take?

Answer: 30-45 minutes total:

  • Account setup + WonderPush connection: 5 min
  • Event tracking integration: 15-20 min (faster if using agentic prompts)
  • Create first campaign: 5-10 min

Or: 5-10 minutes if you use agentic IDE integration (copy-paste prompt).

Q: Do I need to install the Appizer SDK?

Answer: Not exactly. You need:

  1. WonderPush SDK (for push notifications)
  2. HTTP client (to send events to Appizer)

We don't have a separate Appizer SDK; we use REST API. This keeps it lightweight and works with any platform.

Q: What events should I track?

Answer: Minimum recommended:

  • page_view - User navigated to page
  • app_open - App launched
  • button_click - User interacted with UI
  • form_submit - User submitted form/action
  • conversion - User completed desired action (purchase, signup, etc.)

Domain-specific (optional):

  • Games: level_complete, achievement_unlock, tutorial_start
  • SaaS: feature_used, payment_processed, upgrade
  • E-commerce: product_view, add_to_cart, purchase

Q: How often should I send events?

Answer: Send an event every time a significant action happens. Examples:

  • ✅ User opens page: 1 event
  • ✅ User clicks play button: 1 event
  • ✅ User completes level: 1 event
  • ❌ User moves mouse: Don't track (too granular)
  • ❌ User's position updates: Track sparingly (maybe every 30 seconds)

Goal: 10-50 events per user per day. Too few (0-5) = can't segment; Too many (1000+) = noise.

Q: What if users don't consent to tracking?

Answer: Event tracking is separate from push notifications. Best practice:

  1. User installs app → Ask for analytics permission (GDPR, privacy laws)
  2. If consent: Track events
  3. If no consent: Don't track

This is between you, your users, and privacy laws (GDPR, CCPA, etc.). Appizer stores what you send—ensure you have consent first.

Segmentation & Audiences

Q: How detailed can I get with audience segments?

Answer: Appizer supports:

  • Event-based: Users who completed X event in last Y days
  • Property-based: Users where event property (e.g., score >1000)
  • Time-based: Users seen in last X hours/days/months
  • Complex logic: AND/OR combinations of above

Currently limited to single criteria (coming: advanced boolean logic).

Q: Can I create overlapping audiences?

Answer: Yes. Example:

  • Audience 1: "Users inactive 3 days" (100 users)
  • Audience 2: "Users inactive 3 days AND played >5 games" (25 users)
  • Audience 3: "Users inactive 3 days AND never played" (75 users)

All three can exist and be used in different campaigns.

Q: How often are audiences updated?

Answer: Continuously. Appizer re-evaluates audiences every 10 minutes, so changes (new events, user status changes) are reflected within 10 minutes.

Campaigns

Q: Can I schedule campaigns for specific times?

Answer: Yes:

  • Immediate: Send now
  • Scheduled: Send at specific date/time
  • Recurring: Send daily/weekly/hourly
  • Event-triggered: Send immediately after user event

Q: What's the character limit for push messages?

Answer: Typically 240 characters (varies slightly by platform). Appizer alerts if you exceed platform limits.

Q: Can I include links/deeplinks in push messages?

Answer: Yes. When user taps message, you can:

  • Open a website URL
  • Open your app (deeplink)
  • Open app to specific screen

Q: Can I A/B test messages?

Answer:

  • Currently: Create 2 identical campaigns with different copy, compare metrics
  • Planned: Native A/B testing feature (coming soon)

Q: What happens if a user is in multiple campaigns?

Answer: Both campaigns send. Frequency cap applies across all campaigns:

  • Default: Max 3 messages per user per day
  • Configurable: Set per campaign

Q: How do I track if a push notification worked?

Answer: Appizer shows:

  • Send: Number of messages sent
  • Delivery: % successfully delivered (via WonderPush)
  • Open: % users opened (tracked by WonderPush)
  • Click: % users clicked action URL
  • Conversions: Downstream actions (if tracked)

Analytics

Q: How long are events stored?

Answer: Default: 90 days. Extended retention coming.

Q: Can I export event data?

Answer: Currently: Dashboard view and screenshot. Export feature (CSV/JSON) coming soon.

Q: Does Appizer work with Google Analytics?

Answer: Currently separate systems. Roadmap includes:

  • Google Analytics integration (events sync)
  • Mixpanel integration
  • Custom analytics integrations

For now, track in both Appizer and GA separately.

Q: Why is my open rate so low (<10%)?

Answer: Common reasons:

  1. Push permission not granted - Confirm permission request works
  2. Bad message copy - Generic messages don't compel opens
  3. Wrong timing - Sending at 2 AM? Try 9 AM
  4. Wrong audience - Irrelevant messages to wrong users
  5. Frequency fatigue - Too many pushes = users ignore
  6. Device issues - iOS vs Android behavior differs

Solutions:

  • A/B test message copy
  • Test different send times
  • Refine audience targeting
  • Reduce send frequency
  • Use AI-generated messages (usually perform better)

Best Practices

Event Tracking Best Practices

Q: What's the best way to structure event names?

Answer: Use snake_case, be specific:

  • ✅ level_complete (specific)
  • ✅ achievement_unlock_gold_medal (very specific)
  • ❌ event_123 (vague)
  • ❌ user_action (too generic)

Pattern: [entity]_[action] or [action]_[object]

Examples:

  • user_signup
  • game_level_complete
  • video_play
  • purchase_complete

Q: Should I track every click or just important ones?

Answer: Track important user actions, not every interaction:

  • ✅ Track: Button clicks that lead to conversions
  • ❌ Don't track: Mouse movements, page scrolls, every keystroke

Think: "Would I want to segment users on this action?" If no, don't track.

Campaign Best Practices

Q: How often should I send re-engagement campaigns?

Answer: Depends on your app type:

  • Games: 1x per day (high engagement)
  • SaaS: 3-4x per week (avoid fatigue)
  • Social: 2x per week (personalization important)

Frequency cap: Set max 3-5 messages per day to avoid annoying users.

Q: What's the best time to send push notifications?

Answer: Generally:

  • Mornings: 8-10 AM (commute time)
  • Lunches: 12-1 PM (break time)
  • Evenings: 6-8 PM (downtime)

Best practice: A/B test on your user base. Gaming apps = different optimal time than finance apps.

Q: Should I personalize push messages?

Answer: Yes, but level depends on your app:

Minimum (Template):

"Hey {{user.name}}, you earned {{points}} points!"

Medium (AI-generated):

"You completed 5 levels! Ready for hard mode? 🎯"

Advanced (Agentic):

AI generates entirely unique message based on user history + app context

AI-generated consistently outperforms generic copy (15-25% open rate vs 5-10%).

Troubleshooting Best Practices

Q: My events aren't showing up. Where do I start debugging?

Answer: Follow this order:

  1. Check DevTools Network: Are requests reaching api.appizer.com?
  2. Check API key: Is it correct in your code?
  3. Check user ID: Is it consistent across all calls?
  4. Check timestamp: Is it valid ISO format?
  5. Check response: Is it 200 OK or 400+ error?
  6. Wait 30 seconds: Slight delay in dashboard update

Platform-Specific Questions

v0.dev

Q: Can I integrate Appizer directly in v0?

Answer: Yes, via agentic prompt (copy-paste into v0's AI chat). The AI generates integration code automatically.

Windsurf

Q: Does Appizer work with Windsurf's agentic features?

Answer: Yes. Use Windsurf's built-in agentic commands (/edit, /run) to implement integration.

Bolt

Q: Can Appizer work with Bolt's full-stack setup?

Answer: Yes. Implement event tracking in frontend (user actions) and optionally in backend (server-side events).

Account & Billing

Q: How do I change my app's name or delete an app?

Answer: Go to app settings:

  • Edit: App name, description, URLs
  • Delete: Scroll to bottom, "Delete App" button

Warning: Deleting app deletes all data. No recovery possible.

Q: Can I have multiple apps in one Appizer account?

Answer: Yes. Each app is separate:

  • Own events
  • Own audiences
  • Own campaigns
  • Shared settings (billing, profile)

Q: How do I upgrade or downgrade my plan?

Answer: Contact support for plan adjustments.

Community & Support

Q: Is there an Appizer community or Discord?

Answer: Coming soon. For now, ask questions:

Q: Can I contribute to Appizer development?

Answer: Feedback yes! For feedback:

Advanced Questions

Webhook Pass-Through

Q: How do I use webhook pass-through?

Answer: Configure in app settings:

  1. Enter external webhook URL
  2. Appizer forwards all (or filtered) events to that URL
  3. Your system receives same event data as Appizer API

Use cases:

  • Forward to Zapier
  • Send to custom backend
  • Sync with Mixpanel/Segment

Email Campaigns

Q: Can I send email campaigns with Appizer?

Answer: Yes, if you connect Brevo. Same workflow as push campaigns.

Brevo integration is optional (not required for v1).

Roadmap Questions

Q: When will feature X be available?

Answer: Currently planned:

  • SMS campaigns (Q1 2026)
  • In-app messaging (Q1 2026)
  • Advanced A/B testing (Q2 2026)
  • OneSignal integration (Q2 2026)
  • Predictive churn scoring (Q3 2026)

Q: Can you integrate with [platform]?

Answer: Possible. Currently focused on WonderPush + Brevo. For requests, email roadmap@appizer.com.

Feedback & Feature Requests

Q: How do I request a feature?

Answer: Email feature-request@appizer.com with:

  • What problem it solves
  • How you'd use it
  • Why it matters for your use case

Q: Where can I report a bug?

Answer: Email support@appizer.com with:

  • What happened
  • Steps to reproduce
  • Expected vs actual behavior
  • Screenshots/logs

Getting Help

Still have questions?

Getting Help

Still have questions? Start here:

Need direct support?

Previous
Troubleshooting
Next
Community