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/destinations/catalog/actions-facebook-custom-audiences/index.md
+3-4Lines changed: 3 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -43,15 +43,14 @@ This destination sends audiences, or lists of users, to Facebook Custom Audience
43
43
44
44
After you've connected your Facebook Custom Audiences destination to Segment, set up a mapping that adds users to a new or existing Custom Audience.
45
45
46
+
> warning "Added or updated records is the only supported additive sync mode"
47
+
> Selecting any other sync mode might lead to sync failures with the Facebook Custom Audiences (Actions) destination.
48
+
46
49
1. Navigate to **Connections > Sources** and select your Reverse ETL source.
47
50
2. On the Models page, select the model you'd like to use and click **Add Mapping**.
48
51
3. Select the Facebook Custom Audience (Actions) destination and the Sync Audience action, then click **Create Mapping**.
49
52
4. Enter a descriptive name for your mapping. Segment recommends a name that includes both the audience name and sync mode, for example, `Loyalty Users (Add)`.
50
53
5. Under **Select record to map and send**, select **Added or updated records**. The Added or updated records sync mode both adds new records and attempts to re-add any updated records to the custom audience. Adding updated records to your destination enables better match rates as more user identifiers are added to the source model over time.
51
-
52
-
> warning "Added or updated records is the only supported additive sync mode"
53
-
> Selecting any other sync mode might lead to sync failures with the Facebook Custom Audiences (Actions) destination.
54
-
55
54
6. Set how often your model syncs by setting the [Sync schedule](/docs/connections/reverse-etl/#step-4-create-mappings).
56
55
7. Select or create an audience in Facebook to sync your data with. Click the **Select or create audience in Facebook** button to save the audience ID to your mapping.
57
56
8. Map your model columns to the appropriate Facebook Custom Audience parameters. For more context about data formatting, see the [Sync Audience](#sync-audience) and [Data processing](#data-processing) documentation.
Copy file name to clipboardExpand all lines: src/connections/destinations/catalog/actions-kafka/index.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,20 +20,20 @@ id: 65dde5755698cb0dab09b489
20
20
21
21
The way you've configured your Kafka Cluster informs the authentication and encryption settings you'll need to apply to the Segment Kafka Destination. You may need the assistance of someone technical to provide values for the following Settings:
22
22
23
-
5. On the Settings tab, enter values into the **Client ID**, **Brokers** and **Authentication Mechanism** setting fields.
24
-
6. Populate fields based on the value you selected from the **Authentication Mechanism** field:
23
+
1. On the Settings tab, enter values into the **Client ID**, **Brokers** and **Authentication Mechanism** setting fields.
24
+
2. Populate fields based on the value you selected from the **Authentication Mechanism** field:
25
25
-**Plain** or **SCRAM-SHA-256 / 512** authentication: provide values for **Username** and **Password** fields.
26
26
-**Client Certificate** authentication: provide values for the **SSL Client Key** and **SSL Client Certificate** fields.
27
-
7. Populate the **SSL Certificate Authority** field, if necessary.
28
-
8. Save your changes and proceed to [Configure the Send Action](#configure-the-send-action).
27
+
3. Populate the **SSL Certificate Authority** field, if necessary.
28
+
4. Save your changes and proceed to [Configure the Send Action](#configure-the-send-action).
29
29
30
30
### Configure the "Send" Action
31
31
32
-
9. Select the Mappings tab and add a new **Send** mapping.
33
-
10. Select a Topic to send data to. This field should auto-populate based on the credentials you provided in the Settings tab.
34
-
11. Map your payload using the **Payload** field.
32
+
1. Select the Mappings tab and add a new **Send** mapping.
33
+
2. Select a Topic to send data to. This field should auto-populate based on the credentials you provided in the Settings tab.
34
+
3. Map your payload using the **Payload** field.
35
35
_(Optional)_: Specify partitioning preferences, Headers and Message Key values.
36
-
12. Save and enable the Action, then navigate back to the Kafka destination's Settings tab to enable and save the Destination.
36
+
4. Save and enable the Action, then navigate back to the Kafka destination's Settings tab to enable and save the Destination.
0 commit comments