This topic will help you understand when to create a snapshot location.
Each unique screen of your embedded agreement should be represented by a Snapshot location. Locations can be created and managed using the Clickwrap web experience or APIs. Locations apply to both web browsers and mobile apps, and can be associated with one or more groups.
You should create a new location every time you create an experience your customers will encounter when accepting your embedded contract.
To learn more about locations, refer to the Snapshot Locations Overview .
- Always map your locations to each unique experience your customers will encounter.
- If two experiences look identical, but have different URLs, they should each be considered a unique experience for a total of two unique experiences. This means you would create two locations.
- To automatically associate a snapshot to an acceptance record, each location has a specific key that can be passed with the agreed event. You create this association when you implement the embedded Clickwrap .
- The amount of templates and contracts used when creating an experience does not necessarily impact the number of locations used.
Each of the four use cases below detail what experience the customer has created, how many locations are required, and the why behind that number.
Remember, you should create a Snapshot location for each unique experience your customers may encounter.
Number of Locations Required
|WonderWeb Inc. displays their terms and conditions on their website. Their terms and conditions are in English and only include one visual.||1||All counterparties have the same experience since there is a single visual in a single language. There are no variables that require additional locations. There is one unique experience.|