GWEN Webhooks Source

GWEN Webhooks offers powerful gamification tools and insights to convert, engage, and retain users. With GWEN it has never been easier to understand your users behavior patterns and build better performing products with both speed and accuracy.

This is an Event Cloud Source which can not only export data into your Segment warehouse, but can also federate the exported data into your other enabled Segment Destinations.

This source is maintained by Insert Coin AB. For any issues with the source, contact their Support team.

Getting started

1. From your workspace’s Sources catalog page click Add Source.
2. Search for “GWEN Webhooks” in the Sources Catalog, select GWEN Webhooks, and click Add Source.
3. On the next screen, give the Source a nickname and configure any other settings.
   • The nickname is used as a label in the Segment app, and Segment creates a related schema name in your warehouse. The nickname can be anything, but Segment recommends using something that reflects the source itself and distinguishes amongst your environments (for example, SourceName_Prod, SourceName_Staging, or SourceName_Dev).
4. Click Add Source to save your settings.
5. Copy the Write key from the Segment UI and log in to your GWEN account.
6. Navigate to Setup Management > Webhooks and click the Set credentials button next to Segment Source webhooks. Paste the key to connect.

Stream

GWEN Webhooks uses a stream Source component to send Segment event data. It uses a server-side (select from track, identify, page, group) method(s) to send GWEN user data to Segment (Read more about GWEN webhook data here). These events are then available in any destination that accepts server-side events, and also available in a schema in your data warehouse, so you can query using SQL.

The default behavior is for GWEN Webhooks to pass the userId associated with the user who triggered the given update. This may or may not be a userId that you are keeping track of, depending on under what circumstances the user has been created within GWEN. For example, users created anonymously by using the GWEN Analytics script will likely have a userId unknown to you.

Events

The table below lists events that GWEN Webhooks sends to Segment. These events appear as tables in your warehouse, and as regular events in other Destinations.

Event Properties

The table below list the properties included in the events listed above. You can read about specific GWEN mechanic states and updates under modules in the GWEN platform documentation.

Adding Destinations

Now that your Source is set up, you can connect it with Destinations.

Log into your downstream tools and check to see that your events appear as expected, and that they contain all of the properties you expect. If your events and properties don’t appear, check the Event Delivery tool, and refer to the Destination docs for each tool for troubleshooting.

If there are any issues with how the events are arriving in Segment, contact the GWEN support team.