Skip to content
Attribution + engagement

One SDK. One event stream. One bill.

Your attribution tool and your engagement tool keep separate notes on the same user, and each sends its own invoice. Enggage does both jobs on one stream of events: where every install came from, what people did next, and the message that brings them back.

Book a demoSee the SDK

Web · Android · React Native · FlutterData in Mumbai by default

enggage / Overview

Overview

The events are arriving.

live

Events

18,492

this week

Installs

1,284

attributed

Every tap, install and purchase—delivered to one place.

  • 4SDKs

    Web, Android, React Native, Flutter

  • 5channels

    Email, SMS, WhatsApp, RCS, push

  • 3consent flags

    Travel with every single event

  • 25months

    Default retention, then it's gone

  • 0sending accounts

    Held by us; your own providers send

The problem

Two tools, two bills, two versions of the truth.

Most apps run one SDK for engagement and another for attribution. They have never met, and they disagree about your users in two different dashboards.

Before

The usual setup

  • Two SDKs in your app, two event taxonomies to keep in sync
  • The install source lives in one tool, the behaviour in the other
  • Joining them is a data project nobody signed up for
  • Two contracts, often in dollars, with two sales teams

After

With Enggage

  • One SDK and one event spec on web, Android, React Native and Flutter
  • A segment can use the install source; ROAS uses purchases you already track
  • One profile per person, with anonymous history merged on login
  • One contract and one bill, from an Indian company
How it works

From one tap to the right message.

Every event is posted once. Both halves of the product read the same envelope, so nothing has to be copied, synced or reconciled.

  1. Add the SDK

    A few lines in your web, Android, React Native or Flutter app. One write key, one event spec.

    init · track · identify

  2. Events land in one stream

    Installs, opens, sessions and your own events arrive validated and in order per device. Rejected ones come with the reason.

    live, as it happens

  3. Attribution reads the postmark

    A click id, the Play Install Referrer or a link id tells you which network and campaign drove each install.

    last touch, your lookbacks

  4. Engagement writes back

    Segments, campaigns and journeys read the same rows, install source included, and send through your own providers.

    same data, no exports

Follow one envelope

The same event can connect a click to an install, a purchase and the postback that closes the loop.

1

Click

Tracking link

2

Install

Play referrer

3

Purchase

₹1,249 event

4

Postback

Network notified

Available today

Everything on this page works today.

No roadmap in disguise. If it is listed here, it is in the product and in the dashboard.

01 / 03

Measure

Know where every install and event came from.

  • Event analytics

    Count anything.

    Track custom and built-in events, then explore them by day and by property.

  • Install attribution

    “Where did they come from?” Answered.

    Click id, Play Install Referrer or a link id tells you where an install came from, with last touch and per-network lookback windows.

  • Tracking and deep links

    One link, every device.

    Device-aware redirects, Android App Links and deferred deep links, all connected to the attribution record.

  • Ad-network postbacks

    We keep knocking.

    The ad-network postback catalog and URL templates send installs and in-app events back with delivery retries.

  • Cost and ROAS

    Spend in, sense out.

    Upload spend by CSV or API and see cost per install and return on ad spend by campaign.

  • Live and rejected events

    Nothing silently dropped.

    Watch events arrive as they happen, and see exactly why any were turned away.

  • Conversion APIs

    Built. Now proving it live.

    Meta and Google conversion API connections are built and being verified with live accounts. Postback catalog connections work today.

02 / 03

Engage

Reach the right people through the channels you already pay for.

  • Segments

    Who did what, and how many.

    Group people by what they did and who they are, with live sizes and sample profiles.

  • Campaigns on your providers

    Your sender, your templates, your provider bill.

    Email, SMS, WhatsApp, RCS and push through SMTP, SendGrid, MSG91, the WhatsApp Cloud API, Firebase or any HTTP provider, with delivery reports.

  • Journeys

    Persistent, never pushy.

    Timed, multi-step sequences that react to what each person does and stop when they convert.

  • In-app messages

    A nudge at the right moment.

    Modals and banners on web and Android, shown on load or right after an event.

  • Unsubscribe links

    Leaving takes one click.

    Marketing email carries an unsubscribe link, so nobody has to reply STOP to a newsletter.

  • Indian sending rules

    No 2 a.m. promos.

    Approved DLT and WhatsApp template fields; promotional SMS and RCS only between 10:00 and 21:00 IST.

03 / 03

Platform

SDKs built never to crash or slow the app they live in.

  • Four SDKs, one API

    Same names everywhere.

    Web, Android, React Native and Flutter, with an offline queue, batching, backoff and automatic install and session events.

  • Remote kill switch

    Hope you never need it.

    One switch stops every installed copy of the SDK on its next start.

  • Profiles and identity

    Anonymous today, known tomorrow.

    Anonymous and logged-in history merge into one profile, while shared devices stay separate.

  • Roles and keys

    Rotate without a 3 a.m. outage.

    Owner, admin and member roles; write and secret keys with rotation grace periods.

Inside Enggage

The whole customer story, in one workspace.

A guided tour of a sample workspace. The numbers are examples; every view maps to a feature in the product.

  • enggage / Overview

    Good morning

    A single view of the stream.

    Nov 3–9

    Active people

    12,480

    sample workspace

    Purchases

    2,174

    events received

    Attributed

    ₹8.34L

    revenue

    Healthy SDKs

    4 / 4

    sending

    Tracked events

    Purchase, cart and activation events, one timeline.

    18,492
    01

    A shared overview

    Events, installs, profiles and revenue sit on the same canvas.

  • enggage / Person profile
    PS

    Priya Shah

    priya.shah@example.com

    AttributionGoogle / Diwali search
    CityMumbai
    Lifetime revenue₹3,746
    Consentanalytics · marketing

    Journey

    last 14 days

    1. Install attributed

      Google Play

    2. Viewed Masala Chai

      Mumbai

    3. Campaign delivered

      WhatsApp

    4. Purchase received

      ₹1,249

    02

    A person, not a row

    Attribution, journey and revenue belong beside each other.

  • enggage / Funnels

    Funnel

    First cup to checkout

    7 days
    1. Product viewed12,480 · 100%
    2. Added to cart4,902 · 39.3%
    3. Checkout started2,318 · 18.6%
    4. Purchased1,746 · 14.0%

    The largest step-down is cart → checkout. Build a segment from it, then send through your own provider.

    03

    Funnels

    See the step that deserves the next message.

  • enggage / Retention

    Retention

    Weekly cohorts

    event: $session_started
    W0W1W2W3W4W5W6Oct 6Oct 13Oct 20Oct 27
    Week-4 retained28.6%
    04

    Retention

    Cohorts make returning behaviour visible.

  • enggage / Campaigns / WhatsApp

    WhatsApp campaign

    Weekend brew reminder

    ready

    TEMPLATE · APPROVED ID

    Hi Priya, your weekend chai is waiting.

    Free delivery over ₹499 in Mumbai, Pune and Bengaluru.

    Shop chai

    WhatsApp provider

    Gupshup · client account

    SMS provider

    MSG91 · client account

    Audience

    Cart, no purchase · 2d

    Send time

    Sat · 11:00 IST

    Uses your own approved template and provider account.
    05

    WhatsApp, through your provider

    A campaign uses the provider account you already own.

  • enggage / Tracking link

    Tracking link

    Diwali chai offer

    go.enggage.in/diwali-chai

    Installs attributed

    1,284

    +18.2%

    Google
    612
    Instagram
    368
    WhatsApp
    192
    Other
    112
    06

    Links that explain installs

    Source-level installs stay connected to the link that drove them.

  • enggage / Fraud rules

    Attribution fraud

    Rule verdicts, not black boxes.

    Click-to-install under 8 seconds

    rule_01

    Review

    Known device duplication

    rule_02

    Passed

    Suspicious referrer pattern

    rule_03

    Blocked

    Rules are visible beside every decision.

    07

    Fraud verdicts

    Rules and their decisions remain inspectable.

SDK

Four platforms. The same few lines.

Web, Android, React Native and Flutter share one API, one event spec and one write key. Identify a person once and their anonymous history follows them.

  • Offline queue

    with batching and exponential backoff

  • Automatic events

    install, open, update and session, sent for you

  • Remote off switch

    stops every installed copy on its next start

  • Same rules everywhere

    event names and identity work the same on every platform

Enggage.init("wk_...", { host }); Enggage.track("signup_completed");Enggage.identify("user-42");Enggage.track("$purchase", {  revenue: 499,  currency: "INR",  products: [{ id: "plan-pro" }],});
Made for India

Built here, for apps that grow here.

Residency, consent and messaging rules are part of the product, not a project you run after signing.

  • ap-south-1INDIA

    Stored in Mumbai

    Your data lives in AWS Mumbai by default, so residency is settled before your first event.

  • DPDPINDIA

    Export and delete, per person

    Three consent flags travel with every event. Export and delete APIs per user, with a request log. You stay the Data Fiduciary.

  • DLTINDIA

    Your providers, your templates

    Enter your approved DLT and WhatsApp template ids. Messages go out through your own accounts; we hold no sending accounts.

  • ₹ INRINDIA

    Rupees, not dollars

    Quoted in rupees by an Indian company, so your bill does not move with the exchange rate.

  • No fingerprinting: deferred deep links match on click id only
  • Advertising ids need attribution consent; no IMEI or MAC
  • A per-app setting for children's apps turns attribution off
  • 25-month retention by default

Honesty is cheaper than a roadmap slide.

Not here yet

What we have not built, said out loud.

  • Automatic ad-spend pulls

    Spend comes in by CSV or API upload for now. Your finance team may even enjoy it.

  • Customer logos

    None yet, and we will not borrow anyone else's. See it work on your own test build instead.

  • A sending account of our own

    Campaigns use your providers, templates and sender reputation. We do not keep a sending account in the middle.

FAQ

Fair questions, straight answers.

The things people ask on the first call, answered the same way we answer them there.

You have no customers or logos. Why trust you?

Correct, and we will not pretend otherwise. You can see everything working on your own test build, with your own events, before you commit to anything.

Why not just use CleverTap, MoEngage or WebEngage?

They are mature engagement tools, and if engagement is all you need they may be the right choice. They do not do install attribution and deep linking themselves, so you still need a second SDK and a second contract. Enggage puts both on one event stream, so a segment can use the install source, and both come on one bill.

Why not AppsFlyer or Branch?

They have far more established ad-network integrations. Enggage has an ad-network postback catalog and URL-template postbacks in product today. Meta and Google conversion API connections are built and being verified with live accounts; until that is done, lean on what you use now. Our case is for teams that want attribution and engagement on the same data.

Switching is risky. What if you break our app?

The SDKs are built never to crash or slow the host app: offline queue, batching, backoff, a size budget, and a remote kill switch that stops every installed copy on its next start. You can run Enggage alongside your current tools on a test build or a small rollout before switching anything off.

Where is our data stored, and who can see it?

In AWS Mumbai (ap-south-1) by default. Every row carries your tenant and app ids, every query is filtered by both, and tests check that tenants cannot see each other's data. The raw IP address is not stored in the analytics store.

What about the DPDP Act?

You remain the Data Fiduciary and we are your processor. The product gives you consent flags on every event, an optional consent-required mode, export and delete APIs per user with a request log, 25-month retention by default and a setting for apps directed at children.

Can you do our DLT and WhatsApp approvals?

No. You complete DLT registration and WhatsApp template approval with your providers, as you do today, and enter the approved ids in Enggage. We hold no sending accounts, which also means your sender reputation and provider pricing stay yours.

Pricing

One bill instead of two.

Designed to cost well below buying an engagement tool and an attribution tool separately. Prices depend on your volume, so talk to us for a quote.

Get a quote

ENGGAGE

one invoice · one vendor

  • Event analytics
  • Install attribution
  • Tracking and deep links
  • Postbacks, cost and ROAS
  • Segments and campaigns
  • Journeys and in-app

Bills to reconcile1

Book a demo

See it on your own data.

Fifteen minutes, your app, your events. Tell us a little and we will set it up.

  1. 1We create an app and a write key for you.
  2. 2You send a handful of events from a test build or your site.
  3. 3We walk through attribution, a segment and a campaign on your own provider.

Optional, but it helps us prepare.

We use these details only to reply to your request.