FAQ: Everything You’ll Ask Before and During Launch

This is a practical, straight-to-the-point FAQ that you can hand to PMMs, growth, and engineering, so teams can move quickly without guesswork.

What Do We Need to Do for Integration?

1. Which Developers Are Required?

Mobile dev(s): SDK setup and deep links.
Backend dev: server events (payments/subscriptions), ID matching.
PMM/Growth: templates, segments, workflow logic.
(Optional) Data/Analytics: exports and BI wiring.

2. How Much Dev Time Will We Need?

Typical MVP: 2–5 dev-days (mobile) + 2–4 dev-days (backend). Add 2–4 days for advanced integrations/extra events. (Exact effort varies by app complexity.)

3. Channel Setup: Push SDK, Email DNS & Warm-up

Push/In-App: add SDK, handle deep links, and create notifications.
Email: configure SPF, DKIM, and DMARC; set a branded tracking domain; warm up with transactional first. Use Postmaster Tools to monitor reputation. Details >

4. Contact Import & Identifiers

Import via CSV/API; include fields you’ll actually segment on. Use a stable user_id, plus device_id, email, locale, platform, and consent flags. Details >

Stable external ID reference: external ID for creating and updating users

5. Which Events Must We Send?

Events sent via SDK include data about user’s in-app actions. Examples:

LessonStarted / LessonCompleted
GoalSet / GoalAchieved
HealthMetricsRecorded
SleepTracked
SearchPerformed

Backend API events usually carry sensitive data or require server-side validation. Examples:

AccountCreated
UserUpdated (changes in user profile information that are managed server-side)
SubscriptionStarted / SubscriptionRenewed / SubscriptionUpdated / SubscriptionCanceled
PaymentCompleted / PaymentFailed
ReferralInviteAccepted

Read the Planning Event Tracking guide >

Do You Have Similar Examples?

Yes — subscription apps (e.g., Health & Fitness, Education) commonly follow the same priority ladder and see the fastest lift with Abandoned Subscription + Activation.

See use cases >

How Do We Create Workflows, Segments, and Messages?

Workflows: choose trigger type, audience, timing, and stop rules.
Segments are built from events, contact fields, and message activity.
Email / Mobile Push / In-App: use editors to add placeholders and deep links.

How Do We Analyze Results & Export to Other Systems?

Utilize built-in analytics for sends/opens/clicks/conversions. Export data to BI or connected tools via BigQuery and API.

Integrations with Other Services

Connect analytics and apps to automate data flow and trigger campaigns.

For Amplitude, create destinations to stream anonymous IDs, enrich profiles, and pass events into Reteno—so you can segment and launch event-based workflows without custom piping.
For other integrations, use Zapier to sync tools fast.

Availability of Certain Features

1. How to Run A/B Tests?

Use workflow-level A/B testing or the One from many message block. Create variants (subject/copy/timing), set the traffic split, define the winning metric, and launch. Reteno records the results and lets you roll out the winner.

2. How to Launch a Triggered Campaign by Event?

Set up a workflow that starts automatically when a specific event occurs (e.g., SubscriptionCreated, AppOpened). Define the trigger event, configure start/stop conditions, and design the message flow that follows it.

Read the full guide >

3. How to Send a Campaign to a Segment?

Use a regular workflow to send messages to a targeted audience segment. Select the segment, set up the sending schedule or conditions, and customize message content.

Read the full guide >

4. How to Work with Multiple Languages?

Enable the Multilanguage feature to manage content for different locales within a single campaign. Add translations, and Reteno will send each contact the correct language version.

Read the full guide >

Pricing — What Drives It?

User profiles (contacts) are the main driver. Plans scale based on the number of profiles you store, not by per-message fees.

Startup (Free): unlimited mobile pushes, 1,000 sends per channel/month, and 20,000 workflow launches/month to get going.
Growth: $30/month up to 10,000 profiles, then roughly $3 per 1,000 profiles from 10K to 250K; includes unlimited workflows across 8 channels and a dedicated Customer Success Manager.
Enterprise: custom pricing for larger datasets and advanced needs; everything in Growth plus enterprise-level options.

Paid plans are all-inclusive (unlimited features/channels); the free plan still includes event-triggered journeys.

Details >

Pros/Cons vs Competitors

See the side-by-side with Braze: free plan with journeys and all channels, simple all-inclusive packages, and unlimited pushes — versus tiered feature/data allotments and no free trial on the competitor side. Use this page to position pricing and time-to-value.

Migration from a Current Provider

Follow the migration guide: transfer account settings, import contacts and activity (CSV/API), move segments and templates, and run a short parallel period before cutover.

Reteno’s team helps ensure data accuracy and minimize downtime.

Support & Customer Success

Full-service assistance on eligible plans — from strategy design and SDK onboarding to ongoing help with deliverability, SDK version updates, and message design.

What If Email Reputation Drops?

Pause broad sends; keep transactional only.
Reduce frequency, suppress inactive users, and resolve acquisition issues.
Monitor Postmaster Tools; ramp back gradually after recovery.

Details >

What If Reminders Increase Cancel Rate?

Timing: send at the user’s habitual usage time; avoid early mornings by default.
Cadence: cap to ≤3 pushes/week (or less) and test a weekly digest email instead of daily pings.
Message framing: swap guilt/urgency for positive, progress-oriented copy with a single action.
Audience: exclude users with recent frustration signals (PaymentFailed, support tickets, low NPS).
Channel mix: prefer in-app prompts on return rather than off-app nudges to cold users.