Best practices for transaction recording

Before you begin recording your transaction, note the following recommendations:

Choose carefully what you want to include in your transaction script.

Typically, transaction measurements are based on companies’ most important e-commerce processes. For example, an e-tailer might choose to record a typical purchase transaction using their site. Or you may want to focus on common transactions where you believe your users are abandoning your site due to performance problems.

Prepare a plan before you begin recording.

Write down a simple description of the navigation steps you intend to include in the script. A list of pages and links to visit may be sufficient, or you may want to develop a more detailed plan for more complex transactions.

Write out your script steps and include them in the Script description.

A written description is very helpful if your script requires troubleshooting by Keynote, and including the steps in the Script description makes them permanently available to anyone working on the script.

Record all transactions using navigation controls and other interface elements that are part of the pages being recorded.

There is no back or forward key. With Transaction Perspective (Real Browser) scripts, you can enter a new URL manually after you have begun recording.

Keep your recorded transactions reasonably short and straightforward.

More complex transaction scripts are more likely to “break” due to minor site changes.

Add aliases to each transaction page.

Page aliases are names applied to each page in a transaction. You can add your own page aliases to make your transactions easier to troubleshoot and analyze.

Always play back the script to verify it before you upload to Keynote.

Verification is especially important for scripts that have been edited.