A concise overview of the latest Affise MMP updates, improvements, and fixes.
What’s new
August releases include considerable fixes of ad costs collection and delivery to Affise MMP. Unity Ads integration is fixed, which improves tracking. Also, reports are now more informative with new filters added.
Update | Type | Customer impact |
AdCost collection is corrected | Fix 🛠 | Ad costs are collected consistently from traffic sources, and reports show correct data. |
New filters in reports | Improvement 🪄 | The Application filter (App Version and SDK Version) is added to statistics reports. |
APK signing behaviour is changed | Improvement 🪄 | Each app can have its own signing key, which now can be set by a customer, or the system can automatically generate a unique key for the app. When a custom key is uploaded, key rotation doesn't break app installations already deployed to users can continue receiving updates with new builds. |
Unity Ads integration is corrected | Fix 🛠 | Registration events are now passed to Unity Ads and duplicate conversions are no longer sent from Affise MMP to Unity Ads. |
Test and production events distinguishing | Improvement 🪄 | Test devices can be added |
Improvements
New filters in reports
What changed: Now it is possible to filter data by App Version and SDK Version in statistics reports.
Why it matters: This update bridges the gap between the marketing and development teams. By filtering reporting by app_version and sdk_version, Affise MMP now enables true cohort analysis based on build releases. Marketers can A/B test campaign performance against specific app variants, while developers can monitor the rollout of new SDKs in real-time to ensure that new code doesn't negatively impact attribution windows or conversion rates.
Documentation: Updated
APK signing behaviour is changed
What changed: Each app can have its own signing key. You can upload your own keystore, which takes priority, or the system can automatically generate a unique key for the app. Along with this, there's a fix: when you upload your own keystore, Affise MMP automatically builds a key rotation chain from the current signer to the new one. This ensures that app installations already deployed to users can continue receiving updates with new builds.
Why it matters: By automating the key rotation chain, Affise MMP ensures that certificate changes are handled at the system level, not the developer level. Your team can now rotate signing keys for security compliance or operational reasons without triggering the'app not installed' error for existing users. Attribution remains intact because the update flow stays continuous. No re-installs, no attribution breaks, no user churn.
Documentation: N/A
Test and production events distinguishing
What changed: Now it's possible to create a list of test devices, and events from those devices are marked as Sandbox and no longer get mixed in with production statistics.
The Test devices section is added to Applications > Settings.
The Environment filter (All/Production/Sandbox) is added to the reports.
Why it matters: This update transforms how your team collaborates on app performance. Developers can now test SDK updates, campaign managers can validate creative redirects, and QA teams can run regression suites without polluting the single source of truth. The Environment filter ensures that production means exactly that: real users, real revenue, real data. When you're preparing board reports or optimizing campaigns, you can trust the numbers completely, knowing that every test event is safely quarantined in the Sandbox.
Documentation: Updated
Fixes
AdCosts collection is corrected
What changed:
Ad costs are now collected consistently across Meta, TikTok, Google, Unity, and Apple Search Ads. Meta, TikTok, or Unity now report actual ad costs, while Google and Apple Search Ads were migrated to the common setup. This is the foundation for accurate ROAS and ROI calculations.
It's possible to see unmatched Google campaigns and manually assign them to an app, ensuring their ad spend is preserved.
ASA cost data collection setup now works like the legacy flow, where the server automatically generates the key pair and displays the public key, so you are no longer asked to provide a private key.
You can connect TikTok expense tracking via OAuth by clicking the Connect button. There’s no longer any need to manually enter the access token, TikTok App ID, or list of Advertiser IDs.
Why it matters: This update protects your bottom line. Accurate cost data means accurate ROAS, and accurate ROAS means you stop wasting budget on underperforming channels and double down on what actually drives profit. We've removed the friction from cost collection across every major network, so your optimization decisions are based on facts, not guesswork.
Documentation: An article about AdCost is coming soon...
Unity Ads integration is corrected
What changed: The registration type events are now received and passed to Unity Ads as Registration events. The same event (install / registration / purchase) is no longer sent to Unity Ads multiple times when redelivered. Unity Ads reporting is now free of duplicate conversions.
Why it matters: Duplicate conversions overload your reports and cost you money. When Unity Ads sees inflated conversion data, it optimizes toward the wrong signals, bidding higher for users who aren't actually converting. With this fix, you get clean, deduplicated event data, so Unity's algorithm learns to acquire users who genuinely install, register, and purchase.
Documentation: N/A
Please contact the Affise Customer Support team regarding all raised questions via the e-mail: [email protected].