Skip to content

Commit 52771ec

Browse files
authored
more notes integration
1 parent c38c23d commit 52771ec

File tree

1 file changed

+6
-2
lines changed

1 file changed

+6
-2
lines changed

src/engage/audiences/linked-audiences.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -130,9 +130,13 @@ As you're configuring your event, you can view a preview of the enriched event b
130130
#### Map event
131131
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.
132132

133-
#### Send test event to destination (optional)
133+
#### Send test event to destination
134134

135-
See what the event will look like in the destination. 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 Segment test event 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.
135+
To send a test event to your destination, you must have already set up a campaign.
136+
137+
We expect the event to land and exist in MCM tool. Of the profile you want to use for testing your event.
138+
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.
136140

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

0 commit comments

Comments
 (0)