Scripting a Voice-over with Audience Messaging

The voice-over in your video can be customized for your viewers according to the viewer segment that they belong to. Using this method, you can provide different voice-overs to different audiences.

Here are two examples of how audience messaging is implemented in a voice-over:

1. In a video promoting credit card benefits, the voice-over that the viewer hears (regarding bonus points) is based on the credit card that the viewer holds. The segment in this example is the credit card type.

2. In a video announcing the opening of a new supermarket, the voice-over that the viewer hears (describing the bakery, deli, or produce department) is based on the department favored by the viewer. The segment in this example is the department.

Audience messaging is based on data that is passed to SundaySky for each viewer. To learn more on how data is used in the SundaySky Video Platform, see Introduction to Data.

Before you begin scripting, we recommend that you read 10 Best Practices for Voice-over Scripting.


1.

From the scene line-up, select the scene that you want to script.

Selecting_a_scene.jpg

2.

Hover over the narration placeholder to see the blue borders and then click inside the placeholder.

Highlighted_placeholder.jpg

3.

In the right pane, toggle the switch to Message by audience.

Toggle_message_by_audience.jpg

4.

Click the down arrow to open the Set message by drop-down list and then select the data element by which you want to segment your viewers.
▶ In the example below, viewers are segmented according to the type of pre-tax account that they hold.

Set_message_by.jpg

5.

Click the down arrow to open the Audience drop-down list and then select the audience that you are scripting the voice-over for.
▶ In the example below, FSA represents all viewers that hold a flexible spending account.

Audience_1.jpg

6.

Type the voice-over script for this audience and then click anywhere outside the text field to save.

Voice-over_for_audience_1.jpg

7.

(Optional) You can include 1:1 personalization within the voice-over that you are scripting. See Scripting a Voice-over with 1:1 Personalization (steps 4-5) to learn how.
▶ In the example below, the voice-over for FSA account holders begins with the viewer's first name.

Personalization_inside_script.jpg

8.

Click +Variation to add a voice-over script for another viewer audience.

Click_%2Bvariation.jpg

9.

Repeat steps 5-6 to select the audience and type the voice-over script.
▶ In the example below, a different voice-over script has been defined for viewers belonging to the HSA (health savings account) audience.

Audience_2.jpg

10.

(Optional) If you have additional audiences, add more variations as needed.

11.

In the When audience is not defined say, type the script that you want for the voice-over when either of the following occur:
● A viewer does not belong to any of the audiences that you have defined.
● Data is not available for 1:1 personalization in a specific audience. Note that when 1:1 personalization is included, the viewer must belong to the required audience and have data for the required element in order to hear the defined voice-over.

▶ In the example below: Here's the current balance... will be narrated in the scene when:
● The viewer does not belong to either the FSA or HSA audience.
● The viewer's first name is not included in the record of an FSA account holder.

When_audience_is_not_defined.jpg

12.

Preview the voice-over.


Notes:

1.

You can create a variation using more than one audience. In such a case, the voice-over you script will be played if the viewer belongs to any of the audiences that have been selected. In the example below, the voice-over script will play if the customer holds an HSA or FSA account.

 

2_audiences.jpg

2.

If you would like a specific audience to not hear any voice-over, select the relevant audience and then leave the message field empty.

 

No_voice-over.jpg

3.

To delete a variation, click the X in the relevant variation section.

 

Delete_variation.jpg

Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Article is closed for comments.