import {
Accordion,
AccordionContent,
AccordionItem,
AccordionTrigger,
} from "@/components/docs/ui/accordion"
export const exampleFile = 'golang-guide-examples'
# Bento Golang Guide
This guide covers integrating Bento with Go applications: tracking events, managing subscribers, and sending transactional emails.
### Reference
# [API Reference](#api-reference)
# [Troubleshooting](#troubleshooting)
# [FAQ](#faq)
## Getting Started
**1. Package Installation**
## Installation
Install the Bento Go SDK in your project:
**2. Client Configuration**
## Basic Setup
To initialize the Bento client, you'll need your Site UUID, Publishable Key, and Secret Key from your Bento account.
You can find your keys in your [Bento Team](https://app.bentonow.com/account/teams). To see your keys, click
`Your Private API Keys`. If you do not see a Publishable key and Secret Key, click `Generate Key` to
create a set.
## Beginner Guide
## Tracking Your First Event
Events represent specific actions users take within your application. Tracking these actions provides valuable insights
into user behavior patterns and engagement.
#### Adding Subscribers via Events
We recommend using events as the preferred way to add subscribers. One event creates the subscriber and kicks off any
workflows and automations in a single operation.
#### Attaching Data to Events
Events can carry contextual information alongside user actions. This can be used in emails via
[liquid tags](/docs/liquid_guide) or in segmentation. For instance, when recording a purchase event, you can include detailed
transaction information such as:
| Detail | Liquid tag |
|----------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|
| Product details | |
| Purchase amount | |
| Transaction ID | |
| Payment method | |
### Practical Example
When a customer completes a purchase, you can track this as an event while including all relevant purchase details. This
approach enables you to:
- Trigger specific post-purchase workflows
- Launch targeted follow-up automations
- Track lifetime value (LTV) metrics
- Create personalized communications based on purchase history
## Managing Subscribers
If you need to manage subscribers directly there are a set of convenience methods available to you. Add, update, and
unsubscribe subscribers with these simple methods. Currently, you cannot remove subscribers via the API, but you can
remove them from the dashboard `People > All Users`.
#### Adding Individual Subscribers
Please note, while these methods make it easy to manage a subscriber, the Bento recommended way to add **a** subscriber
is via an `event`. This allows you to kick off sequences and automations, while also recording the "event" at the same
time (1 API call).
#### Adding Multiple Subscribers
Importing or modifying multiple subscribers should be handled via the [bulk methods](/docs/examples/nodejs#subscriber-updates),
instead of looping over these calls multiple times.
## Common Use Cases
Here are some common scenarios with ready-to-use code:
## Intermediate Guide
## Custom Fields and Tags
Bento allows you to store custom data about your users through fields and segment them with tags:
## Using Custom Fields & Tags
While custom fields and tags can be used to segment subscribers, most Bento users find that namespaced tags provide a more
effective and easier-to-maintain solution for most segmentation use cases.
#### Namespaced Tags
Namespaced tags follow this format: `namespace`:`detail`
For example, if you offer three subscription plans, you could create these tags:
* `subscription:basic`
* `subscription:pro`
* `subscription:enterprise`
We recommend applying these tags either through an automated flow or via bulk updates.
> **Recommended**
> Tags do not need to be namespaced, but for many customers the organization pays off by using namespaced tags when
> it makes sense.
#### Fields
Fields are perfect for storing information about your subscribers, such as their language, timezone,
or other relevant details. By using fields, you can easily segment subscribers based on their specific needs and
preferences, allowing you to tailor your marketing efforts and messaging to each group.
The primary difference between
fields and namespaced tags is that fields are not limited to a specific detail and do not need to be predefined. You can
store any type of data in a field, including strings, numbers, or even objects. This flexibility makes fields a powerful
tool for storing data.
#### Best Practices
For optimal organization, consider using tags for segmentation while storing more detailed user information in custom
fields. Many successful implementations use a strategic combination of both approaches.
## Tracking Purchase Events
When recording purchase events, you must include a `unique:` key as part of the tracking data. This requirement prevents
duplicate transactions from being recorded in your analytics.
Most users find it beneficial to use their internal cart or order number as the `unique:` key. This approach simplifies
future lookups and maintains consistency across your systems. The `unique:` key value you provide is accessible through
liquid tags when creating custom email templates, allowing for personalized transactional messaging based on specific
purchase details.
Tracking purchases is a great way to monitor customer lifetime value (LTV) and identify recurring customers. Bento reports
on the LTV of each subscriber, allowing you to identify high-value customers and tailor your marketing efforts accordingly.
## Advanced Guide
## Batch Operations
For efficiency, we suggest using batch operations when integrating with Bento. These methods allow for single or bulk
operations on subscribers and events, improving the performance and scalability of your integration. They also cover more
than 80% of the API use cases for most customers.
## Transactional Emails
Bento allows you to send personalized transactional emails for time-sensitive, direct communications. These emails serve
specific functional purposes rather than marketing objectives.
#### Ideal Transactional Email Use Cases
* User onboarding (confirmation etc)
* Password reset notifications
* Sign-in verification links
* Order confirmations and details
* Account notifications
#### NOT Ideal Transactional Email Use Cases
* CC / BCC recipients
* Emails that require an attachment (we suggest always using links for emails for best deliverability)
* Marketing of any kind
* Promotional content
* Newsletters
#### From Address Requirements
The sender address used in your transactional emails must be configured as an Author email within your Bento settings.
Please note that generic addresses such as "~[no-reply@domain.com](mailto:no-reply@domain.com)~" or similar non-personal
addresses are not currently supported.
#### Important Distinction
**Transactional** emails are designed for **essential communications** that facilitate specific **user actions** or provide
critical information.
> 🚨 **Important**
> Transactional emails should **not** be used as substitutes for **marketing** campaigns or **promotional**
> content.
## Subscriber Updates
Many organizations joining Bento already have an established subscriber base that requires bulk updates over time. These
updates commonly include setting field data and managing tags across multiple subscribers. These methods are the
recommended way to manage subscribers, whether you're updating one or thousands.
> These methods cover more than 80% of the API use cases for most customers.
#### Choosing the Right Update Method:
The SDK offers multiple approaches for creating subscribers in Bento, each suited to different scenarios.
#### Preferred Method: Events
The recommended way to create subscribers is via events in response to user activity. This approach activates
automations, workflows, and can contain data enrichment.
#### Alternative Methods
For scenarios where you need to create subscribers independently of user actions:
**1. Single Subscriber Creation**
Use this method when you need to quickly create a single subscriber with minimal data:
> ⚠️ **Warning**
> This endpoint is rate-limited and not suitable for loops or bulk creation. Use only for individual subscriber creation.
**2. Multiple Or Enriched Subscriber Creation**
For creating multiple subscribers or including additional fields:
Best Practices for Batch Imports:
* Though the API supports up to 1,000 subscribers per call, we recommend batches of 200-300 for optimal performance when dealing with extensive data.
* Include all relevant custom fields in the initial import to minimize follow-up updates.
* For very large imports (10,000+ subscribers), consider implementing a queue system with delay between batches.
#### Updating Subscribers
Depending on your requirements, several approaches are available for updating subscriber information.
#### Event-Based Updates (Preferred)
When updates occur in response to user actions, tracking events is the recommended approach:
> Because you can apply as many changes via automations / workflows as you want this is the most flexible method.
> It doesn't require code or deployment changes, and can be completely handled in Bento.
#### Alternative Update Methods
For updates outside of user-triggered actions:
**1. Single Attribute Updates**
For quickly updating a specific attribute on a single subscriber:
> ⚠️ **Warning**
> The Command API is not recommended for multiple updates or bulk operations. Given its heavy rate limit, use the Batch API instead.
**2. Batch Updates**
For updating multiple subscribers or multiple fields at once, use the batch import method:
Recommendations:
* Even for single-subscriber updates, consider using the batch import method when multiple fields need updating.
* The batch import performs an "upsert" operation – it creates subscribers that don't exist and updates those that do.
* This approach provides the most flexibility as your use cases evolve, whether you need to add more changes or modify multiple users simultaneously.
#### Specialized Update Operations
For specific update scenarios, the SDK offers dedicated methods:
## Utility Features
The SDK includes utilities for common secondary tasks, such as email validation and blacklist checks.
## API Reference
### Core API
- **Client** - Main entry point for using the SDK (`bento.Client`)
- **Configuration** - Set up through the `bento.Config` struct with API keys and settings
- **Context Support** - All API operations accept a Go context for cancellation and timeout control
- **Data Types** - Structured request/response types in the root package (`bento.EventData`, `bento.SubscriberInput`, etc.)
- **Error Handling** - Predefined error types (`ErrInvalidConfig`, `ErrInvalidEmail`, etc.) for specialized error handling
### Convenience Methods
#### Core API
| Use Case | Go SDK Method |
|----------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|
| Add a new subscriber | |
| Unsubscribe a subscriber | |
| Update data for an existing subscriber | |
| Add a tag to a subscriber | |
| Update subscriber fields | |
| Track a custom event | |
| Track a purchase event | |
### Modules
#### Batch
| Use Case | Method | API Reference |
|-----------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|
| Import multiple subscribers | | [Import Subscribers](/docs/subscribers#import-subscribers) |
| Import multiple events | | [Import Events](/docs/events_api#create-events) |
| Send emails | | [Send Emails](/docs/emails_api#create-emails) |
#### Commands
| Use Case | Method | API Reference |
|----------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|
| Add a tag | | [Subscriber Upsert](/docs/subscribers#import-subscribers) |
| Remove a tag | | [Subscriber Upsert](/docs/subscribers#import-subscribers) |
| Add a field | | [Subscriber Upsert](/docs/subscribers#import-subscribers) |
| Remove a field | | [Subscriber Upsert](/docs/subscribers#import-subscribers) |
| Subscribe a user | | [Subscriber Command](/docs/subscribers#run-command) |
| Unsubscribe a user | | [Subscriber Command](/docs/subscribers#run-command) |
| Change email address | | [Subscriber Command](/docs/subscribers#run-command) |
#### Experimental
| Use Case | Method | API Reference |
|---------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|
| Validate email address | | [Validate Email](/docs/utility#validate-email) |
| Predict gender from name | | [Gender Guess](/docs/utility#guess-gender) |
| Get IP geolocation | | [IP Geolocation](/docs/utility#geolocate-ip-address) |
| Check domain/IP blacklist | | [Blacklist Check](/docs/utility#search-blacklists) |
#### Fields
| Use Case | Method | API Reference |
|----------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------|
| Get all fields | | [Get Fields](/docs/fields#get-fields) |
| Create a field | | [Create Fields](/docs/fields#create-field) |
#### Subscribers
| Use Case | Method | API Reference |
|---------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------|
| Find subscriber | | [Find Subscriber](/docs/subscribers#find-subscriber) |
| Create a subscriber | | [Create Subscriber](/docs/subscribers#find-subscriber) |
| Run commands | | [Subscriber Commands](/docs/subscribers#run-command) |
#### Tags
| Use Case | Method | API Reference |
|--------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------|
| Get all tags | | [List Tags](/docs/tags_api#get-tags) |
| Create a tag | | [Create Tag](/docs/tags_api#create-tag) |
## Troubleshooting
#### Common Errors
| | |
|------------------------------------------------------------|-------------------------------------------------------------------|
| `Not Authorized` | Check your API keys and ensure they have appropriate permissions |
| `Rate Limited` | Implement backoff/retry logic for batch operations |
| `Network Errors` | Check internet connectivity and API endpoint availability |
| `Exceptions` | Double check you are using a valid `Author` & the payload format. |
#### Debugging Tips
| | |
|----|---------------------------------------------------------------------------|
| 1. | Enable `logErrors: true` in your configuration for detailed error logging |
| 2. | Check the error returned by every API call and handle it explicitly |
| 3. | For batch operations, start with smaller batches to isolate issues |
## FAQ
Can I use this SDK in a frontend environment?
No, this SDK is designed for server-side Go applications as it requires secret API keys that should never be
exposed to clients. If you wish to track events from the frontend, consider using our JavaScript SDK or create a
Go API endpoint that securely handles tracking authenticated user actions.
How do I handle rate limiting?
Implement exponential backoff with Go's retry patterns when you encounter rate limit responses. You can use a
library like `cenkalti/backoff` or implement your own retry logic:
What's the maximum batch size for importing subscribers or events?
Up to 1,000 subscribers or events can be imported in a single batch operation. We recommend batches of 200-300 for
optimal performance. For large imports, consider using Go's concurrency patterns for parallel processing:
How do I track anonymous users?
Currently, the SDK requires an email address for all tracking. Anonymous tracking support is planned for future
releases.
Which Go versions are supported?
The SDK requires Go 1.18 or higher to support the latest features and security improvements. We recommend using the latest stable version of Go for optimal performance and security.
How can I contribute to the SDK?
We welcome contributions! Check the GitHub repository at [github.com/bentonow/bento-golang-sdk](https://github.com/bentonow/bento-golang-sdk)
for contribution guidelines. You can submit pull requests, report issues, or suggest new features.
For direct assistance, join our community Discord server.
How do I handle contexts and cancellation?
All SDK methods accept a context.Context as their first parameter, allowing you to control timeouts and cancellation. Use context timeouts for operations that shouldn't run too long:
For long-running operations or background tasks, consider using a cancellable context that can be terminated when needed.
Can I use the SDK with AWS Lambda or other serverless environments?
Yes, the SDK is compatible with Go serverless environments like AWS Lambda. For best performance, create and reuse the Bento client outside your handler function to take advantage of connection reuse across invocations:
For bulk operations, be mindful of Lambda execution time limits and consider breaking large batches into smaller chunks.