In-App Marketing helps you to engage your app users with messages/experiences and measure the impact of those engagements. Power Hooks are a huge part of engaging your users in your app. Once set up, Power Hooks allow you to change your users' app experience without changing the app code.
Power Hooks are variables that contain a code name (key), a human-friendly name and a value. These variables are passed into your application code by TUNE when your app starts, allowing for settings, text, and logic to be modified on the fly for all user devices without coding, re-versioning or updating your application. Power Hooks can be changed globally impacting all users of the application, customized per user segment or tested as part of an A/B experiment.
What can you do with this key/friendly name/value combination? Once these Power Hook keys and friendly names have been registered into the application, you can control access to a beta feature, change tests on screen, or change display or behavior of anything in the app (color, size, placement, etc.) Once you have registered your Power Hooks and default values, you can sync your power hooks with our dashboard where you can change the values for your power hooks independently from your codebase.
How are the key/value pairs used?
- Key (Hook ID) - The Key/Hook ID is used by App Developers
- Friendly name - The Friendly Name is what appears in the dashboard and is used by Marketers
- Value - The Value is what the user views/experiences
If the current value is unavailable, for example WiFi connectivity, caching or latency issue, IAM automatically fallbacks to the default value. This ensures that users do not receive a blank Power Hook value. Power Hook values are always pulled from the TUNE playlist that is sent to devices. The workflow/scenario includes:
- User has app opened.
- Marketer creates new power hook value and publishes it.
- User receives new Power Hook value once their foreground, background, and/or view has changed.
Implementing Power Hooks
To implement Power Hooks complete the following workflow:
- Register the Power Hook.
- Obtain the value of the Power Hook.
- Use Value In Code.
- Optionally, use callbacks to be notified when Power Hook values change.
Power Hooks Common Use Cases
Common use cases include, but are not limited to:
- Configuration settings
- Modification of API calls
- Messaging, copy and text
- Number of results to display
- Number of columns to show
- Enable/Disable app functionality
- Adjusting required fields
- Ordering of navigation elements
- Text (labels, colors, etc.)
- Position or direction of elements
- Default selections (e.g. quantity)
- Color schemes
- Timing and delays
- Sensitivity controls
- Location accuracy settings
- App specific behavior
- Advertisement frequency and length
- Default values
- Visual media
- Pricing and discounts
- Default tabs or screens
For more information and a detailed Use Case example, see Power Hooks Use Case Example.