Go SDK

Use RudderStack’s Go SDK to send server-side events to various destinations.

RudderStack’s Go SDK lets you track and send the events from your Go applications to the specified destinations.

Refer to the SDK’s GitHub codebase for the implementation-specific details.

Github Badge

SDK setup requirements

  1. Sign up to RudderStack Cloud.
  2. Set up a Go source in your dashboard. You should be able to see a write key for this source:
Go source write key

You will also need a data plane URL. Refer to the Dashboard Overview guide for more information on the data plane URL and where to find it.

success
The Setup tab in the RudderStack dashboard (seen above) has the SDK installation snippet containing both the write key and the data plane URL. Copy it to integrate the Go SDK into your application.

Installing the Go SDK

To install the Go SDK in the GOPATH, run the following command:

go get github.com/rudderlabs/analytics-go

Initializing the SDK

Run the following code snippet to initialize the Go SDK:

package main

import (
    "github.com/rudderlabs/analytics-go/v4"
)

func main() {
    // Instantiates a client to use send messages to the RudderStack API.
    
    // Use your write key in the below placeholder:
    
    client := analytics.New(<WRITE_KEY>, <DATA_PLANE_URL>)

    // Enqueues a track event that will be sent asynchronously.
    client.Enqueue(analytics.Track{
        UserId: "1hKOmRA4GRlm",
        Event:  "Test Event",
    })

    // Flushes any queued messages and closes the client.
    client.Close()
}

Alternatively, you can run the following snippet:

package main

import (
    "github.com/rudderlabs/analytics-go/v4"
)

func main() {
    // Instantiates a client to use send messages to the RudderStack API.
    
    // Enter your write key in the below placeholder:
    
    client, _ := analytics.NewWithConfig(WRITE_KEY,
		analytics.Config{
			DataPlaneUrl: DATA_PLANE_URL,
			Interval:     30 * time.Second,
			BatchSize:    100,
			Verbose:      true,
			DisableGzip:  false,  // Set to true to disable Gzip compression.
		})

    // Enqueues a track event that will be sent asynchronously.
    
    client.Enqueue(analytics.Track{
        UserId: "1hKOmRA4GRlm",
        Event:  "Test Event",
    })

    // Flushes any queued messages and closes the client.
    
    client.Close()
}

Migrating to SDK v4

To migrate to the Go SDK v4.1.0, set the data plane URL in Config (as seen in the above section) instead of passing it as an argument.

SDK initialization options

The RudderStack Go SDK provides the following initialization options:

FieldTypeDescription
IntervalTime (in sec)The SDK sends the messages when this flushing interval time has elapsed.
BatchSizeIntegerTotal number of messages to be sent in a single batch. Default value is 100.
VerboseBooleanWhen set to true, the client sends more frequent and detailed messages to the logger.
RetryAfterTime (in sec)Determines how long the SDK should wait to retry sending the failed messages.
DisableGzipBooleanDisables gzip compression of the requests. By default, this is set to false. To disable gzip, set this parameter to true.
NoProxySupportBooleanSet this variable to true if you do not use a proxy to send the events.
info
Setting NoProxySupport to true will avoid RudderStack making calls to the proxy for fetching the total number of nodes in case of a multi-node setup.

Gzipping requests

success
The gzip compression feature is enabled in the Go SDK version 4.1.0 by default.

The Go SDK automatically gzips requests. However, you can disable this by setting the DisableGzip parameter to true while initializing the SDK:

client, _ := analytics.NewWithConfig(WRITE_KEY,
		analytics.Config{
			DataPlaneUrl: DATA_PLANE_URL,
			Interval:     30 * time.Second,
			BatchSize:    100,
			Verbose:      true,
			DisableGzip: true
		})
warning
The DisableGzip parameter requires rudder-server version 1.4 or higher. Otherwise, your events might fail.

Sending events

warning
RudderStack does not store or persist the user state in any of the server-side SDKs.

Unlike the client-side SDKs that deal with only a single user at a given time, the server-side SDKs deal with multiple users simultaneously. Therefore, you must specify either the userId or anonymousId every time while making any API calls supported by the Go SDK.

Identify

The identify call lets you identify a visiting user and associate them to their actions. It also lets you record the traits about them like their name, email address, etc.

A sample identify call made using the Go SDK is shown below:

client.Enqueue(analytics.Identify{
  UserId: "1hKOmRA4GRlm",
  Traits: analytics.NewTraits().
    SetName("Alex Keener").
    SetEmail("alex@example.com").
    Set("plan", "Free").
    Set("manager", 12),
})

The identify method parameters are as described below:

FieldTypeDescription
userId
Required, if anonymousId is absent.
StringUnique identifier for a user in your database.
anonymousId
Required, if userId is absent.
StringThe SDK automatically sets this identifier in cases where there is no unique identifier for the user.
traitsObjectAn optional dictionary of the user’s traits like name or email.
contextObjectAn optional dictionary of information that provides context about the event. It is not directly related to the API call.
integrationsObjectAn optional dictionary containing the destinations to be enabled or disabled.
timestampTimestamp in ISO 8601 formatThe timestamp of the event’s arrival.

Track

The track call lets you record the user actions along with their associated properties. Each user action is called an event.

A sample track call is shown below:

client.Enqueue(analytics.Track{
  UserId: "1hKOmRA4GRlm",
  Event:  "Signed Up",
  Properties: analytics.NewProperties().
    Set("plan", "Free"),
})

The track method parameters are as described below:

FieldTypeDescription
userId
Required, if anonymousId is absent.
StringUnique identifier for a user in your database.
anonymousId
Required, if userId is absent.
StringThe SDK automatically sets this identifier in cases where there is no unique identifier for the user.
event
Required
StringName of the event.
propertiesObjectAn optional dictionary of the properties associated with the event.
contextObjectAn optional dictionary of information that provides context about the event. It is not directly related to the API call.
integrationsObjectAn optional dictionary containing the destinations to be enabled or disabled.
timestampTimestamp in ISO 8601 formatThe timestamp of the event’s arrival.

Page

The page call lets you record the page views on your application along with the other relevant information about the page.

A sample page call is as shown:

client.Enqueue(analytics.Page{
  UserId: "12345",
  Name:   "Pizza",
  Properties: analytics.NewProperties().
    SetURL("https://dominos.com"),
})

The page method parameters are as described below:

FieldTypeDescription
userId
Required, if anonymousId is absent.
StringUnique identifier for a user in your database.
anonymousId
Required, if userId is absent.
StringThe SDK automatically sets this identifier in cases where there is no unique identifier for the user.
name
Required
StringName of the viewed page.
propertiesObjectAn optional dictionary of the properties associated with the viewed page, like url or referrer.
contextObjectAn optional dictionary of information that provides context about the event. It is not directly related to the API call.
integrationsObjectAn optional dictionary containing the destinations to be enabled or disabled.
timestampTimestamp in ISO 8601 formatThe timestamp of the event’s arrival.

Screen

The screen call is the mobile equivalent of the page call. It lets you record the screen views on your mobile app along with other relevant information about the screen.

A sample screen call is as shown:

client.Enqueue(analytics.Screen{
  UserId: "1hKOmRA4GRlm",
  Name:   "Pizza",
  Properties: analytics.NewProperties().
    SetURL("https://dominos.com"),
})

The screen method parameters are as described below:

FieldTypeDescription
userId
Required, if anonymousId is absent.
StringUnique identifier for a user in your database.
anonymousId
Required, if userId is absent.
StringThe SDK automatically sets this identifier in cases where there is no unique identifier for the user.
name
Required
StringName of the viewed screen.
propertiesObjectAn optional dictionary of the properties associated with the viewed screen, like url or referrer.
contextObjectAn optional dictionary of information that provides context about the event. It is not directly related to the API call.
integrationsObjectAn optional dictionary containing the destinations to be enabled or disabled.
timestampTimestamp in ISO 8601 formatThe timestamp of the event’s arrival.

Group

The group call lets you link an identified user with a group, such as a company, organization, or an account. It also lets you record any custom traits or properties associated with that group.

A sample group call made using the Go SDK is shown below:

client.Enqueue(analytics.Group{
  UserId:  "1hKOmRA4GRlm",
  GroupId: "1",
  Traits: map[string]interface{}{
    "name": "Company",
    "description": "Facebook",
  },
})

The group method parameters are as follows:

FieldTypeDescription
userId
Required, if anonymousId is absent.
StringUnique identifier for a user in your database.
anonymousId
Required, if userId is absent.
StringThe SDK automatically sets this identifier in cases where there is no unique identifier for the user.
groupId
Required
StringUnique identifier of the group in your database.
traitsObjectAn optional dictionary of the group’s traits like nameor email.
contextObjectAn optional dictionary of information that provides context about the event. It is not directly related to the API call.
integrationsObjectAn optional dictionary containing the destinations to be enabled or disabled.
timestampTimestamp in ISO 8601 formatThe timestamp of the event’s arrival.

Alias

The alias call lets you merge different identities of a known user. It is an advanced method that lets you change the tracked user’s ID explicitly. You can use alias for managing the user’s identity in some of the downstream destinations.

warning
RudderStack supports sending alias events only to select downstream destinations. Refer to the destination-specific documentation for more details.

A sample alias call is as shown:

client.Enqueue(analytics.Alias{
  PreviousId: "12345",
  UserId:     "1hKOmRA4GRlm",
})

The alias method parameters are as mentioned below:

FieldTypeDescription
userId
Required, if anonymousId is absent.
StringUnique identifier for a user in your database.
anonymousId
Required, if userId is absent.
StringThe SDK automatically sets this identifier in cases where there is no unique identifier for the user.
previousId
Required
StringThe previous unique identifier of the user.
traitsObjectAn optional dictionary of the user’s traits like name or email.
contextObjectAn optional dictionary of information that provides context about the event. It is not directly related to the API call.
integrationsObjectAn optional dictionary containing the destinations to be enabled or disabled.
timestampTimestamp in ISO 8601 formatThe timestamp of the event’s arrival.

FAQ

How does the Go SDK handle events larger than 32KB?

The Go SDK drops any events greater than 32KB.

Does the Go SDK support event ordering?

The Go SDK does not support event ordering by default.



Questions? Contact us by email or on Slack