You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-**Fast iteration**: Update your tracking configuration at any time, without deploying new app versions.
47
47
-**Fewer dependencies**: Reduce the need for engineering support while still maintaining reliable event tracking.
48
48
49
-
> info "Event Builder during Private Beta"
50
-
> During the Auto-Instrumentation Private Beta, both the Event Builder and the legacy Auto-Instrumentation tab appear in the Segment UI. Segment will remove the legacy tab once all customers have migrated to the Event Builder experience.
51
-
52
49
## How it works
53
50
54
51
After you install the required SDKs and enable Auto-Instrumentation, Segment detects activity like button clicks, navigation, and network calls. Segment captures these events as signals, which appear in the Event Builder.
When you run this code, keep the following in mind:
100
100
101
-
- You'll need to replace <WRITE_KEY> with the key from your Android Source in Segment.
101
+
- You'll need to replace `<WRITE_KEY>` with the key from your Android Source in Segment.
102
102
-`debugMode` sends signals to Segment for use in the Event Builder. Only enable it in development environments.
103
103
- If your app doesn't use Jetpack Compose or Navigation, you can skip those plugin lines.
104
104
@@ -250,4 +250,4 @@ The following table lists the available options:
250
250
251
251
## Next steps
252
252
253
-
After you've confirmed that signals show up in the Event Builder, use the [Generate Events from Signals](/docs/connections/auto-instrumentation/configuration/) guide to configure how signals get translated into analytics events.
253
+
After you've confirmed that signals show up in the Event Builder, use the [Generate Events from Signals](/docs/connections/auto-instrumentation/configuration/) guide to configure how signals get translated into analytics events.
[Amazon EventBridge (Actions)](https://yourintegration.com/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank”} is a serverless event bus that routes real-time data between applications, AWS services, and SaaS tools — making it easy to build scalable, event-driven systems without custom integration code.
11
+
12
+
Segment maintains this destination. For any issues with the destination, [contact the Segment Support team](mailto:[email protected]){:target="_blank”}.
13
+
14
+
## Getting started
15
+
16
+
1. From your workspace's [Destination catalog page](https://app.segment.com/goto-my-workspace/destinations/catalog){:target="_blank”} search for "Amazon EventBridge (Actions)".
17
+
2. Select "Amazon EventBridge (Actions)" and click **Add destination**.
18
+
3. Choose the source you want to connect to Amazon EventBridge (Actions) and create the destination.
19
+
4. In your AWS account, find the EventBridge event bus. Copy your AWS Account ID, then paste it into the AWS Account ID field in the destination settings in Segment.
20
+
5. Select the appropriate **AWS Region** for your EventBridge destination and save the changes.
21
+
6. Go to the Mappings tab, click **+ New Mapping**, then choose the **Send** mapping type. Configure your event trigger and field mappings as needed.
22
+
7. (**Required**:) Before saving your mapping, create a Partner Source. This creates a new EventBridge Partner Event Source in your AWS account if it does not already exist. The source name is
23
+
`aws.partner/segment.com/SEGMENT_SOURCE_ID`. If you don't complete this step, data won't flow to EventBridge.
24
+
8. (Optional:) Once the EventBridge Partner Event Source is created in your AWS account, you can associate the source with the [EventBridge Event Bus](https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-event-bus.html){:target="_blank”}.
25
+
9. Save and enable your mappings.
26
+
10. Enable the destination in settings to send data to Amazon EventBridge.
Copy file name to clipboardExpand all lines: src/connections/destinations/catalog/actions-twilio-messaging/index.md
+23-20Lines changed: 23 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: Twilio Messaging Destination
3
3
id: 674f23ece330374dc1ecc874
4
-
hidden: true
4
+
hidden: false
5
5
hide-dossier: true
6
6
beta: true
7
7
---
@@ -12,10 +12,10 @@ The Twilio Messaging destination connects Segment to Twilio, letting you send me
12
12
13
13
With the Twilio Messaging destination, you can:
14
14
15
-
- Confirm orders or appointments
16
-
- Send shipping updates or reminders
17
-
- Deliver personalized marketing messages
18
-
- Support onboarding and reactivation campaigns
15
+
- Confirm orders or appointments.
16
+
- Send shipping updates or reminders.
17
+
- Deliver personalized marketing messages.
18
+
- Support onboarding and reactivation campaigns.
19
19
20
20
This destination supports two ways to send messages:
21
21
@@ -24,24 +24,24 @@ This destination supports two ways to send messages:
24
24
25
25
Twilio Messaging works with Segment's data and audience tools to send timely, personalized messages without extra integration work.
26
26
27
-
> info "Twilio Messaging Destination Private Beta"
28
-
> The Twilio Messaging Destination is in Private Beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available.
27
+
> info "Twilio Messaging destination public beta"
28
+
> The Twilio Messaging destination is in public beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available.
29
29
30
30
## Getting started
31
31
32
-
To start sending messages through Twilio Messaging, you'll set up your Twilio account credentials and connect the destination in Segment.
32
+
To start sending messages through Twilio Messaging, set up your Twilio account credentials and connect the destination in Segment.
33
33
34
-
You'll set up the Twilio Messaging destination in three stages:
34
+
There are three stages to setting up the Twilio Messaging destination:
35
35
36
36
1.[Create a Twilio API Key and Secret](#authentication-and-setup).
37
37
2.[Add the Twilio Messaging destination in Segment](#add-the-twilio-messaging-destination).
38
38
3.[Configure message mappings](#configuring-message-mappings) to define what messages to send and when.
39
39
40
40
The following sections walk through each step in detail.
41
41
42
-
## Authentication and setup
42
+
## 1. Authentication and setup
43
43
44
-
Before you add the Twilio Messaging destination to Segment, you'll first need to create an API Key and Secret in your Twilio account.
44
+
Before you add the Twilio Messaging destination to Segment, you first need to create an API Key and Secret in your Twilio account.
45
45
46
46
To create your API Key and Secret:
47
47
@@ -55,7 +55,7 @@ To create your API Key and Secret:
55
55
56
56
You now have your Account SID, API Key SID, and API Key Secret, which are required to connect Twilio Messaging in Segment.
57
57
58
-
## Add the Twilio Messaging destination
58
+
## 2. Add the Twilio Messaging destination
59
59
60
60
After setting up your Twilio credentials, add the Twilio Messaging destination to your Segment workspace.
61
61
@@ -73,7 +73,7 @@ The destination is now connected and ready to configure message mappings.
73
73
Users can only access the destination through the specific URL. I'll update these instructions once
74
74
it's publicly available and searchable in the workspace catalog. -->
75
75
76
-
## Configuring message mappings
76
+
## 3. Configuring message mappings
77
77
78
78
The Twilio Messaging destination supports one mapping action: **Send message**. Use this mapping to define when messages get sent and what content they include.
|**Channel**| Choose which channel to send the message on. | Options: SMS, MMS, WhatsApp, and RCS. If selecting RCS, ensure that RCS is enabled in your Twilio account. |
96
+
|**Channel**| Choose which channel to send the message on. | Options: SMS, MMS, WhatsApp, RCS, and Facebook Messenger. If selecting RCS, ensure that RCS is enabled in your Twilio account. Facebook Messenger is a Beta feature.|
97
97
|**Sender Type**| Pick how you want to send the message. | Options: Phone number or Messaging Service. Phone numbers must be approved in Twilio. |
98
98
|**Content Template Type**| Select the type of content template. | Options include Inline or templates you’ve built in Twilio. Segment only shows templates that match your selected Channel and Template Type. |
99
99
|**To Phone Number**| Enter the recipient’s phone number. | Must be in [E.164 format](https://www.twilio.com/docs/glossary/what-e164){:target="_blank"}. |
100
100
|**From Phone Number**| Choose the phone number to send from. | Must be approved in Twilio and support the channel you’re using. |
101
+
|**To Messenger User ID**| Enter the Facebook Messenger User ID to sent to. | Required if Sender Type is Facebook Messenger |
102
+
|**From Facebook Page ID**| Enger your Facebook Page ID. Messages will be sent from this Page. | Required if Sender Type is Facebook Messenger |
101
103
|**Messaging Service SID**| Enter the messaging service SID if you’re using a messaging service. | Required if Sender Type is Messaging Service. |
102
104
|**Content Template SID**| Choose which content template to use. | Required unless you’re using Inline. |
103
105
|**Content Variables**| Map variables used in your content template. | These variables need to be defined in Twilio first. |
@@ -111,7 +113,7 @@ To configure the mapping:
111
113
112
114
The Twilio Messaging destination gives you two ways to create and send messages.
113
115
114
-
**Content templates** are [templates you’ve already set up in Twilio](https://www.twilio.com/docs/content/create-templates-with-the-content-template-builder){:target="_blank”}. They can include text, media, buttons, and other elements, depending on what you’ve built. When you choose a Channel and Content Template Type in Segment, you’ll only see templates that are compatible with those choices. If you’re sending messages to WhatsApp, you’ll need to use Content Templates, since WhatsApp requires pre-approved templates. For most use cases, templates are the way to go because they support richer formatting and keep you compliant.
116
+
**Content templates** are [templates you’ve already set up in Twilio](https://www.twilio.com/docs/content/create-templates-with-the-content-template-builder){:target="_blank”}. They can include text, media, buttons, and other elements, depending on what you’ve built. When you choose a Channel and Content Template Type in Segment, you’ll only see templates that are compatible with those choices. If you’re sending messages to WhatsApp, you need to use Content Templates, since WhatsApp requires pre-approved templates. For most use cases, templates are the way to go because they support richer formatting and keep you compliant.
115
117
116
118
**Inline messages** let you write your message directly in Segment mappings. You can include [dynamic variables](#using-variables) to personalize messages. Inline messages also support adding media URLs if you’re sending MMS or WhatsApp messages. They’re useful for quick tests or simple notifications, but they don’t support all the advanced features that Content Templates do.
117
119
@@ -121,7 +123,7 @@ Choose the option that fits what you’re trying to send. For most customer-faci
121
123
122
124
## Message setup options
123
125
124
-
When you’re configuring your message mapping, there are a few key settings to choose from.
126
+
There are a key settings to choose from when configuring message mappings.
125
127
126
128
### Content template types
127
129
@@ -137,11 +139,12 @@ If you’re sending messages on WhatsApp, all messages must use approved Content
137
139
138
140
### Sender types
139
141
140
-
For the **Sender Type** field, you can choose either a phone numberor a messaging service.
142
+
The **Sender Type** field is used to specify if the message should be sent from a **phone number**, **messaging service**or **Facebook Page ID**. Available Sender Types depend on the selected Channel.
141
143
142
-
If you select **phone number**, Twilio sends the message from a specific number you own. The number must be approved in your Twilio account and support the channel you’re using.
144
+
- For **phone number**, Twilio sends the message from a specific number you own. The number must be approved in your Twilio account and support the channel you’re using.
145
+
- For **messaging service**, Twilio uses a Messaging Service SID to send the message. Messaging Services group multiple senders under one ID, and Twilio decides which sender to use based on your setup. This option is helpful if you’re sending high volumes or managing multiple numbers.
146
+
- For **Facebook Page ID**, Twilio uses the Facebook Page ID to send the message. The [Facebook Page must first be authorized](https://www.twilio.com/docs/messaging/channels/facebook-messenger){:target="_blank"} to send messages in Twilio console.
143
147
144
-
If you select **messaging service**, Twilio uses a Messaging Service SID to send the message. Messaging Services group multiple senders under one ID, and Twilio decides which sender to use based on your setup. This option is helpful if you’re sending high volumes or managing multiple numbers.
145
148
146
149
### Using variables
147
150
@@ -165,7 +168,7 @@ Twilio Messaging also supports a few optional settings you can use in your mappi
165
168
166
169
### Validity period
167
170
168
-
The **Validity Period** controls how long Twilio keeps trying to deliver your message. It’s set in seconds, with a minimum of 1 and a maximum of 14400 (4 hours). If the message isn’t delivered within this time, it won’t be sent. The default is 14400 seconds.
171
+
The **Validity Period** controls how long Twilio keeps trying to deliver your message. It’s set in seconds, with a minimum of 1 and a maximum of 14400 seconds (4 hours). If the message isn’t delivered within this time, it won’t be sent. The default is 14400 seconds.
0 commit comments