Namespaced API

Available since reteno-react-native-sdk v3.0.0.

Every SDK method has always been exported as a flat, top-level function — setUserAttributes, setOnRetenoPushReceivedListener, logEcomEventOrderCreated, and so on. That flat form is unchanged and stays the canonical, fully supported API — nothing in this page deprecates it.

Starting with v3.0.0, the same functions are additionally grouped into seven namespaced objects: user, push, events, inApp, inbox, recommendations, ecommerce. Each namespace member is the identical function reference as its flat counterpart (push.setDeviceToken === setDeviceToken), just re-exposed under a shorter, grouped name — pick whichever style reads better in your codebase, or mix them.

Usage

Import the namespace(s) you need directly:

import { push, user, inApp } from "reteno-react-native-sdk";

await user.setAttributes({ externalUserId: "USER_ID", user: { /* ... */ } });

const clickListener = push.setOnClickedListener((event) => {
  // ...
});

inApp.setAutoOpenLinks(false);

Or import everything under one alias if you prefer a single Reteno. prefix everywhere:

import * as Reteno from "reteno-react-native-sdk";

await Reteno.initialize({ apiKey: "YOUR_SDK_ACCESS_KEY" });
await Reteno.user.setAttributes({ externalUserId: "USER_ID", user: {} });
Reteno.events.addEventListener("pushReceived", (event) => {
  // ...
});

Note that a handful of top-level functions — initialize, logEvent, logScreenView, forcePushData — are not part of any namespace and stay flat-only; they don't belong to one specific feature area.

Namespace reference

user

See Tracking user information.

push

See Push notification.

events

inApp

See In-App Messages.

Note: push.pauseTriggeredInAppMessages / push.setTriggeredInAppMessagesPauseBehaviour (Android-only, push-triggered in-apps) and inApp.pauseMessages / inApp.setPauseBehaviour (all in-apps, both platforms) wrap two different underlying methods — they are not aliases of each other.

inbox

See App Inbox.

recommendations

See Recommendations.

ecommerce

See Ecommerce.

Migrating existing code

There is nothing to migrate — this is purely additive, and flat imports keep working exactly as before. If you do want to move a file over to the namespaced style, it's a mechanical rename with no behavior change, since each namespace member is a direct reference to its flat function:

- import { setUserAttributes, setOnRetenoPushReceivedListener } from "reteno-react-native-sdk";
+ import { user, push } from "reteno-react-native-sdk";

- setUserAttributes({ externalUserId, user: payload });
+ user.setAttributes({ externalUserId, user: payload });

- setOnRetenoPushReceivedListener(onReceived);
+ push.setOnReceivedListener(onReceived);

Types are unaffected either way — SetUserAttributesPayload, RetenoSubscription, and the rest of the exported types are shared by both call styles.