This topic will provide you with an overview of the Ironclad Clickwrap Snapshot automation.
Snapshot automation allows you to automatically capture Snapshots on a defined cadence using emulation or our API.
- Capturing Snapshots with emulation requires lower technical lift, and can be used to capture most browser-based experiences, including desktop and mobile-optimized browsers.
- Capturing Snapshots with our API requires support from your technical partners, but opens up the world of experiences that you can keep track of on virtually any online device with native screenshot capabilities that has an application you manage installed. This includes browser-based experiences as well as mobile devices, smart devices, and more.
Ironclad uses Chromium to maintain a set of emulated environments that are used to generate representative evidence for browser-based online experiences. These environments are largely indistinguishable from what real counterparties would encounter when accessing your web properties through their desktop or mobile web browsers like Safari, including security protocols, logins, and on-screen interactions.
If the user must take some action like before seeing the Clickwrap agreement like logging in, putting something in a cart, or proving they’re not a bot by passing a reCAPTCHA test, you can use Command Builder to simulate that interaction.
Ironclad emulates the following environments:
- Desktop web browser: Google Chrome
- Mobile web browser: Mobile Safari
- iOS App: iPhone X
- Android App: Pixel 2 XL
Snapshots captured with emulation are captured at 7:30am ET (4:30am PT, 10:30am UTC) daily, every Monday, or on the first day of every calendar month based on the selected frequency.
Similar to the Embedded Clickwrap snippet, you can alternatively embed a small piece of code in your native applications that will automatically capture a Snapshot if needed using the native screenshot capabilities of the end user’s device.
Because you control when a Snapshot is taken, you can capture any screen at any point in a user’s flow. The system interaction looks something like:
- Your application asks Ironclad if a Snapshot is needed.
- Ironclad replies ‘yes’ or ‘no’ based on the defined frequency, and when the last Snapshot was captured.
- If a Snapshot is needed, your application takes a screenshot of the experience using the end user device’s native screenshot capabilities, and uploads it to Ironclad
Snapshots captured with the API are captured the first time a valid user encounters the experience within the set frequency.
You have a location for a Native app configured to capture daily Snapshots using the API. This means that a Snapshot will be taken the first time a real user encounters a screen you want to capture.
If the first time a valid user encounters the screen is 3 days after the previous Snapshot is taken, there will be 2 Snapshots taken across the 4 days: One on day 1, and a second on day 4.
On the other hand, if 1000 valid users encounter the same screen on the same day, only a Snapshot for the first user will be captured.