Troubleshoot the Event API
Helps you debug issues with sending events to Optimizely's Event API.
I sent events through the API, but they are not showing up on the results page.
Experiment was or is not running
Make sure the experiment is running, and the events have timestamps within the bounds of the running experiment. SeeStart a rule in Feature Experimentation orStep 6 in the Six steps to create an experiment in Optimizely Web Experimentation or Performance Edge documentation for information on starting an experiment.
Event payload was malformed
Inspect the payload to verify that the required identifiers are properly set to conform with theAPI Reference. If the API returns with a204 response code, it means that the Optimizely logging service has received and persisted in the payload. This response code isnot an indication that the event payload was validated.
Event had one or more incorrect or missing identifiers
Inspect the payload and verify that the required identifiers are properly set.
Event was missing a decision
When activating users, verify that you sent a decision event and that the decision event had an earliertimestamp than the conversion events. ReadHow Optimizely Experimentation counts conversions for information.
Decision was sent but not attributed to the correct eventcampaign_id
When activating users, make sure theentity_id matches thecampaign_id for the variation the user was assigned to.
Event had an incorrect or out-of-bounds timestamp
When activating and tracking users, make sure timestamps have the correct format (a 13-digit integer representingtime since epoch in milliseconds) and are within the bounds of the running experiment.
I sent events with revenue values through the API, but the revenue is not calculated correctly on the Results page.
Revenue is missing from event payload
Make surerevenue is present under the correct conversion event.
Revenue has incorrect value
Make surerevenue has an integer value and represents the revenue incents.
I sent events through the API, and I see some results, but I did not get the expected values.
Duplicate events are sent
Optimizely Experimentation detects events that have the sameentity_id,uuid, andtimestamp and saves only one of them. Make sure each event is using a uniqueuuid ortimestamp before sending.
Events have out-of-bounds timestamps
Make sure timestamps have the correct format (a 13-digit integer, representing time since epoch in milliseconds) and are within the bounds of the running experiment.
Conversion events have timestamps older than the decision event's timestamp
Make sure the conversion events havetimestamp values that are equal to or more recent than the related decision event's timestamp.
Additional resources
Updated 2 months ago