Welcome to NVECTA onboarding. The onboarding process covers everything you need to get started, including account setup, tracking plan creation and implementation, tool adoption training for teams, and configuring marketing channels pipeline.

This setup guide is the first and foremost step, where we will walk you through how to create the right accounts, set up safe access for your team, connect your website and apps, and verify that your core system events and session analytics are tracking correctly across all platforms. The goal is to help you start with clean data, clear identities and proper permissions so that everything you do later in NVECTA is reliable and easy to manage.

Set up your UAT and Production accounts

First, create two separate environments: one for UAT (User Acceptance Testing) and one for Production. Use the UAT account for all tests by connecting your website and apps. If you have staging websites and staging apps, you can use those as well. The UAT account is for your developers to integrate our SDKs, verify events, try new journeys, and send only internal test campaigns. It is fine if the data here contains test users and fake orders.

Use the Production account only for real customers and real traffic. Connect your live website and apps to this account, and send all live campaigns from here. Keep access more limited in Production, and move changes from UAT to Production only after they are tested.

This separation makes it very easy to experiment without risking your real users, and it also helps you keep test data out of your final analytics and reports.

Plan panel access and protect PII

Before inviting your full team into NVECTA, take a moment to decide which people need which level of access. In your account, you can create different roles and control which areas each role can see, for example, campaigns, analytics, settings or billing.

We also offer PII masking, which is an important feature for privacy and compliance. With PII masking, you can hide sensitive user information such as email addresses and phone numbers from selected roles. People with these roles can still work with segments, campaigns and reports, but fields that are marked as PII are obfuscated in the interface.

A simple way to structure your access is to give developers a role that can manage integrations and see the technical event data they need in UAT, give data analysts a role that focuses on analytics with PII masked, give marketers a role that can create and manage campaigns and journeys, and keep a smaller admin group with full access to all organization settings. You can optionally enable two-factor authentication for login to further secure sensitive accounts.

When this is done, invite your team into your UAT and Production accounts and assign them the roles you have just defined, instead of giving everyone full access by default.

Configure your user identifier and profile merging

Next, decide how you will identify users and merge profiles in NVECTA. In your dashboard, you can go to Settings and then to Users and choose how you want profiles to be unified. Our platform supports primary identifiers such as mobile, email, and custom identifier. Once selected, the primary identifier can not be changed.

If your user base is mobile-first, uses WhatsApp or SMS frequently, then choosing mobile as your primary identifier is usually the best option. If your product relies more on email for login, communication, onboarding, or work-related usage, then email is a better primary identifier. Alternatively, choose the custom identifier option if you want to use your own backend ID, such as customer_id, user_id, or account_id, to identify every user in NVECTA.

Furthermore, select the ‘User profile merging’ option to merge multiple profiles of the same user into a single profile. Once enabled, it can not be disabled again. We merge profiles when we have deterministic signals that two records represent the same person, and we avoid merges when core identifiers conflict.

Install NVECTA on your website and apps

At this stage, you’re ready to integrate NVECTA across all the platforms where users interact with your business. Start by listing each digital platform you operate, this typically includes your website and one or more mobile apps. For websites, identify whether it’s custom-built or hosted on a CMS or e-commerce platform such as Shopify. For mobile, note whether you use native Android or iOS apps, or hybrid frameworks like React Native or Flutter.

To connect your website, SDK-based integrations are available. The [Web SDK](https://docs.notifyvisitors.com/docs/web-integration?_gl=1*1bkxxyx*_ga*MTkxNjM5MDkyNy4xNjc1MTc1MTgy*_ga_TM11Z4ENKW*MTY5NTc5NDk1Ni41OTEuMC4xNjk1Nzk0OTU2LjYwLjAuMA..) allows you to add NVECTA to any website to track user behavior, deploy forms and popups, and capture events. If your website runs on a CMS or e-commerce platform, NVECTA offers prebuilt integrations that make setup fast and simple. Platforms such as [Shopify](https://docs.notifyvisitors.com/docs/shopify?_gl=1*5lqo5c*_ga*MTkxNjM5MDkyNy4xNjc1MTc1MTgy*_ga_TM11Z4ENKW*MTY5NTc5NDk1Ni41OTEuMC4xNjk1Nzk0OTU2LjYwLjAuMA..), Magento, WooCommerce, Wix, Wordpress, and more can be connected using ready-made plugins.

Mobile apps can integrate using the [Android SDK](https://docs.notifyvisitors.com/docs/android-integration?_gl=1*1bkxxyx*_ga*MTkxNjM5MDkyNy4xNjc1MTc1MTgy*_ga_TM11Z4ENKW*MTY5NTc5NDk1Ni41OTEuMC4xNjk1Nzk0OTU2LjYwLjAuMA..) or [iOS SDK](https://docs.notifyvisitors.com/docs/ios-integration?_gl=1*ru73dp*_ga*MTkxNjM5MDkyNy4xNjc1MTc1MTgy*_ga_TM11Z4ENKW*MTY5NTc5NDk1Ni41OTEuMC4xNjk1Nzk0OTU2LjYwLjAuMA..). If your app is built using hybrid frameworks such as React Native, Flutter, Cordova, Ionic, or Unity, dedicated SDKs are available to ensure smooth cross-platform integration.

For advanced or backend-driven use cases, NVECTA also supports [API-based integrations](https://docs.notifyvisitors.com/reference/users?_gl=1*1tn8ijj*_ga*MTkxNjM5MDkyNy4xNjc1MTc1MTgy*_ga_TM11Z4ENKW*MTY5NTgwOTE4My41OTIuMS4xNjk1ODA5MTk3LjQ2LjAuMA..). Using APIs, you can send user profiles and key events directly from your backend systems. This approach gives you more control over data flow and enables highly targeted, event-driven campaigns based on real business actions.

NVECTA also offers app marketplace allowing integration with wide range of third-party applications allowing you to extend functionality, streamline workflows, and enhance user engagement with minimal effort.

Once you have identified the right integration method for each platform, log in to your UAT account and visit the mentioned links to follow the appropriate integration guide. From the dashboard, copy the required brand identifiers and keys for your UAT environment and share them with the respective developers along with the correct documentation links. Make sure they clearly understand which field is configured as the unique user identifier so identification methods are implemented correctly. Always complete integrations in UAT first to safely test data flow and fix issues before moving to Production.

Verify session analytics in the panel

Before we move deeper into user and event tracking, make sure that your basic session analytics look healthy. These system-generated events help confirm that your SDK installations are working correctly across all platforms.

First, open your UAT dashboard and look at events from the last 24 hours. Check the following:

• Confirm that the session_start event is appearing for all platforms you have integrated: web, m-site, Android app and iOS app.
• For your web platform, confirm that page_view events are being captured consistently in the last 24 hours.
• For your Android and iOS apps, check whether install event have appeared in the last 24 hours. These events may be fewer in number, but they should still show up whenever the app is installed during your testing.

If any of these events are missing, confirm that System Events are enabled. You can verify this by going to Settings → Events → System Events and checking whether session_start, page_view, install, and other system events are toggled on. Missing system events usually mean they are disabled in this section rather than an SDK issue.

Once everything looks correct in UAT, repeat the same checklist in your Production account to ensure your live environment is tracking sessions and system events accurately.

Set up push notifications and test subscribers

If you plan to send push notifications, configure them at this stage while you are still in UAT. For web push, configure your web push keys and service worker. For Android, set up the connection with Firebase Cloud Messaging, and for iOS configure your APNs credentials.

After technical setup, install your UAT builds on real devices and allow push permissions. Verify that push_registered events are appearing in the last 24 hours for all platforms: web, m-site, Android app and iOS app. In the panel, go to campaigns > App push > Logs to confirm that your test devices are registered.

Create a small test push campaign targeting only your internal test profile or a tiny UAT segment, send a message and confirm that it is delivered and tracked on those devices.

When everything works reliably in UAT, mirror the configuration for your Production account with production keys and repeat the same test with a very small group of internal users before you start using push at scale.

Track Screen View in Android and iOS apps

If you’ve connected mobile apps, the next recommended step is to integrate screen view tracking in your UAT environment and verify this event in the last 24 hours to ensure screen view tracking is working correctly.

• Check whether the screen_view events are appearing for both Android app and iOS app. These events help you understand how users are moving across different screens inside your app.
• If you notice that the event bucket usage is increasing rapidly because of frequent screen view updates, you can disable this event from the panel. Go to Settings → Events → System Events and turn off screen_view if needed.

• Do not remove this event from your app’s SDK implementation. It is still used internally for features such as in-app nudges, and removing it may affect how those experiences trigger.

Once confirmed, follow the same steps in Production to make sure your real apps send stable and controlled screen view analytics.

Where to go next

After you complete this setup, you will have clean UAT and Production accounts, safe access and PII rules for your team, a clear user identity strategy, working SDK integrations, basic analytics and push tracking.

NVECTA Platform Setup & Implementation — AI-Performable Steps Validate access control and PII protection Confirm that multiple access roles exist with different permission levels Verify that: - Technical roles can access integration and event data - Analytics roles can access reports with sensitive fields masked - Marketing roles can manage campaigns without full admin access Confirm that sensitive user attributes (e.g., email, phone) are masked for restricted roles Interpretation: If access is role-based and PII is masked → compliance and data safety are ensured Validate user identification strategy Confirm that exactly one primary user identifier is defined: - Mobile number or - Email or - Custom backend identifier Verify that: - The same identifier is used consistently across all platforms - The identifier is immutable once selected Confirm that profile merging is enabled Interpretation: If identifiers are consistent and profiles merge → user identity is reliable Validate platform integrations Confirm that NVECTA is connected to all intended platforms: - Website - Mobile site (if applicable) - Android app - iOS app Verify that: - SDK-based or API-based integrations are active - Test data is flowing into UAT Interpretation: If events are received from all platforms → integrations are successful Check session start events Verify that the session_start event appears for all integrated platforms: - Web - Mobile site (m-site) - Android app - iOS app Check web page views Confirm that page_view events are appearing consistently in the last 24 hours Check app install events Look for install events in the last 24 hours for: - Android app - iOS app Note: Low volume is acceptable during testing Interpret session analytics health If all system events appear → SDK setup is working correctly If any system event is missing → tracking configuration is incomplete Validate push notification readiness Confirm that push capability exists for: - Web - Android app - iOS app Verify that push_registered events appear in the last 24 hours for test users Confirm that at least one test push message: - Is sent - Is delivered - Is tracked Interpretation: If test pushes are delivered and logged → push setup is functional Validate screen view tracking (mobile apps) Confirm that screen_view events appear for: - Android app - iOS app Verify that screen view events reflect actual navigation behavior Interpretation: If screen views are tracked → in-app analytics and nudges will work correctly