Frequently Asked Questions
Got queries?
We’re here to help
- Product
- Tech
Campaigns are the core experiences you create within Nudge to engage your users. They encompass the setup of interactions, triggers, and user segments, allowing you to deliver personalized and targeted experiences such as challenges, surveys, or in-app messages.
A cohort is a group of users targeted for a specific campaign. You can create a cohort by importing a CSV file containing user identifiers through the Nudge dashboard or by using the Cohort API. This allows you to manage and target specific user segments effectively.
Nudge prioritizes user privacy by requiring only unique identifiers for user tracking, avoiding the collection of personally identifiable information (PII) such as emails or phone numbers. Additionally, all data is encrypted both in transit and at rest, and Nudge complies with data residency requirements by storing data within the ap-south-1 region in India.
Nudge supports two primary types of rewards: Coins and Coupons. Coins act as virtual currency that users can earn and spend within your app, while Coupons are unique codes that users can redeem for discounts or special offers. These rewards can be integrated into various campaigns to incentivize user engagement.
Webhooks in Nudge allow your application to receive real-time notifications about specific events, such as when a user earns a reward. By configuring webhooks in the Nudge dashboard, your backend can automatically process these events, enabling actions like updating user profiles or triggering additional workflows based on user interactions.
Nudge provides an event tracking system that allows you to monitor user interactions within your application. By using the track method in the SDK, you can record events along with their properties. These events are then used to analyze user behavior, segment audiences, and power various campaigns and rewards.
Nudge implements multiple security measures including TLS 1.3 encryption for data in transit, encryption at rest, SQL injection prevention, input validation, IP address monitoring, and rate limiting to prevent denial-of-service (DoS) attacks. Additionally, Nudge leverages secure infrastructure providers like AWS, Scylla, and ClickHouse to ensure robust data protection.
The Client API Key is intended for front-end use, such as tracking events and identifying users through client-side SDKs. It is embedded in your application code and should be handled securely on the client side. The Private API Key, on the other hand, is used for backend integrations and webhooks. It is used for server-to-server communication and must be kept confidential to prevent unauthorized access.
To integrate Nudge with Google Tag Manager, you need to set up Data Layer variables in GTM that correspond to the user and event data you want to track. Then, create GTM tags that utilize these Data Layer variables to send data to Nudge. This allows for dynamic and flexible tracking without modifying your application code directly. Detailed steps can be found in the Data Layer section.
To add a team member to your Nudge dashboard, navigate to the 'Settings' page in the sidebar, go to the 'Team' tab, and click on the 'Add Team Member' button. Enter the new member's details and invite them. They will receive an email invitation to join your organization, where they can set up their password and login with the assigned role.
SDK integration in Nudge involves incorporating the Nudge Software Development Kit into your application to enable features such as user tracking, event logging, and in-app messaging. This integration allows your application to communicate with Nudge's backend services, facilitating personalized user experiences and seamless campaign management. For more details, refer to the Installation section.
Integrating the Nudge SDK into your application allows you to enhance user engagement through personalized campaigns, track user interactions, and reward user activities seamlessly. It provides a robust framework for managing campaigns like challenges, streaks, referrals, and more, enabling data-driven decision-making and improving overall user experience.
Nudge SDK handles user identification by requiring a unique identifier for each user through the userIdentifier method. This ensures that user interactions are tracked accurately without exposing personally identifiable information (PII) such as email addresses or phone numbers. Nudge emphasizes data privacy by allowing you to control the data you send and ensuring all data is encrypted both in transit and at rest. For more details, see the Identifying Users and Data and Privacy sections.
With Nudge SDK, you can create a variety of campaigns including Challenges, Streaks, Referrals, Quizzes, Surveys, Spin the Wheel, Scratch Cards, Nudges (tooltips, spotlights, coachmarks), Popups, Stories, and Checklists. Each campaign type is designed to engage users in different ways, allowing you to boost user engagement, gather feedback, and promote features effectively.
Tracking events with the Nudge SDK is straightforward. Use the track method to log user interactions, specifying the event name and any relevant properties. These events help you understand user behavior and tailor campaigns accordingly. Ensure that event names follow the prescribed format and include necessary properties for detailed analysis.
Managing user sessions with the Nudge SDK involves identifying users when they log in and signing them out when they log out. Use the userIdentifier method to start a session by linking user interactions to a unique identifier. When the user logs out, call the userSignOut method to clear any cached data and end the session. Proper session management ensures accurate tracking and personalization.
Webhooks are automated HTTP POST requests sent from Nudge to your application's backend in response to specific events, such as when a user earns a reward. To set up webhooks, navigate to the Webhooks section in the Nudge dashboard, add a new webhook by specifying your endpoint URL, and select the events you want to receive notifications for. Ensure your server can handle incoming requests and verify webhook signatures for security. Detailed setup instructions can be found in the Webhooks section.