When you toggle on Nanigans in Segment, this is what happens:
- Our CDN is updated within 45 minutes. Then our snippet will start asynchronously loading Nanigans.js onto your page. This means you should remove Nanigans’s snippet from your page.
- Nanigans will start automatically collecting data on your site.
In order for the
track call to succeed, the requirements include a
userId being set previously by an
For ecommerce events,(i.e.
purchase) it is important that the
.track() call also includes the below within
productsarray, which contain objects that have
More information about the semantic naming of our ecommerce events.
If the folks at Nanigans ask you pass through any custom parameters, you can map the Segment event properties to arbitrary querystring parameters as well. Note: This is currently only supported via the server-side destination, which is used for our mobile and server-side libraries.
By default, if you are sending data via a mobile library, we will send the
IDFA (iOS) or
Advertising ID (Android) so that you can associate server side events with the anonymous users from your mobile app.
However, if you are sending events with a server side library, you can still manually pass the
Advertising ID under
context.device.advertisingId and we will send it along to achieve the same effect.
By default, if you send any data with either the iOS or Android library, we will send that data to Nanigans required
If you’d like to send any other server side event using a server side library, you can either enable the option “Send Events to Mobile Endpoint” in your Nanigans settings. However, this means that ALL server side events sent from your server side library will be sent to the mobile endpoint.
If you are unsure which endpoint to send to, please contact Nanigans support!
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
The first step is to make sure Nanigans supports the source type and connection mode you’ve chosen to implement. You can learn more about what dictates the connection modes we support here.
To learn more about about Connection Modes and what dictates which we support, see here.
This destination requires a Device-based Connection Mode for Mobile data. Follow the steps above to ensure you have packaged the Nanigans SDK with Segment’s.
Segment lets you change these destination settings from your Segment dashboard without having to touch any code.
Send Events to Mobile Endpoint
Select this option to send your data to Nanigans’ mobile endpoint. Most projects (even mobile ones) don’t need this option enabled; if you’re unsure, check with your Nanigans contact. Note that if you set this option, you must also set your Facebook App ID.
You can find your App ID in your Nanigans pixel; it’s the xxx part of the app_id=xxx parameter.
Use these fields to map your Segment event names to Nanigans event names. We’ll only send Nanigans the conversion events you specify.
Facebook App ID
You can find your Facebook App ID in your Nanigans pixel; it’s the xxx part of the fb_app_id=xxx parameter.
Questions? Problems? Need more info? Contact us, and we can help!