Nudgespot is the easiest way to trigger emails, SMS, push notifications or in-app messages to your customers, at the right time. Visit Website
Take your company’s email analysis to the next level by adding Nudgespot as a Source to Segment. Segment automatically collects email events like
Email Delivered and
Email Opened, forward them to your destinations, and load them into your data warehouse.
In your favorite BI or analytics tool, you’ll be able to analyze your email campaigns in SQL or through drag-and-drop reports. And, you’ll be able to join your Nudgespot data with the event data you’re already sending through Segment to analyze the down-funnel effects of your emails.
If you have previously enabled sending email events using the Nudgespot destination during our beta (using a project write key), you do not need to create new Nudgespot source. Your email data will continue to flow as normal.
From your workspace’s
segment.com/<your-workspace>/sources page, click
Give the Source a nickname and a schema name. The nickname is a label used in the Segment interface, and the schema name is the namespace you query against in your warehouse. You can name them however you’d like, but we recommend sticking to something that reflects the Source itself, like
Nudgespotfor nickname and
nudgespotfor the schema name.
The next page (“Overview”) will surface your Segment write key for Nudgespot. Copy this write key.
To finish the setup, you’ll have to go into your Nudgespot account and enter this Segment write key in their integrations settings. Find the right place in Nudgespot in set up > Send Email Events to Segment.com.
In Segment, click into your Nudgespot Source in
segment.com/<your-workspace>/sources. From there you’ll be able to add Destinations where you want to see email events.
That’s it! As you send emails, events will now be sent to your destinations and automatically loaded into any warehouses you have enabled.
Nudgespot uses our stream Source component to send Segment email events. It uses a server-side
track method to send data to Segment. These events are then available in any destination that accepts server-side events, and available in a schema in your data warehouse, so you can query using SQL.
The default behavior is for Nudgespot to pass the
userId associated with the email recipient as the
userId. There are cases in which Nudgespot does not have an associated
userId, in which case the email address will be passed in as the
Collections are the groupings of data we pull from your Source. In your warehouse, each collection gets its own table, as well as a
tracks table that aggregates all the events into a single table.
|Email Delivered||Event||Message has been successfully delivered to the receiving server|
|Email Opened||Event||Recipient has opened the HTML message. You need to enable Open Tracking for getting this type of event|
|Email Link Clicked||Event||Recipient clicked on a link within the message. You need to enable Click Tracking for getting this type of event|
|Email Unsubscribed||Event||Recipient clicked on message’s subscription management link|
|Email Bounced||Event||Receiving server could not or would not accept message|
|Email Marked as Spam||Event||Recipient marked message as spam|
Send data to Nudgespot
The Nudgespot Source works better when you also connect Nudgespot as a destination. With the Nudgespot Destination, you can use Segment to send Nudgespot user and event data from which you trigger email campaigns. Want to start sending website or mobile data TO Nudgespot? Head on over to our Nudgespot destination docs.
This page was last modified: 20 Oct 2020
Questions? Problems? Need more info? Contact us, and we can help!