Postback Status Optimization
The Optimization rule for Postback Status gives you the flexibility to choose when a certain condition is not met by any conversion received from the app. Mainly by creating such rules, you will let the system know how to attribute certain conversions in your Swaarm system.
Once the rule has been set up and activated, any conversion which doesn't fulfill the created rule will be attributed as Pending or Rejected based on the measurement tool you select while creating the rule. You can create the rules for postback status with the following measurements in the Optimization section.
Postback Status Rules
Alternate Duplicate Detection: For any conversion for which we identify the duplicate event, the conversion status will be set up as "Pending" by the system. The postback parameter "uq" is used here to match the duplicated events. See more about Postback Parameters Supported by Swaarm here
Budget Reached: If any conversion is received from an app but the daily or monthly offer budget has been reached already then the conversion status will be set up as "Pending" by the system.
Duplicated Click: Any conversion received from an app with the duplicated Swaarm click ID, will be set up as "Rejected" by the system.
Invalid Event Type: Any conversion received from an app with an invalid event type ID, will be set up as "Rejected" by the system.
Invalid Purchase: Any conversion received from an app with an invalid purchase will be set up as "Rejected" by the system.
Invalid Security Token: Any conversion received from an app with an invalid Security Token that does not match the current token will be marked as "Rejected" by the system.
Offer Not Active: Any conversion received from an app when the offer is not active in your system anymore, the conversion status will be set up as "Pending" by the system.
Partner Not Approved: If any conversion is received from an app but the partner is not approved on the offer details page then the conversion status will be set up as "Pending" by the system.
SKAd Invalid Signature: SKAdNetwork signature refers to a unique identifier that apps include in their ad campaigns. This signature is used to identify the specific ad network or source of the ad when attributing app installs or conversions. Any conversion received from an app with an incorrect Skad Signature will be set up as "Rejected" by the system.
SKAd not validated my MMP: MMP postback verification measures generally include verifying the authenticity and consistency of the postback data before taking further action or attributing the event to a specific ad campaign. For SKAd conversions, if the postback is not validated by the respective MMP due to any of the reasons, the conversion status will be set up as "Rejected" by the system.
VTA Not Enabled: Any conversion received from an app on a VTA campaign when VTA is not enabled on the campaign, the conversion status will be set up as "Pending" by the system.