ballerinax/rudderstack Ballerina library

Overview

RudderStack is a customer data platform that collects customer events from websites, apps and servers, routes them to warehouses and business tools, and builds unified customer profiles from them.

The RudderStack connector offers APIs to connect and interact with three RudderStack APIs:

• The Event Stream (HTTP) API, to send identify, track, page, screen, group, alias and batched events.
• The Activation API (Beta), to read and delete the profiles that RudderStack Profiles materialises in a Redis destination.
• The Profiles API, to start a Profiles project run and check its status.

Key features

• Send identify, track, page, screen, group and alias events, one at a time or several in one batch call.
• Use one client for all three APIs. It sends each operation to the right host with the right credential.
• Keep a user's events in order with the AnonymousId header, which the client fills in from each event's anonymousId.
• Read one profile (getProfile) or up to 100 (getProfiles), and delete them (deleteProfile, deleteProfiles).
• Start a Profiles project run (startProfilesRun) and poll it until it finishes (getProfilesRunStatus).
• Switch the Activation and Profiles APIs between the US and EU regions with the region setting.

Setup guide

To use the RudderStack connector, you must have access to a RudderStack workspace. The Event Stream API is available on every plan, including the free plan. The Activation and Profiles APIs need RudderStack Profiles, and the Activation API also needs a Redis destination that the Profiles project syncs to.

The APIs are served from different hosts and use different credentials. A single rudderstack:Client handles all three: it sends the Event Stream operations to your data plane with the source write key, and the Activation and Profiles operations to the hosts of your workspace's region with a Service Access Token.

Set only the credentials of the APIs you call. For example, a client that only sends events needs only the write key and the data plane URL, and a client that only reads profiles needs only the Service Access Token.

Step 1: Sign in to RudderStack

1. Navigate to app.rudderstack.com and sign in, or create an account.

Step 2: Get the source write key and the data plane URL (Event Stream API)

1. In the left sidebar, go to Directory > Sources and select HTTP.

   

2. Give the source a name and complete the setup.

3. On the source page, click Write key to copy the source write key.

   

4. Copy your Data plane URL, which is shown at the top of the Connections page (for example, https://<your-workspace>.dataplane.rudderstack.com).

Step 3: Generate an access token (Activation and Profiles APIs)

The Activation and Profiles APIs authenticate with a Bearer token. For development and testing, you can use a Personal Access Token. For production, use a workspace-level Service Access Token.

For development and testing: Personal Access Token

1. In the left sidebar, go to Settings > Your Profile. Under Personal access tokens, click Generate new token.

   

2. Enter a token name, select the workspace and the scope, and click Generate.

   

3. Copy the token. It is shown only once.

   

For production: Service Access Token

Also see RudderStack's guide on Service Access Tokens. Only workspace Admins can generate them.

1. In the left sidebar, go to Settings > Access Management > Service Access Tokens, and select the Workspace tab.
2. Click Generate new token, enter a name, select the workspace, and click Next.
3. Under Workspace SAT access policy, grant the permissions for the APIs you use:
   • Activation API: Destination Data Access on the Redis destination that the Profiles project syncs to.
   • Profiles API: Edit on the Profiles resource.
4. Click Generate and copy the token. It is shown only once, and its access policy can't be changed later.

Step 4: Note your workspace region

The Activation and Profiles APIs have separate US and EU hosts. If your workspace is in the EU region, set region to rudderstack:EU in the connection config. The default is rudderstack:US.

Quickstart

To use the rudderstack connector in your Ballerina application, update the .bal file as follows:

Step 1: Import the module

import ballerinax/rudderstack;

Step 2: Instantiate a new connector

1. Create a Config.toml file and configure the obtained credentials. Set only the ones for the APIs you use:

   writeKey = "<your-source-write-key>"
   dataPlaneUrl = "https://<your-workspace>.dataplane.rudderstack.com"
   serviceAccessToken = "<your-service-access-token>"

2. Create a rudderstack:Client instance. serviceUrl is the data plane URL, and it's required when you set writeKey:

   configurable string? writeKey = ();
   configurable string? dataPlaneUrl = ();
   configurable string? serviceAccessToken = ();
   
   final rudderstack:Client rudderstackClient = check new ({
       auth: {writeKey, serviceAccessToken}
   }, serviceUrl = dataPlaneUrl);

   Note: For a workspace in the EU region, also set the region so that the Activation and Profiles operations use the EU hosts:

   final rudderstack:Client rudderstackClient = check new ({
       auth: {writeKey, serviceAccessToken},
       region: rudderstack:EU
   }, serviceUrl = dataPlaneUrl);

Step 3: Invoke the connector operation

Now, utilize the available connector operations.

Track an event

public function main() returns error? {
    string response = check rudderstackClient->track({
        userId: "u123",
        event: "Order Completed",
        properties: {"orderId": "o-1001", "revenue": 49.99, "currency": "USD"}
    });
    io:println(response); // ok
}

Get a profile

public function main() returns error? {
    rudderstack:Profile profile = check rudderstackClient->getProfile({
        entity: "user",
        destinationId: "<your-redis-destination-id>",
        id: {'type: "user_id", value: "u123"}
    });
    io:println(profile.data);
}

Step 4: Run the Ballerina application

bal run

Examples

The RudderStack connector provides practical examples illustrating usage in various scenarios. Explore these examples, covering the following use cases:

1. Customer journey tracking: Identify a customer, record the product page they view, then send their add-to-cart and order events together in one batch.
2. B2B signup attribution: Record an anonymous visitor's landing page view with its campaign, link the visitor to the new user ID at signup, record the user's traits, and associate the user with their company.
3. Profile refresh and activation: Start a Profiles run, poll it until it finishes, then fetch the refreshed profiles of a few customers through the Activation API.