The following are detailed descriptions of the status values used in the API. These statuses indicate the current state of an offer or conversion in the system:
Conversion Statuses
Conversion statuses represent the current status of each conversion. These values are returned in the conversion callback and the rewardStatus field of the Offerwall and PubMember API.
Status | Definition | Note |
Pending | The conversion has been received but is in a pending state. | If a pending time is configured for the offer, conversions remain pending until this time elapses. For offers set to manual rewarding, conversions automatically enter a pending state until approved by an admin. |
Success | The conversion has been validated and deemed successful. | Applied when the user completes the required action and all conditions are met. |
Rejected | The conversion was processed but did not meet success criteria. | Common reasons: fraudulent activity, invalid/missing data, or exceeding offer limits. List of rejections reasons here. |
Offer Statuses
Offer statuses represent the user’s progress toward completing an offer.
Query the following statuses in the filter.Progress parameter of the PubMember API.
Status | Definition | Note |
In Progress | API status is set to | Indicates the user engaged but has not yet fully completed the offer. |
Completed | All required events for the multi-event offer have been successfully completed. | Marks the offer as fulfilled and user had completed all available events in the offer |
Rejection Reason Definitions
Below explains the various reasons why conversions may be rejected within our system. Understanding these reasons will help you address issues and ensure smoother operations. Below are the common rejection reasons and their explanations.
1. IP Address is Not Whitelisted
Example: “IP address is not whitelisted. Client’s IP: ”
The IP address used to send the conversion request is not on the approved list for the offer's tracking system. Select tracking system have a predefined list of IPs that are allowed to send requests. If the IP is not in this list, the request will be rejected.
2. Malformed Segments
Example: “Malformed Segment1. Expected Segment1: , Received Segment1: ”
Explanation: This error occurs when the security tokens or keys received in the request (e.g., Segment1 and Segment2) do not match the expected values associated with the offer. These tokens ensure the integrity and authenticity of the conversion data.
3. Malformed Signature
Example: “Malformed Signature. Expected Signature: , Received Signature: ”
Explanation: The signature generated for the conversion request does not match the expected signature. This signature is typically a hash generated using a secret key and specific parameters to validate the request’s authenticity.
4. Time Constraints Violations
Max Time from Previous Event Has Passed: “Max time from previous event has passed, event expired.”
Explanation: The time between this event and the previous one exceeded the maximum allowed duration.
Min Time from Previous Event Has Not Passed: “Min time from previous event has not passed.”
Explanation: The event was received too soon after the previous one, violating the minimum time requirement.
Invalid Event Sequence/Out-of-Order Conversion: "The event is not eligible for an update because of sequence number."
Explanation: The sequence number of the current event does not match the expected order of events. Sequence numbers are used to ensure that events are processed in the correct order, and an event may only be accepted if it is received in the expected sequence.