New in Conversion Rules: More control over post-install validation

Fraud prevention doesn't stop at attribution. Suspicious installs, spoofed events, and invalid post-install activity can have major impacts on your reporting, optimization, and spend decisions. That’s why our recent updates to Conversion Rules give teams more precise control over post-install validation and event quality.

Conversion Rules let marketers define custom validation logic for installs and engagements. This allows them to control whether activity is accepted, flagged as unverified, untrusted, or rejected at the post-install level depending on the rule type. 

Event rules extend that control to post-install activities like sessions, events, and ad revenue, helping teams protect data quality, reduce fraud, and keep reporting cleaner.

We’re continuing to expand the capabilities of our Conversion Rules product. Advertisers can now apply more targeted logic to monetization events, event flows, and rule configuration, ultimately supporting stronger reporting and better optimization.

Flow Check gives advertisers more control over how post-install events are validated by letting them define the expected timing, sequence, and payload requirements for an event.

The flow-based logic includes time-based suppression. This makes it possible to prevent an event from being triggered again within a defined time window, ensuring an event is only accepted once during a specific period.

Flow Check also supports required parameters, so specific SDK parameters such as user_id or transaction_id must be present in the event payload. When multiple parameters are defined, all of them must be present for the event to pass.

This can help reduce noise and limit invalid repeated activity. It also gives teams a more practical way to manage event quality in cases where repeated triggers can distort reporting.

Server-to-server-only event configurations are now available through the Source check condition within Event Rules, giving advertisers a more direct way to manage S2S validation and clearer visibility into which events require server-to-server checks.

To add a further layer of security to your setup, you can use S2S IP Allowlisting. When enabled, only S2S event requests originating from a defined list of IP addresses are accepted, while requests from non-allowlisted IPs are rejected. This helps ensure that S2S data can only be sent from trusted infrastructure.

Suspicious ad revenue filtering is now available within Conversion Rules, integrating into the same reporting and setup environment as other rule types. 

Apply granular controls using target filters such as country and ad revenue source, build precise rules around revenue per impressions, track rejected activities through callbacks, review rejected data in aggregated reports, and use test mode to validate setup before applying changes.

A new device-level rule type, the Parameter Rule, adds another way to validate install and post-install activity in Conversion Rules. With Parameter Rules, advertisers can define one or more SDK parameters, such as product_id, that must be present in the payload. If the required parameters are missing, the activity is flagged as either Unverified or Untrusted.

The rule supports multiple required parameters using and logic, so all specified parameters must be present for the activity to pass. You can also choose how attribution changes when parameters are missing and optionally scope the rule to specific channels, giving more control over where and how parameter validation is applied.

To see when missing parameters are the reason activity was flagged, you can apply this rule to installs, post-install activity, or both.

To learn more about Conversion Rules or how Adjust can help grow your app business in general, reach out to your contact person or request a demo today.