Goedle.io 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, contact the Goedle Support team.

Getting Started

Before you start, make sure goedle.io supports the source type and connection mode you’ve chosen to implement. You can learn more about connection modes here.

1. From your Segment UI’s Destinations page click on “Add Destination”.
2. Search for “Goedle” in the Catalog, select it, and choose which of your sources to connect the destination to.
3. In your Segment Settings UI, enter your goedle.io app key which you received upon sign up.
4. After activating, goedle.io starts 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’re not familiar with the Segment Specs, 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’re not familiar with the Segment Specs, 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’re not familiar with the Segment Specs, take a look to understand what the Identify method does. An example call would look like:

analytics.identify('ze8rt1u89', {
  firstName: 'Jane',
  lastName: 'Kim',
  email: 'jane.kim@example.com'
});

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

Track

If you’re not familiar with the Segment Specs, 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:

• Product List Viewed
• Product Added
• Product Removed
• Product Viewed
• Order Completed

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.

Personas

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

For user-property destinations, an identify call is sent to the destination for each user being added and removed. The property name is the snake_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Personas sends an Identify call with the property order_completed_last_30days: true. When the user no longer satisfies this condition (for example, it’s been more than 30 days since their last order), Personas sets that value to false.

When you first create an audience, Personas sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync.

Settings

Segment lets you change these destination settings from the Segment app without having to touch any code.

APP Key

Your goedle.io APP Key is available in the goedle.io interface.

Adding goedle.io to the integrations object

To add goedle.io to the integrations JSON object (for example, to filter data from a specific source), use one of the following valid names for this integration:

• Goedle

• goedle.io