Verify SmartFloor integration
Step-by-step guide for verifying SmartFloor integration with Metica SDK
Purpose of this Guide
This page outlines the required steps for integrating with the Metica SDK and preparing your build for verification. It also clarifies what Metica will be testing for and how to ensure your integration is accepted quickly.
Before You Begin Integration
Before you start working with the SDK, ensure the following:
Your game has been registered in the Metica dashboard. (Contact: Chloe)
Relevant ad units (e.g., interstitials, rewarded videos) are set up and configured.
Metica has access to your MAX account. (Contact: Justin)
Integration Requirements
Please follow the integration documentation provided by Metica. At a minimum, your app should:
Call the Metica SDK initialization method early in the app’s lifecycle.
Use the Metica SDK to load and show ads, not just native platform ad SDKs.
Ensure your game generates ad impressions that can be reached without complex gating (e.g., ads shown after a short level or via a button).
Log revenue-related events via the SDK.
Build Requirements for Testing
You only need to prepare and submit one standard build of your APK for verification:
The build should not have any hardcoded user IDs.
It should reflect typical production behavior.
The build should be stable and ready for testing. Avoid using early-stage development versions.
SDK Integration Test Tool
Before sending your build to Metica, you should use the SDK Integration Test tool to validate your integration.
See: How to Use the SDK Integration Test Tool
What Metica Will Test
Metica will verify the following via log inspection and SDK-level analysis:
The SDK was successfully initialized.
Ads were properly requested and shown using the Metica integration.
Expected SDK events (e.g., ad load, ad shown, ad revenue) were fired.
Holdout behavior is correctly applied when using the test user ID.
Note: We use real devices to verify your builds and check behavior through logs. We are not testing for gameplay quality or user-facing QA.
Your Role in Testing
While Metica performs the core integration validation, we recommend that you:
Conduct your own QA process in parallel to test ad placement and ensure no runtime errors.
Confirm that ads appear in a predictable and testable flow (e.g., end-of-level, button-triggered).
If possible, provide brief instructions on how to trigger ads in your game to help speed up our review process.
Go-Live Approval
Once the integration has been verified:
Metica will notify you with a go-ahead to release.
You can proceed with your rollout according to your preferred deployment strategy (internal QA, staged rollout, etc).
Support
If you have any questions or need help during integration:
Refer to the official integration documentation provided by Metica.
Reach out to your Metica point of contact for any clarification.
Provide updated builds or debug logs if requested during the verification process.
Last updated
Was this helpful?