Postback Status
The Optimization rule for Postback Status gives you the flexibility to choose when a certain condition is not met by any conversion received from Advertiser. 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.
Rules for Postback Status
Budget Reached: If any conversion is received from an Advertiser 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 Advertiser with the duplicated Swaarm click ID, will be set up as "Rejected" by the system.
Invalid Event Type: Any conversion received from an Advertiser with an invalid event type ID, will be set up as "Rejected" by the system. Note that Swaarm supports
our_event_type_idto receive the event ID created by the Swaarm system andevent_idto receive the advertiser Event ID.Invalid Security Token: Any conversion received from an Advertiser with an invalid Security Token that does not match the current Postback Security Token will be marked as "Rejected" by the system.
Publisher Not Approved: If any conversion is received from an Advertiser but the publisher is not approved on the offer details page then the conversion status will be set up as "Pending" by the system.
Offer Not Active: Any conversion received from an Advertiser when the offer is not active in your system anymore, the conversion status will be set up as "Pending" by the system.
Rejected By Advertiser: Any conversion received from an Advertiser with the "status=rejected" will be set up as "Rejected" by the system.
SKAd Invalid Signature: SKAdNetwork signature refers to a unique identifier that advertisers 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 Advertiser 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 Advertiser on a VTA campaign when VTA is not enabled on the campaign, the conversion status will be set up as "Pending" by the system.
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
Invalid Adjust IP: Any conversion from an Adjust IP that is invalidated by the server and does not belong to Adjust then the conversion status will be set up as "Rejected" by the system.
AppsFlyer Retargeting: Any conversion on offer with the Swaarm parameter and AppsFlyer macro "retargeting={Is-retargeting}" coming from AppsFlyer that is marked as "retargeting=1 or true" the conversion will be Approved, but if it is marked "retargeting=0 or false" then the conversion will be set to Rejected.
FAQ's
What is an Invalid Event Type?
Conversions are rejected due to Invalid Event Type when the value passed in the event_id or our_event_type_id parameter in the advertiser postback does not match with the value in the Event set-up of the offer. The value passed in the event_id parameter should match with the value passed in the Adv. EventType ID field and our_event_type_id should match with Swaarm's event ID.
Use the Conversion Report to check the event_id that the advertiser is firing. Make sure to add the field "Adv. Postback" and filter by "Evaluation Status Failed Rules in Invalid Event Type" on the Conversion Report.
For example, an advertiser might fire a conversion with event_id=install. However, since the default event in Swaarm is install, you will need to check if they can fire the conversion with 0, 1, or Default:
event_id=0event_id=1event_id=Default
If the Advertiser cannot change the event on their side, then you can create an additional event on the offer with Adv. EventTypeId for the event configured as install. However, this will need to be configured on all the network offers from the advertiser.