Troubleshoot the 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. See Start a rule in Feature Experimentation or Steps to create an experiment for information on starting an experiment.

Event payload was malformed

Inspect the payload and verify that all required identifiers are correctly set, as described in the API Reference. If the API responds with a 204 response code, it means that the Optimizely logging service has received and persisted the payload. This response code is not an indication that the event payload was validated.

Event had one or more incorrect or missing identifiers

Check that all required identifiers (account_id, visitor_id, entity_id, etc.) are present and correctly formatted.

Event was missing a decision

When activating users, verify that you sent a decision event and that the decision event had an earlier timestamp than the conversion events. Read How Optimizely Experimentation counts conversions for information.

Decision was sent but not attributed to the correct campaign_id

When activating users, make sure the entity_id matches the campaign_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 representing time 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 sure revenue is present under the correct conversion event.

Revenue has incorrect value

Make sure revenue has an integer value and represents the revenue in cents.

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 share the same entity_id, uuid, and timestamp, and saves only one. Ensure each event has a unique uuid or a different timestamp 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 have timestamp values that are equal to or more recent than the related decision event's timestamp.

I sent events through the API, but they are not showing up on the results page.

I sent events with revenue values through the API, but the revenue is not calculated correctly on the Results page.

I sent events through the API, and I see some results, but I did not get the expected values.

Additional resources