NEW! Calculate your revenue uplift with our Value Calculator

ContextSDK Guide

Everything you need, all in one place! Whether you're curious about ContextSDK, need a quick term lookup, or want to optimize engagement, this guide has you covered.

What makes ContextSDK different from other engagement tools?

Unlike traditional tools that rely on rigid rules or time-based triggers, ContextSDK uses machine learning and real-world signals (like activity or device usage) to adapt dynamically to user behavior. This ensures your prompts are sent at the optimal moment, maximizing engagement and reducing user fatigue.

How does ContextSDK ensure user privacy?

ContextSDK takes privacy seriously and is built with a privacy-first approach:

  • On-Device Processing: All data processing happens locally on the user’s device, ensuring that no Personally Identifiable Information (PII) is stored, transferred, or shared.
  • Privacy Compliance: Our technology adheres to global privacy standards, including GDPR, CCPA, and other key regulations.
  • SOC 2 Certification: ContextSDK is SOC 2 certified, which means our platform meets stringent security, availability, and confidentiality requirements. This certification demonstrates our commitment to maintaining the highest standards of data security and privacy.

How long does it take to integrate ContextSDK into my app?

Integration is simple and quick. ContextSDK is designed to work seamlessly with your existing push providers and analytics tools. Most apps can complete integration in just a few days, with minimal impact on codebase and resources.

Do I need to make changes to my app design for ContextSDK to work?

Not at all. ContextSDK integrates seamlessly into your existing workflows, requiring just a few API calls to enable smarter, context-aware prompts. You’ll retain full control over your app’s design and user experience.

How much historical data do I need to get started?

To get started, ContextSDK requires the following:

  • Insights for the Dashboard: A minimum of 10,000 logged events is needed for the dashboard to generate actionable insights. For larger apps, this can take a day, while smaller apps may need longer.
  • Custom Model Training for Decision: At least 1,000 positive conversion events are required to train a tailored machine learning model for precise decision-making. We typically work with apps that have 100,000+ monthly active users to ensure faster model adaptation and impactful results

Can ContextSDK integrate with my existing tech stack?

Yes! ContextSDK is designed to integrate seamlessly with your existing push notification providers, analytics tools, and backend systems. This ensures smooth implementation with minimal disruption to your current workflows.

What specific user signals does ContextSDK analyze?

ContextSDK processes over 200 real-world signals, all analyzed directly on the user’s device to maintain strict privacy standards. These signals include:

  • Device usage: Screen time, app activity, and battery status.
  • Activity level: Whether a user is stationary, walking, or engaging in active movement.
  • Environmental context: Time of day, ambient light, and device orientation.
  • Motion patterns: Signals from gyroscopes and accelerometers to detect movement trends.

These insights are used by our machine learning models to determine the most relevant timing for notifications, paywalls, or offers - maximizing engagement without user fatigue.

Does ContextSDK work offline?

Yes! Since our AI models run entirely on-device, ContextSDK continues to function even when users are offline. No need to rely on cloud-based decision-making - everything happens in real-time on the user’s device.

Does ContextSDK increase battery usage?

Nope! Our on-device AI is optimized for efficiency. Since all processing happens locally, ContextSDK has minimal impact on battery life compared to cloud-based alternatives.

Can ContextSDK help reduce app uninstalls?

Yes! Poorly timed engagement often leads to user frustration and churn. By delivering messages at the right time, ContextSDK helps reduce spammy interactions and enhances user retention.

Can I test ContextSDK before fully implementing it?

Yes! We recommend running an A/B test to compare ContextSDK’s impact on engagement and conversions against your current setup. Our flexible integration allows for easy experimentation before full rollout.

How does ContextSDK handle updates and improvements?

Our models continuously learn and improve based on real-world interactions, ensuring they stay optimized for engagement and conversions. Plus, ContextSDK supports over-the-air (OTA) updates, meaning improvements and new features roll out seamlessly - no manual app updates required.

Can ContextPush work with any push provider?

Yes! ContextPush seamlessly integrates with all major push notification providers. You don’t need to switch platforms - just enhance your existing setup with smarter, context-aware delivery.

Which types of push notifications can be optimized by ContextPush?

ContextPush optimizes only non-transactional messages, such as promotions, reminders, or engagement campaigns. These are timed perfectly based on your users’ real-world context. Transactional messages - like order confirmations or password resets - that need to be sent immediately are unaffected and will continue to be delivered in real-time.

How does ContextPush work?

ContextPush uses the accelerometer, gyroscope, and other on-device signals from your users’ smartphones to predict their current context - whether they’re walking, sitting, or commuting. Based on this data, we time your non-transactional notifications to be sent at the perfect moment, increasing engagement. All of this is done without processing any PII (Personally Identifiable Information).

Does ContextPush need any app permissions?

ContextPush requires users to accept the standard push notification permission request in order to send notifications. Beyond that, no additional permissions are needed, as we work with data that is already available to your app.

What is ContextDecision, and how does it work?

ContextDecision is an AI-powered decision engine that helps apps determine the best moment to show in-app offers, paywalls, or engagement prompts. It analyzes over 200 real-world signals directly on a user’s device - such as motion patterns, device activity, and time of day - to ensure offers appear only when users are most receptive.

How is ContextDecision different from time-based engagement triggers?

Traditional engagement tools rely on fixed schedules or simple behavioral rules, often leading to poorly timed prompts and user frustration. ContextDecision adapts in real-time, detecting when a user is actively engaged and ready to convert - leading to higher engagement and better retention.

How does ContextDecision improve user engagement and conversions?

ContextDecision ensures offers don’t interrupt users at the wrong time, such as when they are walking, commuting, or in a hurry. By increasing offer frequency only at the best moments, apps experience:

  • Higher conversion rates  -  Users see offers when they are most likely to convert.
  • Less user fatigue  -  Avoid overwhelming users with untimely prompts.
  • Better retention  -  A smoother, more natural user experience.

Does ContextDecision require a lot of historical data to work?

No! ContextDecision starts working immediately but improves over time:

  • Dashboard Insights  -  Needs at least 10,000 logged events for optimal analytics.
  • AI Model Training  -  Needs 1,000 conversion events for custom model optimization.
  • Better retention  -  A smoother, more natural user experience.

For best results, apps with 100,000+ monthly active users generate meaningful engagement patterns quickly.

What types of apps benefit from ContextDecision?

ContextDecision is ideal for any app looking to improve engagement and monetization, including:

  • Gaming  -  Showing in-app purchase prompts at the right time.
  • Health & Fitness  -  Encouraging users to complete workouts.
  • Education  -  Surfacing learning content when users are focused.
  • Social & Dating Apps  -  Re-engaging users when they’re in the right mindset.
  • Finance & Subscriptions  -  Nudging users at key decision points.
  • Finance & Subscriptions  -  Nudging users at key decision points.

Does ContextDecision require changes to my app’s UI/UX?

No. Your app’s design and user experience remain unchanged. ContextDecision works in the background, making engagement smarter while you retain full control over how offers appear.

Can I test ContextDecision before fully implementing it?

Yes. We recommend running an A/B test to compare context-driven engagement with your current setup. Our team will help set up experiments to provide clear performance insights.

How do I track the success of ContextDecision?

We provide controlled experiments to measure impact on conversions, retention, and revenue. A dedicated dashboard is in development to track results in real time.

Is ContextDecision privacy-friendly?

Yes. ContextDecision is built with privacy in mind:

  • On-device processing  -  No data leaves the user’s phone.
  • No personal data collected  -  We only track engagement signals.
  • Education  -  Surfacing learning content when users are focused.
  • GDPR & CCPA compliant -  Fully aligned with global privacy standards.
  • SOC 2 certified -  Meeting high security and privacy standards.

What kind of ROI can I expect from ContextDecision?

Apps using ContextDecision have seen conversion boosts of up to 81% with fewer prompts, leading to:

  • Higher revenue per user (ARPU)
  • Better lifetime value (LTV)
  • Reduced churn from unnecessary engagement

What kind of support do you provide?

We offer dedicated support throughout integration and beyond, including:

  • Technical guidance for smooth implementation
  • Strategy consulting to optimize engagement workflows
  • Performance monitoring to fine-tune results

A

A/B Test Split

We split users into Control Group (your app’s usual flow) and ContextSDK Group (with optimized timing). This shows how ContextSDK impacts performance.

Active User

A user who opens your app and triggers at least one event during a given period (e.g., daily, weekly, monthly). ContextSDK works best with apps that have high active user volume, as more data = better models.

B

Baseline

Your app’s original performance without ContextSDK. Used as a comparison point in A/B tests to measure uplift and improvement.

Behavioral Signal

Any user interaction or pattern (e.g. session length, scroll speed) that helps ContextSDK infer intent or readiness to act.

C

Calibration Phase

When ContextSDK starts, it gathers data until it’s confident about when to show prompts. Once ready, it optimizes timing.

Chance-Initiated Flows

Prompts triggered by the app (not by user clicks). ContextSDK optimizes whether to show them.

Control Group

Users who experience your app as it was before ContextSDK - your baseline for comparison.

Conversion Rate

The percentage of users who complete a desired action (buy, subscribe, sign up) after seeing a prompt.

Custom Signal

Specific app data you share with ContextSDK (like session length or activity) to help improve decisions.

D

Deployment

The process of rolling out a trained model to your app. ContextSDK supports over-the-air (OTA) deployment for fast, flexible updates.

E

Entry Point

A moment where your app can show a prompt, like an upsell or push.

Event

Any user moment you track (like opening the app, finishing a level). We capture these to understand context.

Experiment (or Project)

A test you run to improve one flow (e.g., push timing, paywalls). Each project has its own model.

F

Flow

A specific part of your app where timing matters. Each flow tracks outcomes (good/bad) to improve results.

G

Goal Metric

The primary outcome you’re optimizing for in a ContextSDK experiment - e.g., purchase rate, feature adoption, or opt-in rate.

Granular Timing

The precision with which ContextSDK can evaluate and act on micro-moments throughout a user’s session (e.g., just after finishing a task).

H

High Intent Moments

A point in time when users are most likely to act (e.g. subscribe, purchase). ContextSDK detects these moments in real time.

I

Idle Session

A session with low interaction or passive usage. Recognizing these helps ContextSDK avoid poorly-timed prompts.

J

Journey Stage

The user’s current position in your funnel (e.g., onboarding, post-purchase). ContextSDK adapts decisions based on where users are in their journey.

K

Knowledge Center

Our hub for documentation, FAQs, and tips in our dashboard to make the most of ContextSDK.

L

Lifetime Value (LTV)

The total revenue a user brings over their entire time using the app.

M

Model

Our AI’s decision engine, trained on your app’s data to find the best moments for prompts.

N

Negative Outcome

A missed opportunity - when a user ignores, skips, or closes a prompt. Used to train models on what not to do.

O

On-Device AI

Machine learning that runs directly on the user’s device - no cloud needed. It enables ContextSDK to detect real-world context (like motion or screen state) and make instant engagement decisions, all while keeping user data private.

Opt-Out Rate (Push or Prompts)

The percentage of users who disable push notifications or close prompts too often.

Why it matters: Bad timing leads to higher opt-out rates. ContextSDK reduces this by sending fewer but better-timed prompts.

Outcome

What you want from a user:

Positive Outcome: Success (purchase, sign-up)

Negative Outcome: Rejected the prompt (closed, skipped)

Over-the-air Deployment (OTA)

A way to deliver updated machine learning models to your app without going through App Store or Play Store approval.

Why it matters: OTA lets you improve performance and iterate faster - new models are pushed directly to users’ devices, safely and instantly. No app update required.

P

Project

A specific optimization goal (e.g., post-onboarding upsell). Each project includes flows and models.

Prompt Intensity

How often prompts appear:

Lower intensity = only show in top moments

Higher intensity = show more often, even in “okay” moments

Q

Quiet Moment

A moment when users are relaxed or not rushed - ideal for prompts. ContextSDK identifies and prioritizes these windows.

R

Real-world Context

Your user’s real-world situation: are they sitting, walking, relaxing? ContextSDK reads this to pick the right moment.

S

Signal

Any piece of context data collected by the SDK (e.g. motion, battery, screen state) on-device that helps inform decision-making.

T

Treatment Group

(= ContextSDK Group) Users who get smarter timing decisions from our AI (e.g., better-timed paywalls, push notifications).

U

Upsell Offer (or Upsell Prompt)

Any screen asking users to upgrade, buy, subscribe, or give permissions.

User-Initiated Flows

User clicks something and expects a result right away (e.g., clicks “Subscribe Now”). ContextSDK doesn’t block these.

V

Variant

A version of your app flow used in A/B testing to compare against control. ContextSDK helps test multiple variants for optimization.

W

Wait Threshold

The minimum amount of time ContextSDK may delay a prompt to wait for a better moment.

Z

Zero-Permission Context

ContextSDK captures signals without needing extra permissions, keeping privacy intact by design.