Marketing Automation - Sierra WordPress Theme

What is Revmore?

Revmore is a team specializing in mobile application and game monetization technologies, founded in 2023. Its products are aimed at developers, studios, and publishers who wish to increase both in-app purchase revenues and in-app advertising earnings. Although the old names in the database refer to WordPress themes, the platform offered on the current website is actually an AI-based revenue optimization tool, rather than a website theme or a general marketing automation template.

The platform implements a continuous testing process focused on package design, SKU pricing, advertising interval settings, and diversified revenue generation methods. Users need to schedule a demonstration and integrate the SDK; the system then creates optimized solutions by combining historical data and user analytics, rather than generating marketing content simply by entering a prompt.

Main functions

• In-app purchase optimization: By analyzing existing products, prices, payment behaviors, and historical performance, it suggests more suitable package combinations and purchase options for different users or target groups. The results can serve as candidate ideas for new packages and price experiments, and are applicable to game items, subscription benefits, or one-time payment services.
• Recommended customized packages: Machine learning uses the characteristics of the target audience and historical data to determine which product combinations should be tested first, thereby reducing the costs associated with trying many different variables at once. It is still necessary to take into account factors such as the game’s economy, inventory levels, purchasing power in different regions, and the rules of the store.
• SKU price optimization: It involves finding more effective pricing strategies by considering product prices, discount levels, and user behavior, with results compared through experiments. It addresses issues related to pricing decisions and validation; it does not mean that the system can bypass the settings regarding products, taxes, and regional prices imposed by App Store or Google Play.
• A/B testing of ad intervals: This involves continuous testing to determine the most appropriate times and places to display ads, thereby helping the team to strike a balance between ad revenue and user experience. The input data includes existing ad slots, the intervals between ad displays, and performance metrics; the output consists of the results of these experiments along with recommendations for adjusting those intervals in the future.
• Optimization of the advertising monetization structure: Analyzing advertising services and their aggregation mechanisms to help the team adjust ad design, the timing of their display, and the allocation of intermediaries. The fill rate, bidding strategies, policies, and account status of third-party advertising networks still have an impact on the final results.
• Optimized mixed monetization: Involves evaluating in-app purchases and in-app ads under the same strategy, so as to avoid improving one source of revenue at the expense of another or affecting user retention. This approach is suitable for products that rely on various revenue streams such as paid items, incentive videos, and interstitial ads.
• Ongoing experiments: The packages, prices, ad placement locations, and intervals are broken down into verifiable variables, and controlled experiments are conducted continuously. The team should define in advance the key performance indicators, threshold metrics, sample size range, and criteria for stopping the experiments, in order to avoid choosing the version that yields higher short-term revenues alone.
• Integration via multi-platform SDKs: Integrated SDKs are used to include product events and monetization data in the analysis and optimization processes. The site displays compatibility indicators for mobile systems, Unity, and attribution technologies; however, no complete list of available versions, installation packages, API references, or upgrade strategies are provided, and the actual scope of support must be confirmed during a demonstration.

Input, processing, and output

Typical usage process

1. By using a submission form, users can enter their name, company, work email address, and optional phone number; they can also specify the type of application or game, the platform it operates on, the target market, the number of active users, and the current methods of generating revenue.
2. During the product demonstration, information is provided on Revmore’s current beta status, the SDK platforms it supports, data requirements, implementation timeline, scope of services, and pricing.
3. Review the existing IAP products, ad slots, attribution methods, key events, and experimental metrics, and remove any personal data that cannot be provided or is unnecessary.
4. The engineering team integrates the appropriate SDK in the testing environment to verify that the event names, product identifiers, currency of revenue, user segmentation, and advertising feedback are correct.
5. First, establish baseline data by defining the key metrics as well as the threshold metrics, such as revenue, payment rate, revenue per user, ad frequency, retention rate, and crash rate.
6. Choose a variable to initiate small-scale experiments, such as package combinations, SKU prices, or advertising intervals, in order to avoid changing multiple settings at once which would make it difficult to attribute the results.
7. By examining the sample size, experimental duration, and results across different user groups, external factors such as holiday events, fluctuations in distribution channels, and version updates are taken into account and excluded.
8. After optimizing the manually reviewed versions, the winning versions are gradually expanded, while ongoing monitoring is carried out regarding long-term user retention, refunds, negative reviews, and store compliance.

Confirm with the team before connecting.

• The iOS, Android, Unity, or other technology versions supported by the SDK, as well as the methods for upgrading, rolling back, and handling failures.
• It is possible to minimize or anonymize the collected events, device identifiers, ad identifiers, purchase data, and list of user attributes.
• Experimental shunt location, randomization method, statistical criteria, minimum sample size, and stopping rules.
• Who has the authority to set prices and ad configurations, and are there mechanisms for approval, logging, emergency shutdown, and role-based permissions?
• Data hosting locations, retention periods, sub-processors, security measures, deletion and export procedures.
• Beta service level, technical support hours, plans for official launch and migration, and options for discontinuing the SDK.

Which users are it suitable for

• A mobile gaming team that operates both IAP and IAA, with the goal of establishing a unified mixed reality experimentation framework.
• There is already a certain number of active users and purchase data available, but the studio lacks specialized data science and revenue management personnel.
• Product and commercialization teams that need to repeatedly test gift packs, SKU prices, as well as ad locations and frequency.
• Publishers that have the capability for technical integration and are willing to work with suppliers during the beta phase to verify the delivery of data and processes.
• There is a desire to replace subjective pricing with actual experiments, while still retaining teams responsible for manual approval and ensuring a good user experience.

Advantages

• It covers both purchase revenue and advertising revenue, making it possible to identify the interactions between these two sources of income.
• Converting packages, prices, and advertising schedules into variables that can be experimented with is more suitable for continuous iteration than relying on one-time consultation reports.
• Recommendations are generated based on product historical data and user attribution, enabling operation in specific application environments.
• The application execution process is initiated through the SDK, allowing the optimization results to form a feedback loop with actual user behavior and revenue data.
• The demonstration access approach allows both parties to discuss the technology stack, scale, and monetization goals prior to implementation.

Capabilities boundaries and limitations

• The current main page still indicates that it is in beta testing, and the primary way to access it is through scheduled demonstrations; complete self-registration options, a public control panel, or a standardized purchasing process are not yet available.
• The company’s timeline indicates that a formal release will take place in July 2025, but the product page still invites users to join the Beta version. These two descriptions do not match exactly; therefore, it is necessary to have the team provide written confirmation regarding the current stage of the service and its availability at the time of making a purchase.
• The amount of user data displayed on a site, as well as growth in revenue and user engagement, are indicators provided by the platform itself; they cannot be considered guarantees that every application will achieve.
• AI recommendations depend on event quality, sample size, attribution methods, and experimental design; they may be unstable when there is a lack of data or errors in event tracking.
• Price changes, the frequency of advertisements, and adjustments to subscription packages can affect customer retention, refunds, customer reputation, and the protection of minors; therefore, the decision to launch a product should not be based solely on short-term revenue.
• The SDK adds dependencies on the client side, and the team needs to evaluate the package size, performance, crash risks, privacy aspects, as well as the risks associated with third-party components.
• The terms and conditions regarding products, subscriptions, advertisements, and privacy policies of Apple, Google, and advertising networks remain in force; Revmore cannot replace the platform’s own verification processes.

Price and service status

At present, there is no public free version, no fixed trial period, no standard fees for monthly or annual subscriptions, nor any uniform criteria for charging based on the number of users or revenue; furthermore, no public billing page exists. Whether the Beta version is free, whether there are restrictions on the number of applications and the amount of data that can be used, and how the official service will be priced – all these details shall be specified in a written plan provided after the demonstration.

Refunds and cancellation

Currently, no rules regarding refunds, automatic renewal, cancellation, or early termination are available on the Revmore platform. Before signing a contract, it is necessary to specify in detail how fees will be charged, what the subscription costs are, how unused credits will be handled, the process for transitioning from the beta version to the final version, data export options, how to remove the SDK, and what happens in case of service termination.

Platforms and integration

API, SDK, and open-source status

Revmore promotes its integrated multi-platform SDK, but no publicly accessible installation guides, API references, SDK downloads, version logs, example projects, or licenses could be found. Having the SDK does not mean that the product is open source; for now, the core platform should be considered a proprietary service.

• The REST APIs, Webhooks, authentication methods, call limits, or service status page that are available to customers have not been confirmed.
• No official public GitHub organization or product source code repository that corresponds to the company’s identity was found.
• Publishers with the same domain name on the Unity Store offer separate mobile monetization plugins, which include both free and paid resources; these resources from the store cannot be considered as part of the Revmore AI platform’s SDK, its pricing model, or its open-source version.
• Before integrating the enterprise, it is necessary to obtain a list of SDKs, third-party dependencies, change logs, licenses, a privacy policy, instructions for uninstallation, and information regarding the period of security maintenance.

Privacy, Security, and Compliance

The current site map does not contain any privacy policy, terms of service, or data processing agreement specific to the Revmore AI monetization platform. The privacy page available on the site is intended for the iogram iOS application only, and it cannot be used to determine the rules regarding data collection, storage, or sharing on the Revmore platform.

• The SDK may come into contact with purchase, advertising, device, attribution, and behavior-related data, but the specific fields, whether they constitute personal data, and the roles involved in their processing have not yet been disclosed.
• Before connecting, it is necessary to obtain the privacy policy applicable to the Revmore platform, the data processing agreement, a list of sub-processors, information on the hosting location, and the mechanisms for cross-border data transfer.
• Confirm the data transmission processes, as well as measures for static encryption, access control, auditing, vulnerability response, backup, and data deletion timelines; also ask whether production data is used in the beta environment.
• It provides users with mechanisms for being informed, making choices, accessing data, and deleting it, and it handles ad identifiers, consent management, as well as data related to children and minors in accordance with the target market.
• The actual data collection behavior of the SDK should be reflected in the privacy labels on app stores, as well as in the app’s own privacy statements and consent screens; it is not sufficient to rely solely on information provided by the supplier.
• Without written permission, sensitive personal information, chat content, precise locations, or data that is not related to monetization should not be sent to the platform.

Copyright and commercial usage notes

• Users must ensure that they have the proper rights to use the product names, images, advertising materials, user segments, and the data they upload.
• Dynamic pricing, personalized discounts, and advertising experiments require consideration of local consumer protection laws, anti-discrimination rules, transparency requirements, and regulations regarding minors.
• Before disclosing experimental results or customer cases to the public, it is necessary to ensure that the data is anonymized, that confidentiality obligations are met, and that permissions for using both parties’ brands are in place.
• The ownership of the intellectual property related to the platforms, SDKs, recommendations, and derived configurations has not yet been made public; the rights to use customer data, model outputs, and experimental results should be specified in the contract.
• Before setting the pricing or advertising parameters, manual review and the ability to revert to previous settings are maintained, in order to prevent incorrect charges or excessive display of advertisements resulting from automated errors.

Summary

Revmore focuses on using SDKs, historical data, and ongoing experiments to optimize the IAP, IAA, and hybrid monetization models for mobile applications and games. It is currently more suitable for teams that possess real-world data, engineering capabilities, and a willingness to conduct beta testing; until public pricing information, technical documentation, and platform-specific legal terms are available, purchasing decisions should be based on demonstrations, test results, and written contracts.