Merge pull request #4778 from braze-inc/lx/doc_reqs

_docs/_user_guide/engagement_tools/campaigns/testing_and_more/sending_test_messages.md

@@ -13,7 +13,7 @@ description: "This reference article covers how to send test messages across the
 
 > This reference article goes over how to send test messages across the different Braze channels and how to incorporate custom event properties and user attributes.
 
-Before sending out a messaging campaign to your users, as a best practice, we recommend testing it to make sure it looks right and operates in the intended manner. You can create and send test messages to select devices or team members using the tools in the dashboard.
+Before sending out a messaging campaign to your users, as a best practice, we recommend testing to make sure it looks right and operates in the intended manner. You can create and send test messages to select devices or team members using the tools in the Braze dashboard.
 
 {% alert important %}
 Make sure to save your campaign draft after testing to avoid deleting your campaign. You can send test messages without saving the message as a draft.
@@ -75,7 +75,7 @@ After creating your SMS/MMS message, you can send a test message to your phone t
 {% endtab %}
 {% tab Webhook %}
 
-After creating your webhook, you can do a test send to check the webhook response. Select the **test** tab and select **send test** to send a test send to the supplied webhook URL. You may also select an individual user to preview the response as a specific user. 
+After creating your webhook, you can do a test send to check the webhook response. Select the **Test** tab and select **Send Test** to send a test send to the supplied webhook URL. You can also select an individual user to preview the response as a specific user. 
 
 ![Test Content Card]({% image_buster /assets/img/webhook_test.png %})
 
@@ -102,9 +102,9 @@ Use these testing filters to select users with specific email addresses or exter
 
 These filters have the following options:
 
-1. **Equals** - Looks for an exact match of the email or user ID you provide. Use this if you only want to send the test campaigns to devices associated with a single email or user ID.
-2. **Does not equal** - Use this if you want to exclude a particular email or user ID from test campaigns.
-3. **Matches** - Finds users that have email addresses or user IDs that match part of the search term you provide. You could use this to find only the users with an "@yourcompany.com" address, allowing you to send messages to everyone on your team.
+1. **Equals**: Looks for an exact match of the email or user ID you provide. Use this if you only want to send the test campaigns to devices associated with a single email or user ID.
+2. **Does not equal**: Excludes a particular email or user ID from test campaigns.
+3. **Matches**: Finds users that have email addresses or user IDs that match part of the search term you provide. You could use this to find only the users with an "@yourcompany.com" address, allowing you to send messages to everyone on your team.
 
 These filters can also be used in conjunction to narrow down your list of test users. For example, the test segment could include an email address filter that `matches` "@braze.com" and another filter that `does not equal` "sales@braze.com". You can also select multiple specific emails by using the `matches` option and separating the email addresses with a "\|" character (e.g., `matches` "email1@braze.com\|email2@braze.com").
 
@@ -163,13 +163,11 @@ Target the users as you would for testing using either a testing filter or by ta
 
 ![Test Message Targeting][17]
 
-Go into your app and complete the custom event, and the campaign will trigger, and you should see the message customized with the event property:
+Go into your app and complete the custom event. The campaign will trigger, and you should see the message customized with the event property:
 
 ![Test Message Example][18]
 
-Alternatively, if you are saving custom user IDs, you can also test the campaign by sending a customized test message to yourself. After writing the copy for your campaign, select the **Test** tab and choose **Customized User**. Add the custom event property on the bottom of the page, add your user ID or email address to the top box, and click **Send Test**. 
-
-You should receive a message personalized with the property.
+Alternatively, if you are saving custom user IDs, you can also test the campaign by sending a customized test message to yourself. After writing the copy for your campaign, select the **Test** tab and choose **Customized User**. Add the custom event property on the bottom of the page, add your user ID or email address to the top box, and click **Send Test**. You should receive a message personalized with the property.
 
 ![Testing Using Customized User][22]
 

_docs/_user_guide/engagement_tools/canvas/managing_canvases/cloning_canvases.md

@@ -46,6 +46,16 @@ However, if a Canvas has variant-level branching, and this variant branches out
 
 As another example, if a Canvas has a full step that has exception events and this full step also uses the delay filter "in" or "on the next", then it can't be cloned to Canvas Flow. However, if a Canvas step uses exception events with any other delay type, then the Canvas can be cloned to Canvas Flow.
 
+## Recommendations
+
+To allow existing users to continue their user journey after you've cloned your original Canvas to Canvas Flow, you can add filters to your existing Canvas which prevent new users from entering the new Canvas.
+
+If re-eligibility is off, add the filter "Entered Canvas Variation". If re-eligibility is on, these are the possible methods to consider to ensure that users don't enter the same Canvas twice.
+- Update the existing Canvas to include a unique tag. For the new Canvas, add a filter "Last Received Message from Campaign or Canvas with Tag". This will prevent users from entering the Canvas twice after a specific entry date (total number of days after the last message is sent from the original Canvas plus the conversion window). 
+- **The following method will consume data points.** Update the original Canvas to include a Braze-to-Braze webhook that triggers a custom attribute date timestamp upon entry. This attribute can be used to prevent users from entering the new Canvas after the specified date (total number of days after the last message is sent from the original Canvas plus the conversion window).
+
+For API-triggered Canvases, coordinate with your engineering team to ensure that these Canvases are using the new Canvas ID once the new Canvases are ready to launch.
+
 For more information about the differences between the original Canvas editor and Canvas Flow experience, check out [Canvas FAQs]({{site.baseurl}}/user_guide/engagement_tools/canvas/faqs/#what-are-the-main-differences-between-canvas-flow-and-the-original-canvas-editor).