Insert’s Screen Capture capability enables you to capture and tag screens to use for in-app campaigns and user behavior tracking. The process starts by pairing your device, and then navigating to a screen of interest in your app. Once on the desired screen, you simply tap the camera icon in your app. The Insert SDK transmits information about the native elements in the app to the Insert Cloud Service, and you are presented with a ‘screenshot’ in the web console.
The next step is to tag the screenshot so that it can be uniquely identified by the Insert platform. You can select any native element on the screen, either by pointing and clicking on the image or by selecting the element from the list on the right side of the canvas. That said, there are some best practices that we encourage you to follow.
1) Keep tagging minimal: Do not tag more elements than needed to identify the screen. By keeping it minimal, you optimize the identification process and eliminate sending unnecessary data to the Insert Cloud Service. As an example, consider the screen shown in Figure 1 above. While there are multiple elements on that screen, tagging the Details title header as shown below is sufficient for unique identification.
2) Keep captures minimal: Only capture the screens that you intend to use to either launch campaigns or track user activity for segmentation purposes. This ensures that only necessary data is transmitted from your app to the Insert Cloud Service. Consider the example Product Screen again. There are in fact many different screens that have the same general structure but vary by content as shown below.
In cases like depicted in Figure 3, it is usually best to capture one of the screens and identify it in a generic way (i.e. by tagging the Details title header as shown earlier). By doing this, Insert will be able to identify any of the product detail screens, and you can attach campaigns to specific screens via a Field Value trigger.
3) Avoid dynamic elements: As a general rule, you should not tag fields that contain dynamic text or number values. Since these values change they may not be suitable for identifying a screen. If the value of dynamic fields will dictate whether or not to display an insert, use the Field Value trigger to define conditions related to these values. Back to our Product Screen example. Recall that we initially captured the screen and tagged only the Details title header. If we want to create an insert and only show it on the Black Tie detail screen, we can use a Field Value trigger as shown below.