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
Copy file name to clipboardExpand all lines: src/connections/auto-instrumentation/configuration.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,9 +1,9 @@
1
1
---
2
-
title: Signals Implementation Guide
2
+
title: Generate Events from Signals
3
3
hidden: true
4
4
---
5
5
6
-
This guide is a reference to configuring and using signals in the Signals SDK with Auto-Instrumentation. On this page, you'll find details on:
6
+
This guide is a reference to configuring, generating, and using signals in the Signals SDK with Auto-Instrumentation. On this page, you'll find details on:
7
7
8
8
- Setting up and managing signal types in the Signals SDK
9
9
- Creating custom rules to capture and translate signals into actionable analytics events
Copy file name to clipboardExpand all lines: src/connections/auto-instrumentation/setup.md
-6Lines changed: 0 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -143,12 +143,6 @@ Next, you'll need to verify signal emission and [create rules](/docs/connections
143
143
144
144
Segment displays `Rule updated successfully` to verify that it saved your rule.
145
145
146
-
## Step 4: Redeploy your application
147
-
148
-
After you've finished deploying your new rule(s), redeploy your application.
149
-
150
-
Redeployment ensures that the new rules are active and that your application can generate events from signals.
151
-
152
146
## Next steps
153
147
154
148
This guide walked you through initial Signals SDK/Auto-Instrumentation setup. Next, read the [Auto-Instrumentation Signals Implementation Guide](/docs/connections/auto-instrumentation/configuration/), which dives deeper into Signals and offers examples rules.
Copy file name to clipboardExpand all lines: src/connections/destinations/actions.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -212,6 +212,10 @@ Mapping fields are case-sensitive. The following type filters and operators are
212
212
You can specify nested properties using dot notation, for example `context.app.name`. If the property might appear in more than one format or location, you can use an ANY statement and add conditions for each of those formats. For example, you might filter for both `context.device.type = ios` as well as `context.os.name = "iPhone OS``"`
213
213
The `does``not exist` operator matches both a `null` value or a missing property.
214
214
{% comment %}
215
+
216
+
> info "Valid property and trait values"
217
+
> Property and trait names must begin with the characters: [a-z], [A-Z] or '_'. Property and trait names don't support special characters in the first character. If you save a property or trait with a special character in the first character, you'll get an Invalid Trigger error.
218
+
215
219
> info "Event property operators and supported data types"
216
220
> Operators support matching on values with a **string** data type:
Copy file name to clipboardExpand all lines: src/connections/destinations/catalog/actions-klaviyo/index.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,7 +31,7 @@ Klaviyo (Actions) provides the following benefits:
31
31
2. Search for **Klaviyo (Actions)** in the Catalog, select it, and choose which of your sources to connect the destination to.
32
32
3. Navigate to [Account > Settings > API Keys](https://www.klaviyo.com/account#api-keys-tab){:target="_blank"} in Klaviyo's UI and copy your API Key into the Segment Settings UI.
33
33
34
-
> info "Generate a Private API Key with full access to Klaviyo's Accounts, Campaigns, List, Profiles, Segments, and Subscriptions APIs"
34
+
> info "Generate a Private API Key with full access to Klaviyo's Accounts, Campaigns, Events, List, Profiles, Segments, and Subscriptions APIs"
35
35
> Create a key by going to Klaviyo's UI and clicking [Account > Settings > API Keys > Create API Key](https://www.klaviyo.com/account#api-keys-tab){:target="_blank"} to generate a Private API Key. After you've created a key, copy it into the Segment Settings UI.
Copy file name to clipboardExpand all lines: src/connections/sources/catalog/libraries/mobile/apple/destination-plugins/intercom-swift.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -228,4 +228,4 @@ The bundled mobile SDK `reset` method un-registers a user in Intercom. When user
228
228
229
229
Intercom doesn't support custom arrays or objects. If you want to send a certain user `trait` or event `property` to Intercom, you must send them at the top level instead of in an array or object.
230
230
231
-
This limitation doThis limitation does not apply if you are mapping custom traits or properties to `company` objects on [Identify calls](/docs/connections/spec/identify/). es not apply, however, for mapping `company` objects on [Identify calls](/docs/connections/spec/identify/). Segment continues to handle that in the same way as before. This is only applicable for any custom traits or properties.
231
+
This limitation does not apply when you are mapping custom traits or properties to `company` objects on [Identify calls](/docs/connections/spec/identify/). Segment continues to handle this in the same way as before. This is only applicable for custom traits or properties.
0 commit comments