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/facebook-pixel-server-side/index.md
+1-2Lines changed: 1 addition & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -133,13 +133,12 @@ Beginning February 15th 2021, Facebook requires the `action_source` server event
133
133
134
134
### Action Source
135
135
136
-
`action_source` is set to "website" as a default value. If a mobile library is used then `action_source` defaults to "app".
136
+
`action_source` is set to "website" as a default value.
137
137
138
138
You can set `action_source` manually by passing it as a property of a Track event. You can use either snake case or camel case to include `action_source` as a property in Track events.
Copy file name to clipboardExpand all lines: src/personas/journeys/faq-best-practices.md
+9-2Lines changed: 9 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,12 +11,19 @@ title: Journeys Best Practices and FAQ
11
11
When you create a multi-branch split, do not create overlapping conditions that might lead a user to qualify for more than one step at a time.
12
12
13
13
For example:
14
-
-If a multi-branch split has the following conditions, a user who has performed both `webinar attended` and `registration form submitted` will end up in both branches.
14
+
-In the case where a multi-branch split is based on the conditions`registration form submitted` and `webinar attended`, a user may satisfy both conditions, and therefore is eligible for both paths.
15
15
- To set a priority, branch 2 should then be `who performed registration form submitted and did not perform webinar attended` to ensure mutual exclusivity
16
16
17
17
### Add time windows whenever possible
18
18
19
-
Where possible, add a time window when defining conditions to ensure that users exit the step or Journey, rather than remain at the step forever. This prevents Journeys from collecting stale users which can muddle your data for analytics, or cause you to over-target.
19
+
Add time windows when defining conditions to enforce funnel constraints in a Journey, rather than using an unbounded event condition which operates on the entire history of the user profile. For example, to check if a user has completed an order since receiving an email triggered 7 days ago, use the condition “Order Completed at least 1 time within 7 days.”
20
+
21
+
### Suppress targeting with journey lists
22
+
23
+
Unlike lists associated with Personas Audiences, users who are added to a journey list cannot be subsequently removed. Lists are typically associated with advertising campaigns, and you must take additional steps if you wish to ensure that users do not continue to be targeted with ads after they achieve some goal. A typical implementation pattern is:
24
+
1. Use a send to destination step to add users to the initial targeting list.
25
+
2. Create additional journey steps to model the conditions where a user should be removed from targeting. Create a second send to destination step for the removal list.
26
+
3. When configuring targeting conditions in the destination interface, use boolean logic to include only those users who are in the initial list AND NOT in the removal list.
The destination receives a list of users who qualify for that step of the Journey. This list is constantly updated by Segment.
59
+
The destination receives a list of users who qualify for the associated journey step. Unlike lists associated with Personas Audiences, users who are added to a journey list cannot be subsequently removed. See [best practices](/docs/personas/journeys/faq-best-practices#suppress-targeting-with-journey-lists) for techniques to suppress targeting with journey lists.
83
60
84
61
For more information, see [Using Personas Data](/docs/personas/using-personas-data/).
0 commit comments