Skip to content

Commit b6762b0

Browse files
Merge pull request #2964 from segmentio/develop
Release 22.22.1
2 parents 226270c + 4f3f605 commit b6762b0

File tree

4 files changed

+26
-16
lines changed
  • src
    • connections
      • destinations/catalog
      • sources/catalog/libraries/mobile/kotlin-android
    • engage/profiles

4 files changed

+26
-16
lines changed

src/connections/destinations/catalog/actions-google-analytics-4/index.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -128,3 +128,7 @@ The Google Analytics 4 [debug mode](https://support.google.com/analytics/answer/
128128
### Mobile Data
129129

130130
Google recommends use of their Firebase SDKs to send mobile data to Google Analytics 4. To assist in your implementation, Segment has a [Firebase destination](/docs/connections/destinations/catalog/firebase) available for mobile analytics. For more information on linking Google Analytics 4 properties to Firebase, see [Google Analytics 4 Firebase integration](https://support.google.com/analytics/answer/9289234?hl=en){:target="_blank"}. Segment's Google Analytics 4 destination is currently only compatible with web streams.
131+
132+
### Reserved Names
133+
134+
Google reserves certain event names, parameters, and user properties. Google silently drops any events that include [these reserved names](https://developers.google.com/analytics/devguides/collection/protocol/ga4/reference?client_type=gtag#reserved_names){:target="_blank"}. If you notice that your data isn't appearing in Google, please check that you're not using a reserved name.

src/connections/destinations/catalog/actions-google-enhanced-conversions/index.md

Lines changed: 0 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -6,13 +6,6 @@ hide-dossier: false
66
id: 60ae8b97dcb6cc52d5d0d5ab
77
---
88

9-
> info ""
10-
> This document is about a feature that is in beta. This means that the destination is in active development, and some functionality may change before it becomes generally available.
11-
12-
> success ""
13-
> **Good to know**: This page is about the [Actions-framework](/docs/connections/destinations/actions/) Google Enhanced Conversions Segment destination.
14-
15-
169
The Google Enhanced Conversions destination enables you to improve the accuracy of your conversion measurement. You can supplement existing conversion tags by sending first-party customer conversion data from your website, such as email address, to Google Ads. Segment hashes this data and sends it in a privacy-safe way. Google matches hashed data with signed-in Google accounts to attribute the conversion to ad events, such as clicks or views. To learn more about Google Enhanced Conversions, see Google's documentation [About enhanced conversions](https://support.google.com/google-ads/answer/9888656?hl=en-GB){:target="_blank"}.
1710

1811
> warning "Before you begin"

src/connections/sources/catalog/libraries/mobile/kotlin-android/index.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -458,6 +458,11 @@ Segment currently supports these destinations for Analytics Kotlin and is active
458458
* [Firebase](https://github.com/segment-integrations/analytics-kotlin-firebase)
459459
* [Mixpanel](https://github.com/segment-integrations/analytics-kotlin-mixpanel)
460460

461+
## FAQs
462+
### Can I use the catalog of device-mode destinations from Analytics-Android?
463+
No, only the plugins listed above are supported in device-mode for Analytics-Kotlin.
464+
### Will I still see device-mode integrations listed as `false` in the integrations object?
465+
When you successfully package a plugin in device-mode, you will no longer see the integration listed as `false` in the integrations object for a Segment event. This logic is now packaged in the event metadata, and is not surfaced in the Segment debugger.
461466

462467
## Changelog
463468
[View the Analytics-Kotlin changelog on GitHub](https://github.com/segmentio/analytics-kotlin/releases).

src/engage/profiles/csv-upload.md

Lines changed: 17 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -5,15 +5,15 @@ engage: true
55
---
66
Use the CSV Uploader to add or update user profiles and set subscription states.
77

8-
When you upload a CSV file, Twilio Engage adds new users and updates existing user profiles. CSV rows correspond to a user and columns to an identifier trait in your [identity resolution configuration](/docs/personas/identity-resolution/identity-resolution-settings/).
8+
When you upload a CSV file, Twilio Engage adds new users and updates existing user profiles. Each CSV row corresponds to a user profile and columns to an identifier trait in your [identity resolution configuration](/docs/personas/identity-resolution/identity-resolution-settings/).
99

10-
You can also use the CSV Uploader to set email and SMS [subscription states](#set-user-subscriptions) to track email addresses and phone numbers that you have permission to market to.
10+
You can also [set subscription states](#set-user-subscriptions) for each email and SMS that you upload in the CSV. Subscription states help you track which email addresses and phone numbers you have permission to market to.
1111

1212
## Upload a CSV file
1313

14-
To upload a CSV file, navigate to **Personas > Profiles** and click **Update Users**.
14+
To upload a CSV file, navigate to **Personas > Profiles** and click **Upload CSV**.
1515

16-
### 1. Download a CSV template with identifiers
16+
### 1. Download your CSV template
1717

1818
Click **Download Template** to download a CSV template with identifier columns from your identity resolution configuration. Engage adds subscription columns next to email and SMS identifiers, where you can update subscription states for email addresses and phone numbers.
1919

@@ -22,7 +22,14 @@ Click **Download Template** to download a CSV template with identifier columns f
2222
2323
Navigate to **Personas > Settings** and select the **Identity Resolution** tab to view or add identifiers in your Segment workspace.
2424

25-
### 2. Upload a CSV file
25+
### 2. Fill out your CSV file
26+
27+
Enter values for the identifiers in your CSV file. You can also [set email and phone subscriptions](#set-user-subscriptions) using the `email_subscription_status` and `sms_subscription_status` columns.
28+
29+
> success ""
30+
> Leave any unknown values blank to avoid bad data.
31+
32+
### 3. Upload your CSV file
2633

2734
Upload a CSV file to Twilio Engage in two ways:
2835
- Drag and drop the CSV file in the dropzone.
@@ -32,7 +39,7 @@ Engage processes CSV rows sequentially. Column values, except for a blank subscr
3239

3340
A blank subscription status in the CSV doesn't overwrite current **email** or **phone** [subscription states](/docs/engage/profiles/user-subscriptions/subscription-states/) in your Segment space.
3441

35-
### 3. Name the custom trait
42+
### 4. Name your custom trait
3643

3744
Every time you upload a file, you have the option to add a custom trait to user profiles in the CSV. Use custom traits to help you create audiences or send messages to a specific group of users. You can also add an existing custom trait name from your Segment workspace to the list of users in the CSV file.
3845

@@ -53,12 +60,13 @@ Use error reports to fix invalid rows and quickly re-upload data.
5360
From the Upload History page:
5461

5562
1. Select the link in the **Report** column to download an error report CSV. All rows not present in the error report were processed successfully.
56-
2. Correct data in the invalid rows and remove any extra columns.
57-
3. Click **Update Users** and re-upload the CSV file.
63+
2. Correct data in the invalid rows.
64+
3. Remove any extra columns such as `row_number`, `error_message`, and `error_code`.
65+
3. Click **Upload CSV** and re-upload the file.
5866

5967
## Set user subscriptions
6068

61-
Use the CSV Uploader to set subscription states for user email addresses or phone numbers. Subscription states help you track which email addresses and numbers you have permission to market to.
69+
Use the CSV Uploader to set subscription states for user email addresses and phone numbers.
6270

6371
> info ""
6472
> Each user profile in a Segment workspace can have multiple email addresses and phone numbers, all with different subscription states.

0 commit comments

Comments
 (0)