Segment makes it easy to send your data to Nudgespot (and lots of other destinations). Once you've tracked your data through our open source libraries we'll translate and route your data to Nudgespot in the format they understand. Learn more about how to use Nudgespot with Segment.
When you toggle on Nudgespot in Segment, this is what happens:
- Our CDN is updated within 5-10 minutes.
- If you are using Nudgespot for the first time, sign up and choose the ‘Segment’ option under Destinations on their ‘Getting Started with Nudgespot’ page.
- Once you reach the Segment onboarding page, click on the ‘Enable with Segment’ option.
- If you are already using Nudgespot, go to the ‘Settings’ page and click on the ‘Enable with Segment’ button.
Nudgespot is supported on mobile, web browsers and on the server side.
The first thing you’ll want to do is to identify your users so Nudgespot knows who they are. You’ll use the
identify method to accomplish this - identify takes the unique user Id of a user, first name, and any other traits you know about them.
When you call
identify from any of Nudgespot’s server-side libraries, they’ll create or update the users in Nudgespot with the traits provided.
You will see the traits appear as properties on any events you track.
track method maps events and event properties directly to Nudgespot events and event properties.
Sending Data from Nudgespot
Nudgespot supports sending email events to other tools on the Segment platform. These events will be sent as
track calls to the other destinations you’ve turned on. To enable this feature, enter in your Write Key when setting up your account.
When will I see data from my mobile app?
If you already have an app deployed with the Segment source, and you just turned on Nudgespot, it will take up to an hour for all your mobile users to refresh their Segment settings cache, and learn about the new service that you want to send to. After the settings cache refreshes, our source will automatically start sending data to Nudgespot.
For user-property destinations, an identify call will be sent to the destination for each user being added and removed. The property name will be the snake_cased version of the audience name you provide with a true/false value. For example, when a user first completes an order in the last 30 days, we will send an identify call with the property
order_completed_last_30days: true, and when this user no longer satisfies we will set that value to
When the audience is first created an identify call is sent for every user in the audience. Subsequent syncs will only send updates for those users which were added or removed since the last sync.
Supported Sources and Connection Modes
To learn more about about Connection Modes and what dictates which we support, see here.
Segment lets you change these destination settings via your Segment dashboard without having to touch any code.
Server-side API Key
Your Server-side API Key can be found in your Nudgespot dashboard under Settings
If you have any questions, or see anywhere we can improve our documentation, please let us know!