The value of this tag will be true if a user has already viewed the native permission prompt. The key for this tag will be: prompt_iOS. To delay the iOS opt-in decision until an optimal point in the user journey (and create a more seamless experience), you’ll first need to create a data tag that identifies users that have already viewed the iOS native permission prompt. In other words, data tags allow you to extract specific and valuable data from your app that you can then use to filter your audience and automatically tigger messaging campaigns.Ĭreate the iOS permission prompt data tag:
#Sales script prompter software app code
Triggers rely on data tags: a key:value pair of string or integer data that you must add to your app code to identify a specific user event or value. In-app message triggers are handled by our SDK. How do triggers and data tags work together? Step 5: Build Data Tags & Triggers to Hone Your Timing
Instead, check to ensure that Dismiss on click is checked in this button window. Unlike the native iOS prompt, your button copy should seek to delay the opt-in decision and leave the door open to revisit this decision in future. Enter the copy for your second button option in the Button Text field of this window. This will create an additional Button 2 window. To add a second button, click Add Block and select Button from the drop-down menu.Doing so will create an automatic trigger, thereby linking this button to Apple’s native permission prompt. In the same window, click Add Click Action and select Push Permission Prompt (iOS).You can adjust the color, size, and alignment of your button to better fit your app aesthetic in the button window. Your first button should always showcase your preferred action (i.e. Message section), enter the copy for your first button in the Button Text field. In the case of a pre-permission prompt, an affirmative button click should trigger the native iOS permission prompt to appear. To improve opt-in rates and create a more seamless user experience, the opt-in CTA buttons should be configured to trigger the appropriate next step. Pre-push permission prompts should give users two options: Step 4: Create Custom Call-To-Action (CTA) Buttons Custom triggers can also be used to hone your message timing and targeting abilities. You will need to fine-tune your qualification criteria further by creating a custom data tag and trigger in Step 4. You should see your new segment highlighted under show to segments.Īlthough your audience is now segmented to include iOS users with more than one app session, it will not automatically exclude iOS users that have previously granted push permission. Doing so will bring you back to the in-app message screen. Click Create Segment to save this new segment.This filter will prevent users from receiving the iOS pre-permission prompt the first time they enter your app. Under filters, select Session Count and use the drop-down menu to select greater than and type 1 into the adjacent field.Selecting this option will create an and filter - in order to qualify for this list, a user must meet both/all the criteria (as opposed to one or the other). Click Add filter if you’d like to add other audience filters such as session count.In the form fields that appear, select iOS as the device type from the drop-down menu. Scroll down in the pop-up window and click on Device Type from the filter options. Rename your new segment to make it easier to identify in the future.
Rather than choosing a premade option, click the Create Segment button at the bottom right corner of the window to build your segment from scratch.
0 kommentar(er)
