Skip to content

Commit 7975dc8

Browse files
authored
updating payload info [netlify-build]
1 parent 81acb02 commit 7975dc8

File tree

1 file changed

+8
-6
lines changed

1 file changed

+8
-6
lines changed

src/engage/audiences/linked-audiences.md

Lines changed: 8 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -122,21 +122,23 @@ Select additional traits and properties to include when the event is sent.
122122

123123
#### Show/Hide preview
124124

125-
As you're configuring your event, you can view a preview of the enriched event based on your property selections. See what the enriched event will look like in your payload schema.
125+
As you're configuring your events in Linked Audiences, you can view a preview of the enriched event based on the properties you select. See what the enriched event will look like in your payload schema.
126126

127-
> info
128-
> It is important that copy the data from your final payload schema, you will need this data later when you set up your destination.
127+
> important
128+
> It is important to make a copy of the data from your final payload schema, as you will need this data later when you set up your destination.
129129
130130
#### Map event
131+
131132
Only required fields that need to be filled out are displayed. All other optional & pre-filled fields are hidden - These fields are pre-filled with properties that will work by default.
132133

133134
#### Send test event to destination (optional)
134135

135-
Enter the user Id that you previously set up in your destination.
136+
Send a test event to see if your action-based campaign is rendering correctly. Enter the destination User id for the profile you want to use to test the event, then click the Send test event to destination button.
136137

137-
We expect the event to land and exist in MCM tool. Of the profile you want to use for testing your event.
138+
> important
139+
> The User ID you enter here must match a User ID you previously set up in your destination.
138140
139-
To see what the event will look like in your destination, enter the destination User ID where you want this test event to be sent. You can send a test event to see if your action-based campaign is rendering correctly. If the test event is not successful, adjust the User id to match the existing Source user id. Or if you need to create a new user in your Source, you can define a unique user id in the Segment test event.
141+
If the test event is not successful, adjust the User id or other properties in your destination, then test again.
140142

141143
The Event content drop-down shows you a preview of what the data sent to your destination may look like.
142144

0 commit comments

Comments
 (0)