Events represent the actions that trigger conversions, such as Install, Registration, Purchase, etc. Each event can have its own identifier, payout, and validation settings.
To access event settings: Offers → Select Offer → Events
Creating or Editing an Event
Open the Events tab of the offer.
Click New Event to create a new event, or open an existing one to edit it.
Fill in the event fields described below.
Save the event.
Once the event is created, Swaarm automatically generates the postback URL that the advertiser or MMP must use to send conversions.
Event Configuration Fields
Some fields described in this article are available only on the Rewarded platform. These fields are marked with an asterisk (*).
Name - the internal name of the event in Swaarm, which is used for reporting and internal management. Examples: install, registration, etc.
Description - optional description used for internal reference.
Creative URL* - optional URL pointing to the creative associated with this event.
Creative Thumbnail URL* - optional URL for a thumbnail preview of the creative.
Visibility - defines whether the event is visible to publishers.
Public - the event is visible to Publishers in Partner Platform and Feed API, and its postbacks will be sent to the Publishers.
Private - the event is hidden from Publishers both in Partner Platform and Feed API, if conversion happens for this event - postback will not be sent to the Publisher
Category* - optional category used to organize events.
Adv. EventType ID - is the event identifier expected from the advertiser or MMP. This value is used to match incoming conversions with the correct event.
Postback URL - after the event is saved, Swaarm generates the postback URL for that event. This link could be used by the advertiser or MMP to send conversion events to Swaarm. Additional parameters may be added depending on the integration setup.
Multiple Postbacks checkbox - enable if the same event can occur multiple times for the same user. If disabled, duplicate conversions will have status Rejected with reason Duplicated Click.
Virtual Event - enable to configure an event that fires automatically based on other events - no advertiser postback required. See Virtual Event →
Virtual Event
A Virtual Event fires automatically in Swaarm - without an advertiser postback - when a user has completed all required events and any configured revenue or cost thresholds have been met. Use it when you want to trigger a conversion event based on a combination of earlier events or a minimum spend level, rather than a direct advertiser postback.
Virtual events are identified by the ⚡ lightning icon in the event list.
How to configure a Virtual Event
Create or open an event on the offer
Enable the Virtual Event toggle
Select the Required Events - all selected events must be completed by the user before the virtual event can trigger
Optionally set Minimum Revenue and/or Minimum Cost thresholds
Click Save
Virtual Event fields
Field | Description |
Required Events | The events that must all be completed before this virtual event fires. The user must have at least one approved conversion for each required event. |
Minimum Revenue | Minimum cumulative revenue (WeGet) from the advertiser. Leave empty for no threshold. |
Minimum Cost | Minimum cumulative cost to the publisher (TheyGet). Leave empty for no threshold. |
Minimum Aggregated Value | Minimum user revenue (received in |
How it works - key behaviour
All required events must be approved - rejected postbacks do not count towards the required events
Order doesn't matter - required events can be completed in any order
Fires once per click ID - once a virtual event has fired, re-completing the required events will not trigger it again
Delayed approvals work - if a required event is initially rejected and later approved, the virtual event triggers once all required events are approved
Both thresholds must be met - if both Minimum Revenue and Minimum Cost are set, both must be exceeded simultaneously before the virtual event fires
Publisher postback - follows standard visibility rules. If all required events are set to Private, no publisher postback is fired for the virtual event
Useful to Know
Default Event - when a new offer is created, a default event is automatically added. This event corresponds to an Install and is used as the primary conversion event for the offer.
The event name can be changed if needed, but the default event itself cannot be removed.
Monetization Indicator ($) - The $ symbol displayed next to an event indicates that a payout is configured for that event. Events with a payout are classified as Monetization events, while events without a payout are treated as Quality events.
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 the event configuration on the offer.
This happens when either the value in the event_id parameter does not match the Adv. EventType ID configured on the event, or the value in the our_event_type_id parameter does not match the Swaarm Event ID. More about Optimization rule here.
Install Event Mapping - in some cases, an advertiser may fire an install conversion using event_id=install. However, even though the default event in Swaarm corresponds to Install, the expected event_id value for the default event is: event_id=0, event_id=1, event_id=Default
If the advertiser cannot change the event value on their side, you can create an additional event on the offer and set the Adv. EventType ID to match the value they are sending (for example, install).
Advanced event validation options are available in event Advanced Settings.
See Advanced Event Configuration for more details.