QuanticMind Destination

QuanticMind is the performance leader in predictive advertising management software for paid search, social, display, and mobile. The analytics.js QuanticMind Destination is open-source. You can browse the code on GitHub.

This document was last updated on January 09, 2019. If you notice any gaps, outdated information or simply want to leave some feedback to help us improve our documentation, please let us know!

Getting Started

The first step is to make sure QuanticMind 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.

WebMobileServer
📱 Device-based
☁️ Cloud-based
  1. From your Segment UI’s Destinations page click on “Add Destination”.
  2. Search for “QuanticMind” within the Destinations Catalog and confirm the Source you’d like to connect to.
  3. Drop in your ClientID, and Domain if provided, from QuanticMind account manager.
  4. Under Events you can then map any necessary ‘track’ event/s to QuanticMind numbered event/s. Please note that unless mapped in the settings, no ‘track’ calls will be sent to QuanticMind.

Page

If you haven’t had a chance to review our spec, please take a look to understand what the Page method does. An example call would look like:

analytics.page();

Page calls to Segment result in us pushing a “click” event to QuanticMind.

Identify

If you haven’t had a chance to review our spec, please take a look to understand what the Identify method does. An example call would look like:

analytics.identify('12091906-01011992', {
  name: 'John Doe',
  email: 'john.doe@example.com'
});

Track

If you haven’t had a chance to review our spec, please take a look to understand what the Track method does. An example call would look like:

analytics.track("Button Clicked", {
  property: "test"
});

QuanticMind only accepts numbered events like event1 and event12. When you analytics.track(event, properties) an event, we need to map that event name to QuanticMind numbered event via your destination settings. Enter an event on the left, and the QuanticMind event number you want on the right.


Personas

You can send computed traits and audiences generated through Segment Personas to this destination as a user property. To learn more about Personas, reach out for a demo.

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 false.

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

WebMobileServer
📱 Device-based
☁️ Cloud-based

To learn more about about Connection Modes and what dictates which we support, see here.

Settings

Segment lets you change these destination settings via your Segment dashboard without having to touch any code.

ClientID

Your QuanticMind account manager will provide your ClientID.

Domain

Your QuanticMind account manager will provide your Domain, if needed.

Events

QuanticMind only accepts numbered events like event1 and 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 friends@segment.io 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!