Segment makes it easy to send your data to QuanticMind (and lots of other destinations). Once you've tracked your data through our open source libraries we'll translate and route your data to QuanticMind in the format they understand. Learn more about how to use QuanticMind with Segment.
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.
Your QuanticMind account manager will provide your ClientID.
Your QuanticMind account manager will provide your Domain, if needed.
QuanticMind only accepts numbered events like
event12. When you
analytics.track(event, properties) an event, we need to map that event name to QuanticMind numbered event. Enter an event on the left, and the QuanticMind event number you want on the right. Email firstname.lastname@example.org if you need help!
Use Order Id For Server Side Attribution
Conversions where the pixel-user-id is set to
noclick will indicate to QuanticMind that the conversion should not be matched to a click directly, but instead to a conversion through the conversion’s
orderId. Only use if instructed specifically by your InsideVault account manager.
If you have any questions, or see anywhere we can improve our documentation, please let us know!