Goedle Destination

goedle.io uses powerful AI and Machine Learning algorithms to predict user behavior. The more data you provide, the better its recommendations will be. This destination is maintained by Goedle. For any issues with the destination, please reach out to their team.

This document was last updated on May 16, 2018. 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 Goedle 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 “Goedle” within the Destinations Catalog and confirm the Source you’d like to connect to.
  3. In your Segment Settings UI, enter your goedle.io app key which you received upon sign up.
  4. After activating, goedle.io will start automatically collecting data from your website, mobile app, or game. However, it will take up to 24 hours for goedle.io to process this data and predict future user behavior - you will receive an email from goedle.io when your data is available.

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();

goedle.io will track a pageview and log the path property to distinguish different user behaviors.

Screen

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.screen();

goedle.io will track a screenview on your mobile app and log the name property to distinguish different user behaviors.

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('ze8rt1u89', {
  firstName: 'Zaphod',
  lastName: 'Beeblebrox',
  email: 'Zaphod@hotmail.com'
});

goedle.io will set the userId, as well as specific user traits that are provided with the call.

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('Reached Level', {
  properties: {
    event_id: '60',
    event_value: '66.2'
  }
})

goedle.io will log the corresponding event using the event along with any additional properties passed in.

Ecommerce

goedle.io supports some Ecommerce events as part of the Segment V1 and V2 Ecommerce specs and they will be automatically merged if required. An example Ecommerce call would look like:

analytics.track('Product List Viewed', {
  properties: {
    product_id: 'A20',
    price: 66.2,
    quantity: 2
  }
})

The supported events are as follows:

The following properties are supported as part of the above events:

  • product_id
  • price
  • quantity
  • currency

A/B Testing

goedle.io supports the Segment A/B Testing specs and builds an internal hierarchy used to enhance the prediction of the user behavior during an experiment.

These experiments can be sent as follows with a required experiment_id and an optional variation_id. If experiment_id is not included, Experiment Viewed will be treated as a regular event.

analytics.track('Experiment Viewed', {
  experimentId: '7561662364',
  variationId: '7549901603'
});

Group

When you trigger a group event, we will log the group_id for an individual user.


If you have any questions or see anywhere we can improve our documentation, please let us know or kick off a conversation in the Segment Community!